This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/sfmain/do/go/artf6495?nav=1&selectedTab=comments at Sun, 06 Nov 2022 14:38:00 GMT SourceForge : artf6495: Define Label syntax

Project Home

Tracker

Documents

Tasks

Source Code

Discussions

File Releases

Wiki

Project Admin

NML-WG Homepage
Search Tracker
Project: NML-WG     Trackers > Schema Progress > View Artifact
Artifact artf6495 : Define Label syntax
Tracker: Schema Progress
Title: Define Label syntax
Description:
A Label is the technology-specific value to distinguish a single data stream embedded in a larger data stream.

A Label may have the following UML properties:
* label type: a URI to refer to a technology-specific labelset
* value is one value taken from the labelset
Technology extensions of NML may define additional attributes.


The following XML syntax is proposed:

  <nml:Port id="....">
    <nml:label labeltype="http://schemas.ogf.org/nml/ethernet/2013/10/vlan">42</nml:label>
  </nml:Port>

  <nml:Port id="....">
    <nml:label labeltype="http://schemas.ogf.org/nml/wdm/2013/10/frequency">193.10~0.05</nml:label>
  </nml:Port>

(where the exact attributename: "labeltype", "type" or "encoding" is still open for debate in artf6577)


The following RDF syntax is proposed:

  @prefix  nml: <http://schemas.ogf.org/nml/base/2012/10#>; .
  @prefix  nmleth: <http://schemas.ogf.org/nml/ethernet/2012/10#>; .
  ex:myport         a                     nml:Port            .
  ex:myport         nmleth:vlan           "42"                .
  nmleth:vlan       rdfs:isSubPropertyOf  nml:Label           .

  @prefix  nml: <http://schemas.ogf.org/nml/base/2013/10#>; .
  @prefix  nmlwdm: <http://schemas.ogf.org/nml/wdm/2013/10#>; .
  ex:myport         a                     nml:Port            .
  ex:myport         nmlwdm:frequency      "193.10~0.05"       .
  nmlwdm:frequency  rdfs:isSubPropertyOf  nml:Label           .
Submitted By: Freek Dijkstra
Submitted On: 09/19/2011 9:37 PM EDT
Last Modified: 11/30/2012 8:05 AM EST
Closed: 11/30/2012 8:05 AM EST

Status / Comments Change Log Associations Attachments (1)  
Status  
Status:* Completed
Category:* – Labels / Channels
Priority: * 1
Assigned To: * None
Comments
Jeroen van der Ham: 11/30/2012 8:05 AM EST
  Action: Update
Closed set to 11/30/2012
Status changed from Last Call to Completed
Freek Dijkstra: 09/07/2012 3:29 AM EDT
  Action: Update
Status changed from Under discussion to Last Call
Freek Dijkstra: 09/06/2012 9:58 AM EDT
  Action: Update
Description changed from
A Label is the technology-specific value to distinguish a single data stream embedded in a larger data stream.

A Label may have the following UML properties:
* label type: a URI to refer to a technology-specific labelset
* value is one value taken from the labelset
Technology extensions of NML may define additional attributes.


The following XML syntax is proposed:

  <nml:Port id="....">
    <nml:label labeltype="42http://schemas.ogf.org/nml/ethernet/2013/10/vlan">42</nml:label>;
  </nml:Port>

  <nml:Port id="....">
    <nml:label labeltype="193.10~0.05http://schemas.ogf.org/nml/wdm/2013/10/frequency">193.10~0.05</nml:label>;
  </nml:Port>

(where the exact attributename: "labeltype", "type" or "encoding" is still open for debate in artf6577)


For RDF, the following two alternatives exist:

