This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/go/artf6575?nav=1 at Fri, 04 Nov 2022 23:45:10 GMT SourceForge : artf6575: NML relation in RDF
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 artf6575 : NML relation in RDF
Tracker: Schema Progress
Title: NML relation in RDF
Description: 
RDF regards an NML relations as any other property. In order to distinguish in RDF between 

    <nml:Relation type="http://schemas.ogf.org/nml/2013/10/base#hasInboundPort">
and
    <nml:hasInboundPort>

Propose: RDF needs to add the following triplet for all NML relations:
    nml:hasInboundPort rdfs:subPropertyOf nml:Relation .

Note: a NML version 1 compliant client does not need to add the these triplets for relations defined in version 1 of NML
, but it MUST include them for other relations if they are used in the description. Eg. if it is using a relation 
defined in the experimental extension schema.


Example 1: the following two syntaxes are equivalent.

RDF:

 @prefix nml: <http://schemas.ogf.org/nml/2013/10/base#>; .
 nml:hasInboundPort rdfs:subPropertyOf‎nml:Relation .
 urn:ogf:network:example.net:2012:mynode a nml:Node .
 urn:ogf:network:example.net:2012:mynode nml:hasInboundPort urn:ogf:network:example.net:2012:myport .
 urn:ogf:network:example.net:2012:myport a nml:Port .

XML:

 <nml:Node id="urn:ogf:network:example.net:2012:mynode">
   <nml:Relation type="http://schemas.ogf.org/nml/2013/10/base#hasInboundPort">
     <nml:Port idRef="urn:ogf:network:example.net:2012:myport" />
   </nml:Relation>
 </nml:Node>

