[Nsi-wg] Adding service definition elements to NML

[Jeroen van der Ham]

Hi,

On 28 Oct 2013, at 16:31, John MacAuley <john.macauley at surfnet.nl> wrote:
> Our decision in Madrid was to associate a list of applicable service definitions against an STP within our topology definitions.  The question I have is a that of procedure.  At the moment there is the base NML specification (nmlbase.xsd) which we should never have to touch.  Then there is the NML extensions for NSI (nsi-ext.xsd) which contains definitions for our NSA and Service entries.  It is my assumption that we should we be expanding on the "NML extensions for NSI" document instead of creating an additional "NSI extensions for NML extensions for NSI".  Do people agree?

The "NML Extensions for NSI” document is still in draft, so it can be changed. If you have suggestions, patches or text are welcome!

> I had a look through the NML base definitions and it looks like we could put a serviceDefinition element into the base PortType definition through the XML ANY held in the BasePortContent group.  However, we are in a bit of a pickle for PortGroup because it does not contain a direct child XML ANY element.  Therefore, we will need to access indirectly through a Port element, which may confuse the meaning of PortGroup a little bit.  I have included a mock example below:

This seems like an error in the NML spec, as the PortGroup element (like other elements in NML) should be extensible.

> I believe that given the current limitations of the NML base schema we should probably use the second mechanism.  It seem to fit a bit better and will contain the ServiceDefinition element to a single location on the Topology element.

I have no preference for either.
I’m happy to see that someone is finally giving the NML base schema the scrutiny it has needed for some time. Any changes you find necessary to make this into a proper schema are very welcome.

Jeroen.