RDF Alternative 1 (unnamed label object):

  @prefix  nml: <http://schemas.ogf.org/nml/base/2012/10#>; .
  @prefix  nmleth: <http://schemas.ogf.org/nml/ethernet/2012/10#>; .
  ex:myport         a                     nml:Port            .
  ex:myport         nml:hasLabel          #28a8d3cf435        .
  #28a8d3cf435      a                     nml:Label           .
  #28a8d3cf435      nml:labeltype         nmleth:vlan         .
  #28a8d3cf435      nml:labelvalue        "42"                .

  @prefix  nml: <http://schemas.ogf.org/nml/base/2013/10#>; .
  @prefix  nmlwdm: <http://schemas.ogf.org/nml/wdm/2013/10#>; .
  ex:myport         a                     nml:Port            .
  ex:myport         nml:hasLabel          #8c6b32cec          .
  #8c6b32cec        a                     nml:Label           .
  #8c6b32cec        nml:labeltype         nmlwdm:frequency    .
  #8c6b32cec        nml:labelvalue        "193.10~0.05"       .

RDF Alternative 2 (subproperties):

  @prefix  nml: <http://schemas.ogf.org/nml/base/2012/10#>; .
  @prefix  nmleth: <http://schemas.ogf.org/nml/ethernet/2012/10#>; .
  ex:myport         a                     nml:Port            .
  ex:myport         nmleth:vlan           "42"                .
  nmleth:vlan       rdfs:isSubPropertyOf  nml:Label           .

  @prefix  nml: <http://schemas.ogf.org/nml/base/2013/10#>; .
  @prefix  nmlwdm: <http://schemas.ogf.org/nml/wdm/2013/10#>; .
  ex:myport         a                     nml:Port            .
  ex:myport         nmlwdm:frequency      "193.10~0.05"       .
  nmlwdm:frequency  rdfs:isSubPropertyOf  nml:Label           .

RDF Alternative 3:

  @prefix  nml: <http://schemas.ogf.org/nml/base/2012/10#>; .
  @prefix  nmleth: <http://schemas.ogf.org/nml/ethernet/2012/10#>; .
  ex:myport         a                     nml:Port            .
  ex:myport         nml:layerencoding     nmleth:IEEE802.3    .
  ex:myport         nml:Label             "42"                .

  @prefix  nml: <http://schemas.ogf.org/nml/base/2013/10#>; .
  @prefix  nmlwdm: <http://schemas.ogf.org/nml/wdm/2013/10#>; .
  ex:myport         a                     nml:Port            .
  ex:myport         nml:layerencoding     nmlwdm:DWDM         .
  ex:myport         nml:Label             "193.10~0.05"       .
to
A Label is the technology-specific value to distinguish a single data stream embedded in a larger data stream.

A Label may have the following UML properties:
* label type: a URI to refer to a technology-specific labelset
* value is one value taken from the labelset
Technology extensions of NML may define additional attributes.


The following XML syntax is proposed:

  <nml:Port id="....">
    <nml:label labeltype="42http://schemas.ogf.org/nml/ethernet/2013/10/vlan">42</nml:label>;
  </nml:Port>

  <nml:Port id="....">
    <nml:label labeltype="193.10~0.05http://schemas.ogf.org/nml/wdm/2013/10/frequency">193.10~0.05</nml:label>;
  </nml:Port>

(where the exact attributename: "labeltype", "type" or "encoding" is still open for debate in artf6577)


The following RDF syntax is proposed:

  @prefix  nml: <http://schemas.ogf.org/nml/base/2012/10#>; .
  @prefix  nmleth: <http://schemas.ogf.org/nml/ethernet/2012/10#>; .
  ex:myport         a                     nml:Port            .
  ex:myport         nmleth:vlan           "42"                .
  nmleth:vlan       rdfs:isSubPropertyOf  nml:Label           .

  @prefix  nml: <http://schemas.ogf.org/nml/base/2013/10#>; .
  @prefix  nmlwdm: <http://schemas.ogf.org/nml/wdm/2013/10#>; .
  ex:myport         a                     nml:Port            .
  ex:myport         nmlwdm:frequency      "193.10~0.05"       .
  nmlwdm:frequency  rdfs:isSubPropertyOf  nml:Label           .

