- From: Ed Davies <edavies@nildram.co.uk>
- Date: Wed, 06 Jun 2007 11:23:06 +0100
- To: Marc de Graauw <marc@marcdegraauw.com>
- CC: www-tag@w3.org
Marc de Graauw wrote: > ... > On a side note, in fact the 303 solution is not that different from subject > identifiers. Both assert whether a URI refers to an information resource or > not. In the XML serialization of Topic Maps, if a URI refers to an > information resource it is embedded in a <resourceRef> element, otherwise in > a <subjectIndicatorRef> element. So, tweaking the Topic Map definitions a > bit, it would be fair to say a 303 response means the dereferenced URI is a > subject indicator ... It doesn't follow that the destination of a 303 has a specific topic so <subjectIndicatorRef> is not equivalent. Using the examples from the httpRange-14 draft finding you could have these URIs http://example.com/ontology/metre http://example.com/ontology/kilogram http://example.com/ontology/watt all 303 to http://example.com/ontology/SI/Information which then provides RDF and/or HTML descriptions of hundreds of SI units, no one of which can be said to be the primary topic of the resource. Ed Davies.
Received on Wednesday, 6 June 2007 10:23:22 UTC