This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/go/artf6577?nav=1 at Fri, 04 Nov 2022 23:45:00 GMT SourceForge : artf6577: layer and label encoding terminology

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 artf6577 : layer and label encoding terminology
Tracker: Schema Progress
Title: layer and label encoding terminology
Description:
NML has currently a one-to-one relation between the layer encoding (a URI to define the layer of sublayer of a specific 
Port of Link) and the label type (a URI to define the resource label of a technology).

Proposal: (was: Option 4). Use "encoding" for layer encoding and "labeltype" for label type

 <nml:Port id="....">
    <nml:encoding>http://schemas.ogf.org/nml/2013/10/ethernet#802.3</nml:encoding>;
    <nml:label labeltype="http://schemas.ogf.org/nml/2013/10/ethernet#vlan">1780</nml:label>
 </nml:Port>
Submitted By: Freek Dijkstra
Submitted On: 07/27/2012 12:46 PM EDT
Last Modified: 11/30/2012 8:03 AM EST
Closed: 11/30/2012 8:03 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:03 AM EST Jeroen van der Ham
Status
Last Call
Completed
11/30/2012 8:03 AM EST Jeroen van der Ham
Status
Under discussion
Last Call
09/07/2012 3:30 AM EDT Freek Dijkstra
Description
NML has currently a one-to-one relation between the layer encoding (a URI to 
define the layer of sublayer of a specific Port of Link) and the label type (a 
URI to define the resource label of a technology).

The following options exist to denote the layer encoding and label type:

Option 1. Use "encoding" for both layer encoding and label type:

 <nml:Port id="....">
    <nml:encoding>http://schemas.ogf.org/nml/2013/10/ethernet#802.3</nml:
encoding>;
    <nml:label encoding="http://schemas.ogf.org/nml/2013/10/ethernet#vlan">1780<
/nml:label>
 </nml:Port>

Option 2. Use "layer" for layer encoding and "encoding" for label type:

 <nml:Port id="....">
    <nml:layer>http://schemas.ogf.org/nml/2013/10/ethernet#802.3</nml:encoding>;
    <nml:label encoding="http://schemas.ogf.org/nml/2013/10/ethernet#vlan">1780<
/nml:label>
 </nml:Port>

Option 3. Use "encoding" for layer encoding and "labeltype" for label type

 <nml:Port id="....">
    <nml:encoding>http://schemas.ogf.org/nml/2013/10/ethernet#802.3</nml:
encoding>;
    <nml:label type="http://schemas.ogf.org/nml/2013/10/ethernet#vlan">1780</nml
:label>
 </nml:Port>

Option 4. Use "encoding" for layer encoding and "labeltype" for label type

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

etc. etc. (there are numerous options)
NML has currently a one-to-one relation between the layer encoding (a URI to 
define the layer of sublayer of a specific Port of Link) and the label type (a 
URI to define the resource label of a technology).

Proposal: (was: Option 4). Use "encoding" for layer encoding and "labeltype" for
 label type

 <nml:Port id="....">
    <nml:encoding>http://schemas.ogf.org/nml/2013/10/ethernet#802.3</nml:
encoding>;
    <nml:label labeltype="http://schemas.ogf.org/nml/2013/10/ethernet#vlan">1780
</nml:label>;
 </nml:Port>
09/06/2012 9:50 AM EDT Freek Dijkstra
Status
Last Call
Under discussion
08/09/2012 11:46 AM EDT Freek Dijkstra
Priority
3
2
08/08/2012 10:28 AM EDT Freek Dijkstra
Status
Under discussion
Last Call
08/08/2012 10:28 AM EDT Freek Dijkstra

 
 
 
< 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/go/artf6577?nav=1 at Fri, 04 Nov 2022 23:45:05 GMT