Example 2: the following two syntaxes are equivalent (note the missing "nml:hasInboundPort rdfs:subPropertyOf‎nml:
Relation ." line)

RDF:

 @prefix nml: <http://schemas.ogf.org/nml/2013/10/base#>; .
 urn:ogf:network:example.net:2012:mynode a nml:Node .
 urn:ogf:network:example.net:2012:mynode nml:hasInboundPort urn:ogf:network:example.net:2012:myport .
 urn:ogf:network:example.net:2012:myport a nml:Port .

XML:

 <nml:Node id="urn:ogf:network:example.net:2012:mynode">
   <nml:hasInboundPort">
     <nml:Port idRef="urn:ogf:network:example.net:2012:myport" />
   </nml:hasInboundPort>
 </nml:Node>
Submitted By: Freek Dijkstra
Submitted On: 07/18/2012 10:53 AM EDT
Last Modified: 11/30/2012 8:00 AM EST
Closed: 11/30/2012 8:00 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:00 AM EST Jeroen van der Ham
Status 
Last Call
 
Completed
 11/30/2012 8:00 AM EST Jeroen van der Ham
Status 
Under discussion
 
Last Call
 09/07/2012 3:29 AM EDT Freek Dijkstra
Description 
RDF regards an NML relations as any other property. In order to distinguish in 
RDF between 

    <nml:Relation type="http://schemas.ogf.org/nml/2013/10/base#hasInboundPort">

and
    <nml:hasInboundPort>

Propose: RDF needs to add the following triplet for all NML relations:
    nml:hasInboundPort a nml:Relation .

Note: a NML version 1 compliant client does not need to add the these triplets 
for relations defined in version 1 of NML, but it MUST include them for other 
relations if they are used in the description. Eg. if it is using a relation 
defined in the experimental extension schema.


Example 1: the following two syntaxes are equivalent.

RDF:

 @prefix nml: <http://schemas.ogf.org/nml/2013/10/base#>; .
 nml:hasInboundPort a nml:Relation .
 urn:ogf:network:example.net:2012:mynode a nml:Node .
 urn:ogf:network:example.net:2012:mynode nml:hasInboundPort urn:ogf:network:
example.net:2012:myport .
 urn:ogf:network:example.net:2012:myport a nml:Port .

XML:

 <nml:Node id="urn:ogf:network:example.net:2012:mynode">
   <nml:Relation type="http://schemas.ogf.org/nml/2013/10/base#hasInboundPort">
     <nml:Port idRef="urn:ogf:network:example.net:2012:myport" />
   </nml:Relation>
 </nml:Node>

Example 2: the following two syntaxes are equivalent (note the missing "nml:
hasInboundPort a nml:Relation ." line)

RDF:

 @prefix nml: <http://schemas.ogf.org/nml/2013/10/base#>; .
 urn:ogf:network:example.net:2012:mynode a nml:Node .
 urn:ogf:network:example.net:2012:mynode nml:hasInboundPort urn:ogf:network:
example.net:2012:myport .
 urn:ogf:network:example.net:2012:myport a nml:Port .

XML:

 <nml:Node id="urn:ogf:network:example.net:2012:mynode">
   <nml:hasInboundPort">
     <nml:Port idRef="urn:ogf:network:example.net:2012:myport" />
   </nml:hasInboundPort>
 </nml:Node>
 
RDF regards an NML relations as any other property. In order to distinguish in 
RDF between 

    <nml:Relation type="http://schemas.ogf.org/nml/2013/10/base#hasInboundPort">;

and
    <nml:hasInboundPort>

Propose: RDF needs to add the following triplet for all NML relations:
    nml:hasInboundPort rdfs:subPropertyOf nml:Relation .

Note: a NML version 1 compliant client does not need to add the these triplets 
for relations defined in version 1 of NML, but it MUST include them for other 
relations if they are used in the description. Eg. if it is using a relation 
defined in the experimental extension schema.


Example 1: the following two syntaxes are equivalent.

RDF:

 @prefix nml: <http://schemas.ogf.org/nml/2013/10/base#>; .
 nml:hasInboundPort rdfs:subPropertyOf‎nml:Relation .
 urn:ogf:network:example.net:2012:mynode a nml:Node .
 urn:ogf:network:example.net:2012:mynode nml:hasInboundPort urn:ogf:network:
example.net:2012:myport .
 urn:ogf:network:example.net:2012:myport a nml:Port .

XML:

 <nml:Node id="urn:ogf:network:example.net:2012:mynode">
   <nml:Relation type="http://schemas.ogf.org/nml/2013/10/base#hasInboundPort">;
     <nml:Port idRef="urn:ogf:network:example.net:2012:myport" />
   </nml:Relation>
 </nml:Node>

Example 2: the following two syntaxes are equivalent (note the missing "nml:
hasInboundPort rdfs:subPropertyOf‎nml:Relation ." line)

RDF:

 @prefix nml: <http://schemas.ogf.org/nml/2013/10/base#>; .
 urn:ogf:network:example.net:2012:mynode a nml:Node .
 urn:ogf:network:example.net:2012:mynode nml:hasInboundPort urn:ogf:network:
example.net:2012:myport .
 urn:ogf:network:example.net:2012:myport a nml:Port .

XML:

 <nml:Node id="urn:ogf:network:example.net:2012:mynode">
   <nml:hasInboundPort">
     <nml:Port idRef="urn:ogf:network:example.net:2012:myport" />
   </nml:hasInboundPort>
 </nml:Node>
 09/06/2012 9:53 AM EDT Freek Dijkstra
Status 
Need proposal
 
Under discussion
 09/05/2012 9:35 AM EDT Freek Dijkstra
Description 
RDF does not differentiate between NML relations and other relations.

A) If a relation is translated from RDF to XML, how to determine if the relation
 is a NML relation or not?

E.g. the following code 

 @prefix nml: <http://schemas.ogf.org/nml/2013/10/base#>;
 @prefix nmlrel: <http://schemas.ogf.org/nml/2013/10/relation#>;
 urn:ogf:network:example.net:2012:mynode a nml:Node
 urn:ogf:network:example.net:2012:mynode nmlrel:hasInboundPort urn:ogf:network:
example.net:2012:myport
 urn:ogf:network:example.net:2012:myport a nml:Port

Can either translate to:

 <nml:Node id="urn:ogf:network:example.net:2012:mynode">
   <nmlrel:hasInboundPort>
     <nml:Port idRef="urn:ogf:network:example.net:2012:myport" />
   </nmlrel:hasInboundPort>
 </nml:Node>

or to:

 <nml:Node id="urn:ogf:network:example.net:2012:mynode">
   <nml:Relation type="http://schemas.ogf.org/nml/2013/10/relation#
hasInboundPort">
     <nml:Port idRef="urn:ogf:network:example.net:2012:myport" />
   </nml:Relation>
 </nml:Node>

Options:

1. Use nml:Relation for relations in the http://schemas.ogf.org/nml namespace.
2. Use nml:Relation for a set of predefined relations.
3. Add some syntax to RDF to differentiate between a nml:Relation and some other
 relation
4. Never use a nml:Relation, even not for relations in the http://schemas.ogf.
org/nml namespace.
5. Always use a nml:Relation, even for relations outside the http://schemas.ogf.
org/nml namespace.

RDF regards an NML relations as any other property. In order to distinguish in 
RDF between 

    <nml:Relation type="http://schemas.ogf.org/nml/2013/10/base#hasInboundPort">;

and
    <nml:hasInboundPort>

Propose: RDF needs to add the following triplet for all NML relations:
    nml:hasInboundPort a nml:Relation .

Note: a NML version 1 compliant client does not need to add the these triplets 
for relations defined in version 1 of NML, but it MUST include them for other 
relations if they are used in the description. Eg. if it is using a relation 
defined in the experimental extension schema.


Example 1: the following two syntaxes are equivalent.

RDF:

 @prefix nml: <http://schemas.ogf.org/nml/2013/10/base#>; .
 nml:hasInboundPort a nml:Relation .
 urn:ogf:network:example.net:2012:mynode a nml:Node .
 urn:ogf:network:example.net:2012:mynode nml:hasInboundPort urn:ogf:network:
example.net:2012:myport .
 urn:ogf:network:example.net:2012:myport a nml:Port .

XML:

 <nml:Node id="urn:ogf:network:example.net:2012:mynode">
   <nml:Relation type="http://schemas.ogf.org/nml/2013/10/base#hasInboundPort">;
     <nml:Port idRef="urn:ogf:network:example.net:2012:myport" />
   </nml:Relation>
 </nml:Node>

Example 2: the following two syntaxes are equivalent (note the missing "nml:
hasInboundPort a nml:Relation ." line)

RDF:

 @prefix nml: <http://schemas.ogf.org/nml/2013/10/base#>; .
 urn:ogf:network:example.net:2012:mynode a nml:Node .
 urn:ogf:network:example.net:2012:mynode nml:hasInboundPort urn:ogf:network:
example.net:2012:myport .
 urn:ogf:network:example.net:2012:myport a nml:Port .

XML:

 <nml:Node id="urn:ogf:network:example.net:2012:mynode">
   <nml:hasInboundPort">
     <nml:Port idRef="urn:ogf:network:example.net:2012:myport" />
   </nml:hasInboundPort>
 </nml:Node>
 09/05/2012 9:34 AM EDT Freek Dijkstra
Priority 
3
 
2
 08/08/2012 10:27 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/go/artf6575?nav=1 at Fri, 04 Nov 2022 23:45:15 GMT