This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/go/artf6552?nav=1 at Fri, 04 Nov 2022 23:48:55 GMT SourceForge : artf6552: Ordered list

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 artf6552 : Ordered list
Tracker: Schema Progress
Title: Ordered list
Description:
XML parsers do not have to preserve order of child elements (even though most parsers do in practise).

RDF does not define order at all.

For some relations (including isSerialCompoundLink) we need to specify order.


Proposal: use the "next" relation for both XML and RDF, although their use is different. For RDF, also add the ListItem 
class and item relation.

Example:

<!--
      link A         link B         link C
 O--------------O--------------O--------------O

 (--------------------------------------------)
                     link Z
-->

XML:

<nml:Link id="urn:ogf:network:example.net:2012:linkZ">
	<nml:capacity>1000000000</nml:capacity>
	<nml:Relation type="serialcompound">
		<!-- this is a list -->
		<nml:Link nm:idRef="urn:ogf:network:example.net:2012:linkA">
			<!-- specify order of the list using the next relation -->
			<nml:Relation type="next">
				<nml:Link nm:idRef="urn:ogf:network:example.net:2012:linkB"/>
			</nml:Relation>
		</nml:Link>
		<nml:Link nm:idRef="urn:ogf:network:example.net:2012:linkB">
			<!-- specify order of the list using the next relation -->
			<nml:Relation type="next">
				<nml:Link nm:idRef="urn:ogf:network:example.net:2012:linkC"/>
			</nml:Relation>
		</nml:Link>
		<nml:Link nm:idRef="urn:ogf:network:example.net:2012:linkC">
	</nml:Relation>
</nml:Link>

RDF:

@prefix nml: <http://example.ogf.org/schemas/nml/>; .
@prefix nmlrel: <http://example.ogf.org/schemas/nml-relation/>; .
@prefix ex: <urn:ogf:network:example.net:2012> .

ex:linkZ a nml:Link ;
	nml:capacity 1000000000 ;
	nmlrel:isSerialCompoundLink ex:linkZ_1 .

ex:linkZ_1 a nml:ListItem ;
	nml:item ex:linkA ;
	nmlrel:next ex:linkZ_2 .
	
ex:linkZ_2 a nmlrel:ListItem ;
	nml:item ex:linkB ;
	nmlrel:next ex:linkZ_3 .

ex:linkZ_3 a nmlrel:ListItem ;
	nml:item ex:linkC .
Submitted By: Freek Dijkstra
Submitted On: 03/28/2012 6:06 PM EDT
Last Modified: 11/30/2012 7:56 AM EST
Closed: 11/30/2012 7:56 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 7:56 AM EST Jeroen van der Ham
Status
Last Call
Completed
11/30/2012 7:56 AM EST Jeroen van der Ham
Priority
4
2
08/08/2012 9:41 AM EDT Freek Dijkstra
Status
Need proposal
Last Call
08/08/2012 9:41 AM EDT Freek Dijkstra
Description
XML parsers do not have to preserve order of child elements (even though most 
parsers do in practise).

RDF does not define order at all.

For some relations (including isSerialCompoundLink) we need to specify order.
XML parsers do not have to preserve order of child elements (even though most 
parsers do in practise).

RDF does not define order at all.

For some relations (including isSerialCompoundLink) we need to specify order.


Proposal: use the "next" relation for both XML and RDF, although their use is 
different. For RDF, also add the ListItem class and item relation.

Example:

<!--
      link A         link B         link C
 O--------------O--------------O--------------O

 (--------------------------------------------)
                     link Z
-->

XML:

<nml:Link id="urn:ogf:network:example.net:2012:linkZ">
	<nml:capacity>1000000000</nml:capacity>
	<nml:Relation type="serialcompound">
		<!-- this is a list -->
		<nml:Link nm:idRef="urn:ogf:network:example.net:2012:linkA">
			<!-- specify order of the list using the next relation -->
			<nml:Relation type="next">
				<nml:Link nm:idRef="urn:ogf:network:example.net:2012:linkB"/>
			</nml:Relation>
		</nml:Link>
		<nml:Link nm:idRef="urn:ogf:network:example.net:2012:linkB">
			<!-- specify order of the list using the next relation -->
			<nml:Relation type="next">
				<nml:Link nm:idRef="urn:ogf:network:example.net:2012:linkC"/>
			</nml:Relation>
		</nml:Link>
		<nml:Link nm:idRef="urn:ogf:network:example.net:2012:linkC">
	</nml:Relation>
</nml:Link>

RDF:

@prefix nml: <http://example.ogf.org/schemas/nml/>; .
@prefix nmlrel: <http://example.ogf.org/schemas/nml-relation/>; .
@prefix ex: <urn:ogf:network:example.net:2012> .

ex:linkZ a nml:Link ;
	nml:capacity 1000000000 ;
	nmlrel:isSerialCompoundLink ex:linkZ_1 .

ex:linkZ_1 a nml:ListItem ;
	nml:item ex:linkA ;
	nmlrel:next ex:linkZ_2 .
	
ex:linkZ_2 a nmlrel:ListItem ;
	nml:item ex:linkB ;
	nmlrel:next ex:linkZ_3 .

ex:linkZ_3 a nmlrel:ListItem ;
	nml:item ex:linkC .
08/08/2012 9:41 AM EDT Freek Dijkstra
Assigned To None Jeroen van der Ham
03/29/2012 11:52 AM EDT Freek Dijkstra
Status
Need documentation
Need proposal
03/29/2012 11:52 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/artf6552?nav=1 at Fri, 04 Nov 2022 23:49:00 GMT