Jason Zurawski: 08/16/2012 7:40 AM EDT
  Comment:
Beyond the debate of artf6577, the XML syntax is fine with me.  I am not an RDF expert, but I agree with Jeroen's reasoning.  
  Action: Update
Jeroen van der Ham: 08/10/2012 4:37 AM EDT
  Comment:
I dislike the unnamed object approach, because it's messy.
On the one hand I would prefer the 3rd alternative, because it's clean and makes for a simple "label" approach.
On the other hand, I'm afraid that this makes it to easy to just "forget" to add the layerencoding property. Also, it would make it impossible to have
 a Port with different layerencodings.

All in all, I think the 2nd alternative is best, it makes it impossible to leave out the encoding.
  Action: Update
Freek Dijkstra: 08/08/2012 8:14 AM EDT
  Action: Update
Priority changed from 3 to 1
Freek Dijkstra: 08/08/2012 8:12 AM EDT
  Comment:
There seems consensus on the XML syntax, but I came up with a few RDF alternatives. Please post your preferences here.
  Action: Update
Status changed from Wait for Other to Under discussion
Freek Dijkstra: 08/08/2012 8:11 AM EDT
  Action: Update
Description changed from
A Label is the technology-specific value to distinguish a single data stream embedded in a larger data stream.

A Label may have the following attributes:
* labeltype: a URI to refer to a technology-specific labelset
* value is one value taken from the labelset
Technology extensions of NML may define additional attributes.


For RDF, the following syntax is proposed:

  @prefix  nml: <http://schemas.ogf.org/nml/base/2013/10/>; .
  @prefix  nmleth: <http://schemas.ogf.org/nml/ethernet/2013/10/>; .
  #28a8d3cf435    a                 nml:Label    .
  #28a8d3cf435    nml:labeltype     nmleth:vlan  .
  #28a8d3cf435    nml:labelvalue    "42"  .

  @prefix  nml: <http://schemas.ogf.org/nml/base/2013/10/>; .
  @prefix  nmleth: <http://schemas.ogf.org/nml/ethernet/2013/10/>; .
  #8c6b32cec    a                 nml:Label    .
  #8c6b32cec    nml:labeltype     nmlwdm:frequency  .
  #8c6b32cec    nml:labelvalue    "193.10~0.05"  .


For XML, the following two syntaxes are proposed:

Proposal 1)

  <nml:label>
    <nml:parameter name="labeltype">http://schemas.ogf.org/nml/ethernet/2013/10/vlan</nml:parameter>;
    <nml:parameter name="value>42</nml:parameter>
  </nml:label>

  <nml:label>
    <nml:parameter name="labeltype">http://schemas.ogf.org/nml/wdm/2013/10/frequency</nml:parameter>;
    <nml:parameter name="unit">THz</nml:parameter>
    <nml:parameter name="spacing">0.050</nml:parameter>
    <nml:parameter name="value">193.1</nml:parameter>
  </nml:label>

Proposal 2)

  <nml:label labeltype="42http://schemas.ogf.org/nml/ethernet/2013/10/vlan">42</nml:label>;

  <nml:label labeltype="193.10~0.05http://schemas.ogf.org/nml/wdm/2013/10/frequency">193.10~0.05</nml:label>;
to
A Label is the technology-specific value to distinguish a single data stream embedded in a larger data stream.

A Label may have the following UML properties:
* label type: a URI to refer to a technology-specific labelset
* value is one value taken from the labelset
Technology extensions of NML may define additional attributes.


The following XML syntax is proposed:

  <nml:Port id="....">
    <nml:label labeltype="42http://schemas.ogf.org/nml/ethernet/2013/10/vlan">42</nml:label>;
  </nml:Port>

  <nml:Port id="....">
    <nml:label labeltype="193.10~0.05http://schemas.ogf.org/nml/wdm/2013/10/frequency">193.10~0.05</nml:label>;
  </nml:Port>

