The PortGroup and LinkGroup concepts require a "set of labels" concept. E.g. "VLAN 8,42,100-119". Here are two proposals how to represent this. Please pick one (personal preference, XML/RDF-fetish, or throwing a dice are valid selection mechanisms for today). Option 1. ========= XML: <nml:PortGroup id="urn:ogf:network:example.net:2010:mytrunk"> <nml:label> <nml:parameter name="type">vlan</nml:parameter> <nml:parameter name="set"> <nml:parameter name="value">8</nml:parameter> <nml:parameter name="value">42</nml:parameter> <nml:paramater name="range"> <nml:paramater name="start">100</nml:paramater> <nml:paramater name="end">119</nml:paramater> </nml:paramater> </nml:parameter> </nml:label> </nml:PortGroup> RDF: @prefix ex: <urn:ogf:network:example.net:2010> . @prefix nml: <http://example.ogf.org/schemas/nml/base/201303/> . @prefix nmlparam: <http://example.ogf.org/schemas/nml/param/201303/> . ex:mytrunk a nml:PortGroup . ex:mytrunk nml:label #12345678 . #12345678 nmlparam:type "vlan" . #12345678 nmlparam:set #9876543 . #9876543 nmlparam:value "8" . #9876543 nmlparam:value "42" . #9876543 nmlparam:range #asdfghj . #asdfghj nmlparam:start "100" . #asdfghj nmlparam:start "119" . Option 2. ========= XML: <nml:PortGroup id="urn:ogf:network:example.net:2010:mytrunk"> <nml:label> <nml:parameter name="type">vlan</nml:parameter> <nml:parameter name="values">8,42,100-119</nml:paramater> </nml:label> </nml:PortGroup> RDF: @prefix ex: <urn:ogf:network:example.net:2010> . @prefix nml: <http://example.ogf.org/schemas/nml/base/201303/> . @prefix nmlparam: <http://example.ogf.org/schemas/nml/param/201303/> . ex:mytrunk a nml:PortGroup . ex:mytrunk nml:label #12345678 . #12345678 nmlparam:type "vlan" . #12345678 nmlparam:values "8,42,100-119" . Thanks, Freek
Hi all, I have no idea how easy or hard it is to implement a parser for the latter one, but the first one seems to be a safer bet. Jeroen. On 28 Jun 2012, at 15:45, Freek Dijkstra wrote:
The PortGroup and LinkGroup concepts require a "set of labels" concept. E.g. "VLAN 8,42,100-119".
Here are two proposals how to represent this. Please pick one (personal preference, XML/RDF-fetish, or throwing a dice are valid selection mechanisms for today).
Option 1. =========
XML:
<nml:PortGroup id="urn:ogf:network:example.net:2010:mytrunk"> <nml:label> <nml:parameter name="type">vlan</nml:parameter> <nml:parameter name="set"> <nml:parameter name="value">8</nml:parameter> <nml:parameter name="value">42</nml:parameter> <nml:paramater name="range"> <nml:paramater name="start">100</nml:paramater> <nml:paramater name="end">119</nml:paramater> </nml:paramater> </nml:parameter> </nml:label> </nml:PortGroup>
RDF:
@prefix ex: <urn:ogf:network:example.net:2010> . @prefix nml: <http://example.ogf.org/schemas/nml/base/201303/> . @prefix nmlparam: <http://example.ogf.org/schemas/nml/param/201303/> .
ex:mytrunk a nml:PortGroup . ex:mytrunk nml:label #12345678 . #12345678 nmlparam:type "vlan" . #12345678 nmlparam:set #9876543 . #9876543 nmlparam:value "8" . #9876543 nmlparam:value "42" . #9876543 nmlparam:range #asdfghj . #asdfghj nmlparam:start "100" . #asdfghj nmlparam:start "119" .
Option 2. =========
XML:
<nml:PortGroup id="urn:ogf:network:example.net:2010:mytrunk"> <nml:label> <nml:parameter name="type">vlan</nml:parameter> <nml:parameter name="values">8,42,100-119</nml:paramater> </nml:label> </nml:PortGroup>
RDF:
@prefix ex: <urn:ogf:network:example.net:2010> . @prefix nml: <http://example.ogf.org/schemas/nml/base/201303/> . @prefix nmlparam: <http://example.ogf.org/schemas/nml/param/201303/> .
ex:mytrunk a nml:PortGroup . ex:mytrunk nml:label #12345678 . #12345678 nmlparam:type "vlan" . #12345678 nmlparam:values "8,42,100-119" .
Thanks, Freek
_______________________________________________ nml-wg mailing list nml-wg@ogf.org https://www.ogf.org/mailman/listinfo/nml-wg
Option 2 is how OSCARS currently works today, and I believe it works well. I would vote to go with that for 'ease of implementation' :) -jason On 6/28/12 9:45 AM, thus spake Freek Dijkstra:
The PortGroup and LinkGroup concepts require a "set of labels" concept. E.g. "VLAN 8,42,100-119".
Here are two proposals how to represent this. Please pick one (personal preference, XML/RDF-fetish, or throwing a dice are valid selection mechanisms for today).
Option 1. =========
XML:
<nml:PortGroup id="urn:ogf:network:example.net:2010:mytrunk"> <nml:label> <nml:parameter name="type">vlan</nml:parameter> <nml:parameter name="set"> <nml:parameter name="value">8</nml:parameter> <nml:parameter name="value">42</nml:parameter> <nml:paramater name="range"> <nml:paramater name="start">100</nml:paramater> <nml:paramater name="end">119</nml:paramater> </nml:paramater> </nml:parameter> </nml:label> </nml:PortGroup>
RDF:
@prefix ex:<urn:ogf:network:example.net:2010> . @prefix nml:<http://example.ogf.org/schemas/nml/base/201303/> . @prefix nmlparam:<http://example.ogf.org/schemas/nml/param/201303/> .
ex:mytrunk a nml:PortGroup . ex:mytrunk nml:label #12345678 . #12345678 nmlparam:type "vlan" . #12345678 nmlparam:set #9876543 . #9876543 nmlparam:value "8" . #9876543 nmlparam:value "42" . #9876543 nmlparam:range #asdfghj . #asdfghj nmlparam:start "100" . #asdfghj nmlparam:start "119" .
Option 2. =========
XML:
<nml:PortGroup id="urn:ogf:network:example.net:2010:mytrunk"> <nml:label> <nml:parameter name="type">vlan</nml:parameter> <nml:parameter name="values">8,42,100-119</nml:paramater> </nml:label> </nml:PortGroup>
RDF:
@prefix ex:<urn:ogf:network:example.net:2010> . @prefix nml:<http://example.ogf.org/schemas/nml/base/201303/> . @prefix nmlparam:<http://example.ogf.org/schemas/nml/param/201303/> .
ex:mytrunk a nml:PortGroup . ex:mytrunk nml:label #12345678 . #12345678 nmlparam:type "vlan" . #12345678 nmlparam:values "8,42,100-119" .
Thanks, Freek
W dniu 2012-06-28 16:17, Jason Zurawski pisze:
Option 2 is how OSCARS currently works today, and I believe it works well. I would vote to go with that for 'ease of implementation' :)
Agree, besides parameter inside parameter does not look nice to me. In case of a very simple parameter nested structure I would prefer NM/NMC approach <parameters><parameter/></parameters>. More complex structures may be built in a specific namespaces. Roman
-jason
On 6/28/12 9:45 AM, thus spake Freek Dijkstra:
The PortGroup and LinkGroup concepts require a "set of labels" concept. E.g. "VLAN 8,42,100-119".
Here are two proposals how to represent this. Please pick one (personal preference, XML/RDF-fetish, or throwing a dice are valid selection mechanisms for today).
Option 1. =========
XML:
<nml:PortGroup id="urn:ogf:network:example.net:2010:mytrunk"> <nml:label> <nml:parameter name="type">vlan</nml:parameter> <nml:parameter name="set"> <nml:parameter name="value">8</nml:parameter> <nml:parameter name="value">42</nml:parameter> <nml:paramater name="range"> <nml:paramater name="start">100</nml:paramater> <nml:paramater name="end">119</nml:paramater> </nml:paramater> </nml:parameter> </nml:label> </nml:PortGroup>
RDF:
@prefix ex:<urn:ogf:network:example.net:2010> . @prefix nml:<http://example.ogf.org/schemas/nml/base/201303/> . @prefix nmlparam:<http://example.ogf.org/schemas/nml/param/201303/> .
ex:mytrunk a nml:PortGroup . ex:mytrunk nml:label #12345678 . #12345678 nmlparam:type "vlan" . #12345678 nmlparam:set #9876543 . #9876543 nmlparam:value "8" . #9876543 nmlparam:value "42" . #9876543 nmlparam:range #asdfghj . #asdfghj nmlparam:start "100" . #asdfghj nmlparam:start "119" .
Option 2. =========
XML:
<nml:PortGroup id="urn:ogf:network:example.net:2010:mytrunk"> <nml:label> <nml:parameter name="type">vlan</nml:parameter> <nml:parameter name="values">8,42,100-119</nml:paramater> </nml:label> </nml:PortGroup>
RDF:
@prefix ex:<urn:ogf:network:example.net:2010> . @prefix nml:<http://example.ogf.org/schemas/nml/base/201303/> . @prefix nmlparam:<http://example.ogf.org/schemas/nml/param/201303/> .
ex:mytrunk a nml:PortGroup . ex:mytrunk nml:label #12345678 . #12345678 nmlparam:type "vlan" . #12345678 nmlparam:values "8,42,100-119" .
Thanks, Freek
nml-wg mailing list nml-wg@ogf.org https://www.ogf.org/mailman/listinfo/nml-wg
participants (4)
-
Freek Dijkstra -
Jason Zurawski -
Jeroen van der Ham -
Roman Łapacz