RE: Arrays in SKOS: proposal

The skos:ordered property suggestion is intended to be used as in ...

<skos:Concept rdf:about="URI_X">
	<skos:prefLabel>Aircraft</skos:prefLabel>
	<skos:array>
 		<skos:Array>
 			<rdfs:label>Aircraft by form</rdfs:label>
 			<skos:members rdf:parseType="Collection">
 				<skos:Concept rdf:about="URI_A"/>
 				<skos:Concept rdf:about="URI_B"/>
             		<skos:Concept rdf:about="URI_C"/>
         	</skos:members>
			<skos:ordered>false</skos:ordered>
 		</skos:Array>
 	</skos:array>
</skos:Concept>

...

and no, it should be rdf:about, not rdf:resource (check the specs [1]).

(I could have done the example above as ...

<skos:Concept rdf:about="URI_X">
	<skos:prefLabel>Aircraft</skos:prefLabel>
	<skos:array>
 		<skos:Array>
 			<rdfs:label>Aircraft by form</rdfs:label>
 			<skos:members rdf:parseType="Collection">
 				<rdf:Description rdf:about="URI_A"/>
 				<rdf:Description rdf:about="URI_B"/>
             		<rdf:Description rdf:about="URI_C"/>
         	</skos:members>
			<skos:ordered>false</skos:ordered>
 		</skos:Array>
 	</skos:array>
</skos:Concept>

... but it looks prettier if you put the type in the element name).

Al.

[1] http://www.w3.org/TR/rdf-primer/#collections

---
Alistair Miles
Research Associate
CCLRC - Rutherford Appleton Laboratory
Building R1 Room 1.60
Fermi Avenue
Chilton
Didcot
Oxfordshire OX11 0QX
United Kingdom
Email:        a.j.miles@rl.ac.uk
Tel: +44 (0)1235 445440



> -----Original Message-----
> From: public-esw-thes-request@w3.org
> [mailto:public-esw-thes-request@w3.org]On Behalf Of Houghton,Andrew
> Sent: 13 May 2004 19:15
> To: 'public-esw-thes@w3.org'
> Subject: RE: Arrays in SKOS: proposal
> 
> 
> 
> > From: Miles, AJ (Alistair) [mailto:A.J.Miles@rl.ac.uk] 
> > Sent: Thursday, May 13, 2004 1:59 PM
> > Subject: RE: Arrays in SKOS: proposal
> > 
> > Hi Andy,
> > 
> > We are using RDF Collections here - the skos:members property 
> > should be used exactly as in the #students property in the 
> > example at [1].
> > 
> > So a SKOS e.g. in RDF/XML ...
> > 
> > <skos:Concept rdf:about="URI_X">
> > 	<skos:prefLabel>Aircraft</skos:prefLabel>
> > 	<skos:array>
> > 		<skos:Array>
> > 			<rdfs:label>Aircraft by form</rdfs:label>
> > 			<skos:members rdf:parseType="Collection">
> > 				<skos:Concept rdf:about="URI_A"/>
> > 				<skos:Concept rdf:about="URI_B"/>
> >                       <skos:Concept rdf:about="URI_C"/>
> >                 </skos:members>
> > 		</skos:Array>
> > 	</skos:array>
> > 	<skos:narrower rdf:resource="URI_A"/>
> > 	<skos:narrower rdf:resource="URI_B"/>	
> > 	<skos:narrower rdf:resource="URI_C"/>
> > </skos:Concept>
> 
> Oops, I missed the collection at skos:members, so skos:ordered
> goes under skos:members?  If that's the case it seems to go
> against the grain of how the basic RDF rdf:Alt and rdf:Seq work.
> For example the collection semantics determine how they the
> element is interpreted.  So to extend the rdf:Alt and rdf:Seq
> analogy, I would expect to see skos:membersUnordered and
> skos:membersOrdered.
> 
> BTW, I think those rdf:about under skos:members should be
> rdf:resource.
> 
> 
> Andy.
> 
> Andrew Houghton, OCLC Online Computer Library Center, Inc.
> http://www.oclc.org/about/
> http://www.oclc.org/research/staff/houghton.htm
>

Received on Thursday, 13 May 2004 14:55:41 UTC