(where the exact attributename: "labeltype", "type" or "encoding" is still open for debate in artf6577)


For RDF, the following two alternatives exist:

RDF Alternative 1 (unnamed label object):

  @prefix  nml: <http://schemas.ogf.org/nml/base/2012/10#>; .
  @prefix  nmleth: <http://schemas.ogf.org/nml/ethernet/2012/10#>; .
  ex:myport         a                     nml:Port            .
  ex:myport         nml:hasLabel          #28a8d3cf435        .
  #28a8d3cf435      a                     nml:Label           .
  #28a8d3cf435      nml:labeltype         nmleth:vlan         .
  #28a8d3cf435      nml:labelvalue        "42"                .

  @prefix  nml: <http://schemas.ogf.org/nml/base/2013/10#>; .
  @prefix  nmlwdm: <http://schemas.ogf.org/nml/wdm/2013/10#>; .
  ex:myport         a                     nml:Port            .
  ex:myport         nml:hasLabel          #8c6b32cec          .
  #8c6b32cec        a                     nml:Label           .
  #8c6b32cec        nml:labeltype         nmlwdm:frequency    .
  #8c6b32cec        nml:labelvalue        "193.10~0.05"       .

RDF Alternative 2 (subproperties):

  @prefix  nml: <http://schemas.ogf.org/nml/base/2012/10#>; .
  @prefix  nmleth: <http://schemas.ogf.org/nml/ethernet/2012/10#>; .
  ex:myport         a                     nml:Port            .
  ex:myport         nmleth:vlan           "42"                .
  nmleth:vlan       rdfs:isSubPropertyOf  nml:Label           .

  @prefix  nml: <http://schemas.ogf.org/nml/base/2013/10#>; .
  @prefix  nmlwdm: <http://schemas.ogf.org/nml/wdm/2013/10#>; .
  ex:myport         a                     nml:Port            .
  ex:myport         nmlwdm:frequency      "193.10~0.05"       .
  nmlwdm:frequency  rdfs:isSubPropertyOf  nml:Label           .

RDF Alternative 3:

  @prefix  nml: <http://schemas.ogf.org/nml/base/2012/10#>; .
  @prefix  nmleth: <http://schemas.ogf.org/nml/ethernet/2012/10#>; .
  ex:myport         a                     nml:Port            .
  ex:myport         nml:layerencoding     nmleth:IEEE802.3    .
  ex:myport         nml:Label             "42"                .

  @prefix  nml: <http://schemas.ogf.org/nml/base/2013/10#>; .
  @prefix  nmlwdm: <http://schemas.ogf.org/nml/wdm/2013/10#>; .
  ex:myport         a                     nml:Port            .
  ex:myport         nml:layerencoding     nmlwdm:DWDM         .
  ex:myport         nml:Label             "193.10~0.05"       .

Freek Dijkstra: 08/07/2012 6:19 PM EDT
  Comment:
This ought to be decided upon. I'm inclined to put this in last call with proposal #2 as the choice. However, I'm waiting for our choice on artf6577.
  Action: Update
Assigned To changed from Freek Dijkstra to none (no value)
Status changed from Need proposal to Wait for Other
Freek Dijkstra: 07/11/2012 7:44 PM EDT
  Action: Update
Description changed from
A Label is the technology-specific value to distinguish a single data stream embedded in a larger data stream.

A Label may have the following attributes:
* labeltype: a URI to refer to a technology-specific labelset
* value is one value taken from the labelset
Technology extensions of NML may define additional attributes.


For RDF, the following syntax is proposed:

  @prefix  nml: <http://schemas.ogf.org/nml/base/2013/10/>; .
  @prefix  nmleth: <http://schemas.ogf.org/nml/ethernet/2013/10/>; .
  #28a8d3cf435    a                 nml:Label    .
  #28a8d3cf435    nml:labeltype     nmleth:vlan  .
  #28a8d3cf435    nml:labelvalue    "42"  .

  @prefix  nml: <http://schemas.ogf.org/nml/base/2013/10/>; .
  @prefix  nmleth: <http://schemas.ogf.org/nml/ethernet/2013/10/>; .
  #8c6b32cec    a                 nml:Label    .
  #8c6b32cec    nml:labeltype     nmlwdm:frequency  .
  #8c6b32cec    nml:labelvalue    "193.10~0.05"  .


