- From: Ed Davies <edavies@nildram.co.uk>
- Date: Mon, 30 Jul 2007 14:09:48 +0100
- To: www-tag@w3.org
On 2007-06-06 I wrote: > On reflection, I'm starting to wonder if treating 303 as > being equivalent to any sort of functional property is a > bad idea. This is because it is a relationship between > the original _URI_ and some destination resource, not the > original _resource_. Two URIs which refer to the same > original resource can 303 to two different destination > resources. So, from the point of view of resources, > 303 is a many-to-many relationship. Therefore, modulo > the issue with the destination possibly being a non-RDF > resource, I'll go back to my original suggestion of > rdf:seeAlso as the equivalent. Commenting in the light of the more recent Terminology Question monster thread, perhaps the same name should be given to the resource referenced by a 303 as that by a rdfs:seeAlso.
Received on Monday, 30 July 2007 13:11:50 UTC