- From: Tim Berners-Lee <timbl@w3.org>
- Date: Mon, 10 Jan 2011 15:01:32 +0000
- To: Vasiliy Faronov <vfaronov@gmail.com>
- Cc: Toby Inkster <tai@g5n.co.uk>, Peter DeVries <pete.devries@gmail.com>, public-lod@w3.org
It is well to look at and make best practices for the things we have if we don't It was the FOAF folks who, initially, instead of using linked data, used an Inverse Functional Property to uniquely identify someone and then rdfs:seeAlso to find the data about them. So any FOAF browser has to look up the seeAlso or they don't follow any links. So tabulator always when looking up x and finding x see:also y will load y. So must any similar client or any crawler. So there is a lot of existing use we would throw away if we allowed rdfs:seeAlso for pointing to things which do not provide data. (It isn't the question of conneg or mime type, that is a red herring. it is whether there is machine-redable standards-based stuff about x). Further, we should not make any weaker properties like seeDocumentation subproperties of see:Also, or they would imply We maybe need a very weak top property like mayHaveSomeKindOfInfoAboutThis to be the superProperty of all the others. One things which could be stronger than seeAlso is definedBy if it is normally used for data, to point to the definitive ontology. That would then imply seeAlso. Tim
Received on Monday, 10 January 2011 15:02:16 UTC