Re: mapsTo cf. ref cf. rdfs:seeAlso

Good point, no, rdfs:seeAlso and isDefinedBy take a single URI. OK, I 
suggest we therefore stick with ref for POWDER and that each element in 
the white space separated list is rendered a an rdfs:seeAlso property in 
POWDER-S (you can have any number of those).

Scream if we're planning something that XSLT can't handle!

P

Smith, Kevin, VF-Group wrote:
>  Hi Phil,
> 
> Makes sense, also another option is rdfs:isDefinedBy - however I'm not
> clear if either support a whitespace seperated list of URIs? I can't see
> a datatype binding to either, just that they are instances of
> rdfs:resource.
> 
> Cheers
> Kevin
> 
>  
> 
> 
> -----Original Message-----
> From: public-powderwg-request@w3.org
> [mailto:public-powderwg-request@w3.org] On Behalf Of Phil Archer
> Sent: 05 March 2008 11:59
> To: Public POWDER
> Subject: mapsTo cf. ref cf. rdfs:seeAlso
> 
> 
> Following on from Monday's discussion about the correct attribute for
> the Tagset (sorry, tagset :-))
> 
> We ended up saying that we would define wdr:ref to mean that the
> referenced resource may provide further definition of what the tag(s)
> mean. I wonder whether we should use the (well established) rdfs:seeAlso
> predicate for this? So we'd have something like
> 
> <tagset rdfs:seeAlso="http://example.com/chilli_sauce.htm">
>    <tag>Salsa</tag>
>    <tag>tomato</tag>
> </tagset>
> 
> The definition [1] of rdfs:seeAlso says:
> 
> "A triple of the form:
> 
> S rdfs:seeAlso O
> 
> states that the resource O may provide additional information about S. 
> It may be possible to retrieve representations of O from the Web, but
> this is not required. When such representations may be retrieved, no
> constraints are placed on the format of those representations."
> 
> WDYT?
> 
> Phil.
> 
> [1] http://www.w3.org/TR/rdf-schema/#ch_seealso
> 
>

Received on Wednesday, 5 March 2008 12:28:23 UTC