For XML, the following two syntaxes are proposed:

Proposal 1)

  <nml:label>
    <nml:parameter name="labeltype">http://schemas.ogf.org/nml/ethernet/2013/10/vlan</nml:parameter>;
    <nml:parameter name="value>http://schemas.ogf.org/nml/wdm/2013/10/frequency</nml:parameter>;
  </nml:label>

  <nml:label>
    <nml:parameter name="labeltype">wavelength</nml:parameter>
    <nml:parameter name="unit">THz</nml:parameter>
    <nml:parameter name="spacing">0.050</nml:parameter>
    <nml:parameter name="value">193.1</nml:parameter>
  </nml:label>

Proposal 2)

  <nml:label labeltype="42http://schemas.ogf.org/nml/ethernet/2013/10/vlan">42</nml:label>;

  <nml:label labeltype="193.10~0.05http://schemas.ogf.org/nml/wdm/2013/10/frequency">193.10~0.05</nml:label>;
to
A Label is the technology-specific value to distinguish a single data stream embedded in a larger data stream.

A Label may have the following attributes:
* labeltype: a URI to refer to a technology-specific labelset
* value is one value taken from the labelset
Technology extensions of NML may define additional attributes.


For RDF, the following syntax is proposed:

  @prefix  nml: <http://schemas.ogf.org/nml/base/2013/10/>; .
  @prefix  nmleth: <http://schemas.ogf.org/nml/ethernet/2013/10/>; .
  #28a8d3cf435    a                 nml:Label    .
  #28a8d3cf435    nml:labeltype     nmleth:vlan  .
  #28a8d3cf435    nml:labelvalue    "42"  .

  @prefix  nml: <http://schemas.ogf.org/nml/base/2013/10/>; .
  @prefix  nmleth: <http://schemas.ogf.org/nml/ethernet/2013/10/>; .
  #8c6b32cec    a                 nml:Label    .
  #8c6b32cec    nml:labeltype     nmlwdm:frequency  .
  #8c6b32cec    nml:labelvalue    "193.10~0.05"  .


For XML, the following two syntaxes are proposed:

Proposal 1)

  <nml:label>
    <nml:parameter name="labeltype">http://schemas.ogf.org/nml/ethernet/2013/10/vlan</nml:parameter>;
    <nml:parameter name="value>42</nml:parameter>
  </nml:label>

  <nml:label>
    <nml:parameter name="labeltype">http://schemas.ogf.org/nml/wdm/2013/10/frequency</nml:parameter>;
    <nml:parameter name="unit">THz</nml:parameter>
    <nml:parameter name="spacing">0.050</nml:parameter>
    <nml:parameter name="value">193.1</nml:parameter>
  </nml:label>

Proposal 2)

  <nml:label labeltype="42http://schemas.ogf.org/nml/ethernet/2013/10/vlan">42</nml:label>;

  <nml:label labeltype="193.10~0.05http://schemas.ogf.org/nml/wdm/2013/10/frequency">193.10~0.05</nml:label>;

Freek Dijkstra: 07/11/2012 7:29 PM EDT
  Action: Update
Description changed from
Define label and the type of label concepts in UML, and provide examples.

Proposal is: attribute of Link or Port, with type and optional unit value. E.g.

  <nml:label type="c-vlan">42</nml:label>
  <nml:label type="wavelength" unit="nm">1500</nml:label>
to
A Label is the technology-specific value to distinguish a single data stream embedded in a larger data stream.

A Label may have the following attributes:
* labeltype: a URI to refer to a technology-specific labelset
* value is one value taken from the labelset
Technology extensions of NML may define additional attributes.


