W3C home > Mailing lists > Public > public-powderwg@w3.org > March 2008

RE: mapsTo cf. ref cf. rdfs:seeAlso

From: Smith, Kevin, VF-Group <Kevin.Smith@vodafone.com>
Date: Wed, 5 Mar 2008 13:11:14 +0100
Message-ID: <37AC1116121D3F43B9A67CB16E2E79FF0B914A@VF-MBX11.internal.vodafone.com>
To: "Phil Archer" <parcher@icra.org>, "Public POWDER" <public-powderwg@w3.org>

 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:11:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:42:12 GMT