W3C home > Mailing lists > Public > public-lod@w3.org > April 2010

Re: Delegating trust via.. ? rdfs:seeAlso or?

From: Leigh Dodds <leigh.dodds@talis.com>
Date: Mon, 19 Apr 2010 14:34:47 +0100
Message-ID: <m2sf323a4471004190634ldee856dai28eef985522bb225@mail.gmail.com>
To: Story Henry <henry.story@bblfish.net>
Cc: nathan <nathan@webr3.org>, Linked Data community <public-lod@w3.org>, foaf-protocols <foaf-protocols@lists.foaf-project.org>

On 19 April 2010 14:18, Story Henry <henry.story@bblfish.net> wrote:
>> rdfs:seeAlso is appropriate here [1]. You're refering to another
>> relevant RDF document.
> At the same time how relevant it is will depend on usage. If there are a lot
> of rdfs:seeAlso links that point pretty much to any type of resource, then the
> value of following such a link could be too small. rdfs:seeAlso is very generic,
> and it seems to be functioning somewhat like a <a href="/other">see Also</a> link,
> which if there are enough on the page, could be a bit difficult for a client
> to work with.

In which case you ought to indicate to the consumer about what they
may expect to receive after de-referencing the indicated document. It
could be an RSS feed. Or it could be, as in this case, another
PersonalProfileDocument. These relationships could be indicated using
sub-properties, or by just indicating the general "type" of document
you're referencing [1].

<http://www.example.org/person/A? rdfs:seeAlso
<http://www.example.org/doc/other> a foaf:PersonalProfileDocument.

A client application can then make a more informed decision. In this
scenario it would be sensible for a FOAF viewer to fetch all of the
PersonalProfileDocuments it has discovered for that person.

[1]. http://patterns.dataincubator.org/book/ch04s03.html



Leigh Dodds
Programme Manager, Talis Platform
Received on Monday, 19 April 2010 13:35:21 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:16:05 UTC