Hi all, We have another call on April 19th UTC 15:00 - Ams 17:00 - Eastern 11:00 - Pacific 8:00 Call: +1-734-615-7474 (Please use if you do not pay for Long Distance) or +1-866-411-0013 (toll free US/Canada Only) Enter access code: 0186145 - urn:ogf:network status - conclusion from id idref - Label Proposal - XML Schema language - ordered list in RDF
Also reminder, following tickets are in last call:
https://forge.ogf.org/sf/go/artf6537 - implicit definitions and parser behavior https://forge.ogf.org/sf/go/artf6534 - Case https://forge.ogf.org/sf/go/artf6539 - Inbound/Outbound Ports https://forge.ogf.org/sf/go/artf6538 - Verbs in relation-names https://forge.ogf.org/sf/go/artf6545 - isSerialCompoundLink https://forge.ogf.org/sf/go/artf6550 - isSource/isSink relations
Jeroen.
Hi All; I will be unable to attend due to travel. Thanks; -jason On Apr 18, 2012, at 6:29 AM, Jeroen van der Ham <vdham@uva.nl> wrote:
Hi all,
We have another call on April 19th
UTC 15:00 - Ams 17:00 - Eastern 11:00 - Pacific 8:00
Call: +1-734-615-7474 (Please use if you do not pay for Long Distance) or +1-866-411-0013 (toll free US/Canada Only) Enter access code: 0186145
- urn:ogf:network status - conclusion from id idref - Label Proposal - XML Schema language - ordered list in RDF
Also reminder, following tickets are in last call:
https://forge.ogf.org/sf/go/artf6537 - implicit definitions and parser behavior https://forge.ogf.org/sf/go/artf6534 - Case https://forge.ogf.org/sf/go/artf6539 - Inbound/Outbound Ports https://forge.ogf.org/sf/go/artf6538 - Verbs in relation-names https://forge.ogf.org/sf/go/artf6545 - isSerialCompoundLink https://forge.ogf.org/sf/go/artf6550 - isSource/isSink relations
Jeroen.
_______________________________________________ nml-wg mailing list nml-wg@ogf.org https://www.ogf.org/mailman/listinfo/nml-wg
W dniu 2012-04-18 13:29, Jeroen van der Ham pisze:
Hi all,
We have another call on April 19th
UTC 15:00 - Ams 17:00 - Eastern 11:00 - Pacific 8:00
Call: +1-734-615-7474 (Please use if you do not pay for Long Distance) or +1-866-411-0013 (toll free US/Canada Only) Enter access code: 0186145
- urn:ogf:network status - conclusion from id idref - Label Proposal
I'm thinking about 3 options: 1) <nml:label type="c-vlan">42</nml:label> <nml:label type="wavelength" unit="nm">1500</nml:label> or 2) use of tag namespaces to indicate a technology <nml-eth:label>42</nml-eth:label> <nml:parameter name="vlan">42</nml:parameter> </nml-eth:label> <nml-wv:label>1500</nml-wv:label> <nml:parameter name="wavelength">1500</nml:parameter> <nml:parameter name="unit">nm</nml:parameter> </nml-wv:label> or 3) use of attribute namespaces to introduce tech related attributes <nml:label nml:type="c-vlan">42</nml:label> <nml:label nml:type="wavelength" nml-wv:unit="nm">1500</nml:label> R.
- XML Schema language - ordered list in RDF
Also reminder, following tickets are in last call: https://forge.ogf.org/sf/go/artf6537 - implicit definitions and parser behavior https://forge.ogf.org/sf/go/artf6534 - Case https://forge.ogf.org/sf/go/artf6539 - Inbound/Outbound Ports https://forge.ogf.org/sf/go/artf6538 - Verbs in relation-names https://forge.ogf.org/sf/go/artf6545 - isSerialCompoundLink https://forge.ogf.org/sf/go/artf6550 - isSource/isSink relations Jeroen.
_______________________________________________ nml-wg mailing list nml-wg@ogf.org https://www.ogf.org/mailman/listinfo/nml-wg
Roman Łapacz wrote:
- Label Proposal
I'm thinking about 3 options:
1)
<nml:label type="c-vlan">42</nml:label> <nml:label type="wavelength" unit="nm">1500</nml:label>
or 2)
use of tag namespaces to indicate a technology
<nml-eth:label>42</nml-eth:label> <nml:parameter name="vlan">42</nml:parameter> </nml-eth:label>
<nml-wv:label>1500</nml-wv:label> <nml:parameter name="wavelength">1500</nml:parameter> <nml:parameter name="unit">nm</nml:parameter> </nml-wv:label>
or 3)
use of attribute namespaces to introduce tech related attributes
<nml:label nml:type="c-vlan">42</nml:label> <nml:label nml:type="wavelength" nml-wv:unit="nm">1500</nml:label>
I find 2 a bit confusing because of the double value (both as label and as parameter), which makes me wonder if there is a situation where they can be different. I have no preference for either 1 or 3 (I see 3 as an extension of 1). The only think that is important to me is that it is possible to define multiple label types per technology. For example Ethernet can define VLANs, ISID and MAC; DWDM can define wavelengths and wavelength groups; SDH can define STS, TUG and VTG; ATM can define VPI and VCI, etc. Regards, Freek
W dniu 2012-04-19 16:56, Freek Dijkstra pisze:
Roman Łapacz wrote:
- Label Proposal I'm thinking about 3 options:
1)
<nml:label type="c-vlan">42</nml:label> <nml:label type="wavelength" unit="nm">1500</nml:label>
or 2)
use of tag namespaces to indicate a technology
<nml-eth:label>42</nml-eth:label> <nml:parameter name="vlan">42</nml:parameter> </nml-eth:label>
<nml-wv:label>1500</nml-wv:label> <nml:parameter name="wavelength">1500</nml:parameter> <nml:parameter name="unit">nm</nml:parameter> </nml-wv:label>
or 3)
use of attribute namespaces to introduce tech related attributes
<nml:label nml:type="c-vlan">42</nml:label> <nml:label nml:type="wavelength" nml-wv:unit="nm">1500</nml:label> I find 2 a bit confusing because of the double value (both as label and as parameter), which makes me wonder if there is a situation where they can be different.
update? <nml-eth:label type="vlan"> <nml:parameter name="id">42</nml:parameter> </nml-eth:label> <nml-eth:label type="mac"> <nml:parameter name="address">42</nml:parameter> </nml-eth:label> Roman
I have no preference for either 1 or 3 (I see 3 as an extension of 1).
The only think that is important to me is that it is possible to define multiple label types per technology. For example Ethernet can define VLANs, ISID and MAC; DWDM can define wavelengths and wavelength groups; SDH can define STS, TUG and VTG; ATM can define VPI and VCI, etc.
Regards, Freek
participants (4)
-
Freek Dijkstra -
Jason Zurawski -
Jeroen van der Ham -
Roman Łapacz