I am good with these changes and will issue a new update. I have a constant battle with spaces versus tabs. I just went back to tabs :-) ----- Original Message -----
From: "Atsuko Takefusa" <takefusa@acm.org> To: "John MacAuley" <john.macauley@surfnet.nl> Cc: "nsi-wg@ogf.org WG" <nsi-wg@ogf.org> Sent: Tuesday, July 12, 2011 10:57:31 AM Subject: Re: [Nsi-wg] Updated NSI WSDL - July 7th 2011
Hi John,
I think requester and provider operations should be separated as attachments. (I have not checked its grammar.) Because a requester module and a provider module may be different.
And I have a cosmetic suggestion. Could you use spaces, instead of 4-character tab? I think you use 4-character tab in the wsdl and schema files, but it is not general for editors, such as emacs and vi.
Thanks,
Atsuko
2011/7/8 John MacAuley <john.macauley@surfnet.nl>:
Peoples,
I have updated the WSDL and XML schema based on the decisions reached at Wednesday's meeting. The only remaining item I need to get done, and I think it can wait until after OGF, is to add the security policies to the WSDL so we can sign the messages to validate authenticity. This will not impact the core XML schema.
Here are the changes in this version:
1. Cosmetic change to operation primitive names:
Request a reservation: reserveRequest changes to reservationRequest and remains rsv.rq in the state machine. reserveConfirmed changes to reservationConfirmed and remains rsv.cf in the state machine. reserveFailed changes to reservationFailed and remains rsv.fl in the state machine.
Terminate a reservation: cancelRequest changes to terminateRequest and changes to term.rq in the state machine. cancelConfirmed changes to terminateConfirmed and changes to term.cf in the state machine. cancelFailed changes to terminateFailed and changes to term.fl in the state machine.
State machine change Canceling state changes to Terminating.
2. Removed the NsaType and changed requestorNSA and providerNSA to be of type anyURI. This removes the additional per-NSA security attributes.
3. Changed connectionId definition to be an anyURI and stated it must be a Universally Unique Identifier (UUID) URN as per ITU-T Rec. X.667 | ISO/IEC 9834-8:2005 and IETF RFC 4122.
4. Removed security attributes from confirmed messages.
5. Extended the NsiExceptionType to use an attribute type/value pairs for added flexibility.
6. Added simpleTypes for NsaIdType, GlobalReservationIdType, ConnectionIdType, and uuidType so there is a single location requiring modification if we decided to change the types.
John.
_______________________________________________ nsi-wg mailing list nsi-wg@ogf.org http://www.ogf.org/mailman/listinfo/nsi-wg
-- Atsuko Takefusa Information Technology Research Institute, AIST