Oh, speaking of globalreservationid! we're only passing it around and persisting it not doing anything with it AFAICT. - it's supposed to be a way to tie this connection with external services, right? - if so, the name is not quite descriptive of its function - it's also optional, while the name sounds terribly important - why a URI instead of a string? or key-value pair - there's only one of them, why not allow for a set? On Dec 5, 2012, at 6:46 AM, Henrik Thostrup Jensen wrote:
Hi
Found a couple of things in the v2 CS WSDL. Mostly minor stuff.
The types:
GlobalReservationIdType ( restriction base: xsd:anyURI ) ConnectionIdType ( restriction base: xsd:string ) NetworkIdType ( restriction base: xsd:anyURI )
Seems to just be aliases. Are there any reason for having them?
The file ogf_nsi_connection_types_v2_0.xsd import saml, but does not appear to use it. I'm guessing this is just a leftover from when the security attributes was in the file.
Not sure of the implications of removing this, but would be nice if we could avoid breakage. OTOH we will probably have to live with these things for a while, and will probably not get another chance to fix it.
Questions:
Why do we need protocol version in Header? Isn't this already contained in SOAP action?
Do we really need a file ( ogf_nsi_framework_headers_v2_0.xsd ) for one type? Not really important, just seemed like overkill.
Best regards, Henrik
Henrik Thostrup Jensen <htj at nordu.net> Software Developer, NORDUnet
_______________________________________________ nsi-wg mailing list nsi-wg@ogf.org https://www.ogf.org/mailman/listinfo/nsi-wg