W3C home > Mailing lists > Public > public-dwbp-wg@w3.org > March 2014

Re: APIs to work with data on the web

From: Leigh Dodds <leigh@ldodds.com>
Date: Tue, 18 Mar 2014 16:38:50 +0000
Message-ID: <CAC_nr_of0XtcoCiS62SLtbsDe8ddAQ8wq0-9rBpf3CWR5kaJcg@mail.gmail.com>
To: Manuel.CARRASCO-BENITEZ@ec.europa.eu
Cc: laufer@globo.com, Steven Adler <adler1@us.ibm.com>, Deirdre.Lee@deri.org, mail@makxdekkers.com, newton@nic.br, public-dwbp-wg@w3.org

On Tue, Mar 18, 2014 at 4:23 PM, <Manuel.CARRASCO-BENITEZ@ec.europa.eu>wrote:

>  Forgot ... nothing wrong with having APIs in addition to URIs; but it is
> essential to have URIs.

It's more useful to characterise this as a SHOULD rather than a MUST
(essential), and also fine tune what those URIs are representing

For example:

If you want to publish "3 star data" then you MUST have a stable URI for
the dataset and SHOULD have a URI for each version of the dataset (for
archiving), as well as a "latest version" URI. Those are best practices to
support linking and archiving of datasets.

If you want to publish "5 star data" then you MUST have a stable URI for
everything in your dataset AND the dataset, or re-use existing URIs.
Publishing Linked Data is a best practice, and the use of URIs follows from
that (you can't do Linked Data otherwise).

There are specific best practices for creating cool, useful URIs for both
of these scenarios. I've captured some of those patterns here:



Received on Tuesday, 18 March 2014 16:39:21 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:24:12 UTC