For RDF, the following syntax is proposed:

  @prefix  nml: <http://schemas.ogf.org/nml/base/2013/10/>; .
  @prefix  nmleth: <http://schemas.ogf.org/nml/ethernet/2013/10/>; .
  #28a8d3cf435    a                 nml:Label    .
  #28a8d3cf435    nml:labeltype     nmleth:vlan  .
  #28a8d3cf435    nml:labelvalue    "42"  .

  @prefix  nml: <http://schemas.ogf.org/nml/base/2013/10/>; .
  @prefix  nmleth: <http://schemas.ogf.org/nml/ethernet/2013/10/>; .
  #8c6b32cec    a                 nml:Label    .
  #8c6b32cec    nml:labeltype     nmlwdm:frequency  .
  #8c6b32cec    nml:labelvalue    "193.10~0.05"  .


For XML, the following two syntaxes are proposed:

Proposal 1)

  <nml:label>
    <nml:parameter name="labeltype">http://schemas.ogf.org/nml/ethernet/2013/10/vlan</nml:parameter>;
    <nml:parameter name="value>http://schemas.ogf.org/nml/wdm/2013/10/frequency</nml:parameter>;
  </nml:label>

  <nml:label>
    <nml:parameter name="labeltype">wavelength</nml:parameter>
    <nml:parameter name="unit">THz</nml:parameter>
    <nml:parameter name="spacing">0.050</nml:parameter>
    <nml:parameter name="value">193.1</nml:parameter>
  </nml:label>

Proposal 2)

  <nml:label labeltype="42http://schemas.ogf.org/nml/ethernet/2013/10/vlan">42</nml:label>;

  <nml:label labeltype="193.10~0.05http://schemas.ogf.org/nml/wdm/2013/10/frequency">193.10~0.05</nml:label>;

Freek Dijkstra: 07/11/2012 7:44 AM EDT
  Action: Update
Title changed from Define Label concept to Define Label syntax
Freek Dijkstra: 07/10/2012 8:33 AM EDT
  Comment:
I have recently distributed some NML example topologies to people outside of the NML developers. This included label definitions like:

  <nml:label>
    <nml:parameter name="type">http://schemas.ogf.org/nml/2013/10/ethernet/vlan</nml:parameter>;
    <nml:parameter name="values">1780-1783</nml:parameter>
  </nml:label>


Some of the feedback was that the label syntax was too verbose, and the alternative was akin to the original proposal:

  <nml:label labelType="http://schemas.ogf.org/nml/2013/10/ethernet/vlan">1780-1783</nml:label>

This in combination with a recent majority on the NML mailing list who favoured a relative flat syntax for label ranges ("1780-1783" instead of <start
>1780</start><end>1783</end>) has prompted me to see if a more simple alternative is possible. To that end, I posed two complex label definitions, to 
see how those can be described:


1. IP does not describe resource labels, but a source + destination label pair. How to describe a label pair with "source IP 145.100.124.38 and 
destination IP 193.10.252.66"?

2. WDM channel not only have a (central) frequency (or central wavelength) but also a given frequency bandwidth, the spacing. How to specify the these
 (ITU-gridless) wavelengths: "The wavelengths with 193.0, 193.1 and 193.2 central frequency with 100 GHz spacing, and another wavelength at 193.275 
central frequency with 50 GHz spacing".


After some thinking, here is a proposal:

1. <nml:label labeltype="http://schemas.ogf.org/nml/2013/10/ip/ipv4"><source>145.100.124.38</source><destination>193.10.252.66</destination></nml:
label>

