W3C home > Mailing lists > Public > public-lod@w3.org > January 2011

Re: Is it best practices to use a rdfs:seeAlso link to a potentially multimegabyte PDF?, existing predicate for linking to PDF?

From: Vasiliy Faronov <vfaronov@gmail.com>
Date: Sun, 09 Jan 2011 18:21:34 +0300
To: Tim Berners-Lee <timbl@w3.org>
Cc: Peter DeVries <pete.devries@gmail.com>, public-lod@w3.org
Message-Id: <1294586494.3425.14.camel@midgard>
On Птн, 2011-01-07 at 11:47 -0500, Tim Berners-Lee wrote:
> Certainly. the tabulator follows rdfs:seeAlso and expects some terse
> RDF.
> and so would be crippled by any large file, and PDF would not of
> course help it at all.
> I take seeAlso as a fairly strong request to see the other thing, like
> an HTTP redirect.
> Not a generic "this is vaguely related" link at all, and not in
> general to point to human-readable stuff.

Maybe it's time to define several specializations of rdfs:seeAlso with
stronger semantics?

For example (in a hypothetical namespace):

- see:authoritative -- "strong" pointer to a defining document, 
  equivalent to (or even superseding) follow-your-nose. Could probably 
  just reuse wrds:describedby, though it's not a subproperty of 
- see:continued -- pointer to more data of the same nature. Would be 
  useful for paged data. When you have a blog marked up with RDFa, you 
  may want to let the consumer know that any given page is really just
  a part of it. "Strength" depends on the application.
- see:historical -- pointer to data that no longer holds, thus cannot
  be taken at face value, but only in conjunction with some
  time-related terms (like owlTime:Interval). In other words, "don't go 
  there unless you are time-enabled".
- see:non_rdf -- pointer to a machine-readable description that is not 
  in a serialization of RDF (GRDDL not counted as one).
- see:human_readable -- pointer to a description that is human-readable 

Vasiliy Faronov
Received on Sunday, 9 January 2011 15:22:07 UTC

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