W3C home > Mailing lists > Public > public-linked-json@w3.org > June 2014

Re: Process of "following your nose"

From: Anders Riutta <anders.riutta@gladstone.ucsf.edu>
Date: Sun, 1 Jun 2014 08:57:38 -0700 (PDT)
To: Markus Lanthaler <markus.lanthaler@gmx.net>
Cc: public-linked-json@w3.org
Message-ID: <1370050078.3473557.1401638258696.JavaMail.zimbra@gladstone.ucsf.edu>
> Why would you need to know that beforehand? Sure, you could avoid a few
> failing requests but does that really improves things? What if you link to
> someone else's data? What if the set of media types changes? IMO it's enough
> to find it out at runtime (yeah, you could use the same argument against
> hydra:Resource/Link)

Good points. So hydra:Resource/Link tells us a URI is also a URL. A URL can be dereferenced, but we don't know whether it represents RDF statements. So we use content type negotiation and possibly sniffing of the response body to check for the availability of a format representing RDF statements. The server can use HTTP 303 redirects along with the content type negotiation to help us get a format representing RDF statements.

> Summarized, your application can do whatever it wants. Since the Web is a
> distributed system that isn't controlled by a single entity it is very often
> not practical to define strict contracts that define all details beforehand.
> A lot has to be found out at runtime. You obviously need to program your
> application accordingly.

Makes sense. Thanks!
Received on Sunday, 1 June 2014 15:58:04 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:18:41 UTC