2. <nml:labelgroup labeltype="http://schemas.ogf.org/nml/2013/10/dwdm/frequency">193.0-193.2±0.05,193.275±0.025</nml:label>
   (or the alternative if we don't want a non-ASCII "±" sign, and like to see the spacing rather than half the spacing):
   <nml:labelgroup labeltype="http://schemas.ogf.org/nml/2013/10/dwdm/frequency">193.0-193.2~0.1,193.275~0.05</nml:label>


In conclusion, while the above surely needs tuning, I think that the shorter variant can be done, and I don't see why not to take that approach. We 
just need to specify per labeltype what the syntax is (but we needed to do that anyway). I recommend to distinguish between nml:label and nml:
labelgroup, now that the type="value"/type="values" is no longer there to distinguish between a label and a label group.
  Action: Update
Freek Dijkstra: 05/09/2012 6:01 PM EDT
  Comment:
Here is the proposal by Roman Łapacz:

The proposal how the labels could look like is as follows (RNC format):

Label = 
    element nml:label {
        element nml:parameter {
            attribute name { "type" } &
            text
            } &
        (
            element nml:parameter {
                attribute name { text } &
                text
            } +
        ) |
        anyElement+
    } +


### taken from nmc base schema

anyElement = element * {anyThing }

anyAttribute = attribute * { text }

anyThing = 
    ( 
        anyElement | 
        anyAttribute | 
        text 
    )*


an example:

  <nml:label>
    <nml:parameter name="type">c-vlan</nml:parameter>
    <nml:parameter name="value>42</nml:parameter>
  </nml:label>

  <nml:label>
    <nml:parameter name="type">wavelength</nml:parameter>
    <nml:parameter name="unit">nm</nml:parameter>
    <nml:parameter name="spacing">25GHz</nml:parameter>
    <nml:parameter name="value">1500</nml:parameter>
  </nml:label>



By default, other nemaspaces than nml basic one are not needed but I would not forbid them. Use of a set of nml:parameter elements (flat structure) 
seems to be enough flexible to cover almost all possible cases but I can imagine a very rare requirement to have a nested structure inside nml:label, 
for example:

    <nml:label>
        <nml:paremeter name="type">xyz</nml:parameter>
        <nml-ext:something_1>
            <nml-ext:something_2>
                ...
            </nml-ext:something_2>
        </nml-ext:something_1>
    </nml:label>

(that is why I've added anyElement in the RNC snippet)

If you are 100% sure that such a requirement will not come up I'm fine to remove this extension possibility.
  Action: Update
Freek Dijkstra: 03/29/2012 12:37 PM EDT
  Action: Update
Description changed from
Define Label and LabelType concepts in uML schemU
to
Define label and the type of label concepts in UML, and provide examples.

Proposal is: attribute of Link or Port, with type and optional unit value. E.g.

  <nml:label type="c-vlan">42</nml:label>
  <nml:label type="wavelength" unit="nm">1500</nml:label>

Freek Dijkstra: 03/29/2012 11:53 AM EDT
  Comment:
I'll take this.
  Action: Update
Assigned To changed from Jeroen van der Ham to Freek Dijkstra
Freek Dijkstra: 03/28/2012 10:42 AM EDT
  Action: Update
Status changed from Under discussion to Need proposal
Jeroen van der Ham: 09/20/2011 9:29 AM EDT
  Action: Update
Status changed from New to Work in Progress
Jeroen van der Ham: 09/20/2011 9:25 AM EDT
  Action: Update
Assigned To set to Jeroen van der Ham
Freek Dijkstra: 09/19/2011 10:16 PM EDT
  Comment:
FYI, a picture of G.800 on Port Forwarding.

How does this map to NML “Port”?
How does this relate to NSI “STP”?
  Attachment: g800.png (30.71 KB)
  Action: Update
Added an attachment.
Freek Dijkstra: 09/19/2011 9:39 PM EDT
  Action: Update
Priority changed from 4 to 3
Freek Dijkstra: 09/19/2011 9:37 PM EDT
  Action: Create


 
 
 
< Previous
 
 
Next >
 


The Open Grid Forum Contact Webmaster | Report a problem | GridForge Help
This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/sfmain/do/go/artf6495?nav=1&selectedTab=comments at Sun, 06 Nov 2022 14:38:01 GMT