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/artf6562?nav=1&selectedTab=history at Sun, 06 Nov 2022 14:39:28 GMT SourceForge : artf6562: Labelsgroup described as string
Home Projects Search
User Password Logins Disabled Help

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 artf6562 : Labelsgroup described as string
Tracker: Schema Progress
Title: Labelsgroup described as string
Description: 
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 2bis.
=========

XML:

  <nml:PortGroup id="urn:ogf:network:example.net:2010:mytrunk">
    <nml:labelgroup labeltype="http://schemas.ogf.org/nml/ethernet/2013/10/vlan">8,42,100-119</nml:labelgroup>
  </nml:PortGroup>

RDF:

  @prefix ex: <urn:ogf:network:example.net:2010> .
  @prefix nml: <http://example.ogf.org/schemas/nml/2013/03/base#>; .
  @prefix nmleth: <http://example.ogf.org/schemas/nml/2013/03/ethernet#>; .

  ex:mytrunk  a               nml:PortGroup .
  ex:mytrunk  nml:label       #12345678 .
  #12345678   nmlparam:type   "http://example.ogf.org/schemas/nml/2013/03/ethernet#vlan"  .
  #12345678   nmlparam:values "8,42,100-119" .

* The exact RDF syntax depends on the outcome of artf6495.

* The - and , are special characters in the label string.
* Technology-specific schemes must define the exact syntax of the label and the labelgroup string with parsing 
guidelines. (E.g. the WDM label string may contain the spacing)
* This proposal explicitly forbid negative labels to avoid parsing errors later.
Submitted By: Freek Dijkstra
Submitted On: 07/11/2012 3:23 PM EDT
Last Modified: 11/30/2012 8:06 AM EST
Closed: 11/30/2012 8:06 AM EST

Status / Comments Change Log Associations Attachments  
 (7 Items)
Field Old Value New Value Date Performed By
Closed 11/30/2012 11/30/2012 8:06 AM EST Jeroen van der Ham
Status 
Last Call
 
Completed
 11/30/2012 8:06 AM EST Jeroen van der Ham
Description 
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 2bis.
=========

XML:

  <nml:PortGroup id="urn:ogf:network:example.net:2010:mytrunk">
    <nml:labelgroup labeltype="http://schemas.ogf.org/nml/ethernet/2013/10/vlan"
>8,42,100-119</nml:labelgroup>
  </nml:PortGroup>

RDF:

  @prefix ex: <urn:ogf:network:example.net:2010> .
  @prefix nml: <http://example.ogf.org/schemas/nml/2013/03/base#>; .
  @prefix nmleth: <http://example.ogf.org/schemas/nml/2013/03/ethernet#>; .

  ex:mytrunk  a               nml:PortGroup .
  ex:mytrunk  nml:label       #12345678 .
  #12345678   nmlparam:type   "http://example.ogf.org/schemas/nml/2013/03/
ethernet#vlan"  .
  #12345678   nmlparam:values "8,42,100-119" .

* The exact RDF syntax depends on the outcome of artf6495.

* The - and , are special characters in the label string.
* Technology-specific schemes must define the exact syntax of the label and the 
labelgroup string with parsing guidelines. (E.g. the WDM label string may 
contain the spacing)
* This proposal explicitly forbid negative labels to avoid parsing errors later.
 
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 2bis.
=========

XML:

  <nml:PortGroup id="urn:ogf:network:example.net:2010:mytrunk">
    <nml:labelgroup labeltype="8,42,100-119http://schemas.ogf.org/nml/ethernet/2013/10/vlan"
>8,42,100-119</nml:labelgroup>;
  </nml:PortGroup>

RDF:

  @prefix ex: <urn:ogf:network:example.net:2010> .
  @prefix nml: <http://example.ogf.org/schemas/nml/2013/03/base#>; .
  @prefix nmleth: <http://example.ogf.org/schemas/nml/2013/03/ethernet#>; .

  ex:mytrunk  a               nml:PortGroup .
  ex:mytrunk  nml:label       #12345678 .
  #12345678   nmlparam:type   "http://example.ogf.org/schemas/nml/2013/03/
ethernet#vlan";  .
  #12345678   nmlparam:values "8,42,100-119" .

* The exact RDF syntax depends on the outcome of artf6495.

* The - and , are special characters in the label string.
* Technology-specific schemes must define the exact syntax of the label and the 
labelgroup string with parsing 
guidelines. (E.g. the WDM label string may contain the spacing)
* This proposal explicitly forbid negative labels to avoid parsing errors later.
08/09/2012 5:16 AM EDT Jeroen van der Ham
Priority 
4
 
2
 08/08/2012 10:18 AM EDT Freek Dijkstra
Status 
Under discussion
 
Last Call
 08/08/2012 10:18 AM EDT Freek Dijkstra
Description 
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" .

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 2bis.
=========

XML:

  <nml:PortGroup id="urn:ogf:network:example.net:2010:mytrunk">
    <nml:labelgroup labeltype="8,42,100-119http://schemas.ogf.org/nml/ethernet/2013/10/vlan"
>8,42,100-119</nml:labelgroup>;
  </nml:PortGroup>

RDF:

  @prefix ex: <urn:ogf:network:example.net:2010> .
  @prefix nml: <http://example.ogf.org/schemas/nml/2013/03/base#>; .
  @prefix nmleth: <http://example.ogf.org/schemas/nml/2013/03/ethernet#>; .

  ex:mytrunk  a               nml:PortGroup .
  ex:mytrunk  nml:label       #12345678 .
  #12345678   nmlparam:type   "http://example.ogf.org/schemas/nml/2013/03/
ethernet#vlan";  .
  #12345678   nmlparam:values "8,42,100-119" .

* The exact RDF syntax depends on the outcome of artf6495.

* The - and , are special characters in the label string.
* Technology-specific schemes must define the exact syntax of the label and the 
labelgroup string with parsing guidelines. (E.g. the WDM label string may 
contain the spacing)
* This proposal explicitly forbid negative labels to avoid parsing errors later.
 08/08/2012 10:18 AM EDT Freek Dijkstra
Title 
Group of Label syntax
 
Labelsgroup described as string
 08/08/2012 10:18 AM EDT Freek Dijkstra

 
Return
 
 
< 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/artf6562?nav=1&selectedTab=history at Sun, 06 Nov 2022 14:39:28 GMT