Peoples, Based on today's feedback I will restructure the WSDL and XML as follows: 1. The ogf_nsi_connection_types.xsd will be used as a reference description for the NSI protocol specification and should have all transport/implementation specific components removed and placed in either the WSDL definition of a separate implementation specific XSD file. 2. The replyTo element in all request messages will need to be moved out to the WSDL or a separate XSD definition since this is specific to the web services implementation. 3. Remove the GenericResponseType out to the WSDL or a separate XSD definition since this is specific to the web services implementation. 4. Explicitly define all protocol request, confirmed, and failed message types in the XSD so that the XSD is clear on message definition without need for WSDL files. If I missed anything let me know. I will update the schema tonight an issue a new version following the suggested pattern. John. ----- Original Message -----
From: "John MacAuley" <john.macauley@surfnet.nl> To: nsi-wg@ogf.org Sent: Wednesday, March 16, 2011 12:31:35 AM Subject: [Nsi-wg] NSI Connection Services WSDL Peoples,
I promised to get a draft of this out today so here it is. I checked to make sure it compiles, but not much beyond that. I have been adding documentation annotations to the files, but have not completed it yet. There is probably enough in there now for people to understand how it is laid out. I also auto-generated a PDF for the XSD types if you would rather look at that. I made many types up for lack of specification. We can discuss.
John.
_______________________________________________ nsi-wg mailing list nsi-wg@ogf.org http://www.ogf.org/mailman/listinfo/nsi-wg