Call on April 19th

newer
Label proposal (was: Call on April...

Jeroen van der Ham

18 Apr 2012 18 Apr '12

11:29 a.m.

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.

Show replies by date

Jason Zurawski

18 Apr 18 Apr

1:52 p.m.

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 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

Roman Łapacz

19 Apr 19 Apr

1:27 p.m.

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) 42 1500 or 2) use of tag namespaces to indicate a technology nml-eth:label42 42 nml-wv:label1500 1500 nm or 3) use of attribute namespaces to introduce tech related attributes 42 1500 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

Freek Dijkstra

2:56 p.m.

Roman Łapacz wrote:

...

...
- Label Proposal

I'm thinking about 3 options:

1)

42 1500

or 2)

use of tag namespaces to indicate a technology

nml-eth:label42 42

nml-wv:label1500 1500 nm

or 3)

use of attribute namespaces to introduce tech related attributes

42 1500

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

Roman Łapacz

3:16 p.m.

W dniu 2012-04-19 16:56, Freek Dijkstra pisze:

...

Roman Łapacz wrote:

...
...
- Label Proposal I'm thinking about 3 options:

1)

42 1500

or 2)

use of tag namespaces to indicate a technology

nml-eth:label42 42

nml-wv:label1500 1500 nm

or 3)

use of attribute namespaces to introduce tech related attributes

42 1500 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? 42 42 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

4552

Age (days ago)

4553

Last active (days ago)

List overview

Download

4 comments

4 participants

participants (4)

Freek Dijkstra
Jason Zurawski
Jeroen van der Ham
Roman Łapacz