RE: DCAT: Describing APIs

I consider this an important matter, too, and suggested to consider an “access manifest” for DCAT back in January’13: http://lists.w3.org/Archives/Public/public-gld-comments/2013Jan/0002.html but nobody seemed to be interested.

With kind regards,
Vasily Bunakov
STFC Scientific Computing


From: Stuart Harrison [mailto:stuart.harrison@theodi.org]
Sent: 04 April 2013 07:16
To: public-gld-comments@w3.org
Cc: tech@theodi.org
Subject: DCAT: Describing APIs

Hi,

I've just had a look at DCAT, and, as someone who's tried to maintain and submit to government data catalogues in the past, it looks really comprehensive.

The only thing I can see which may be missing is how we describe APIs - these often end up in data catalogues (rightly or wrongly), and, as they're being constantly updated, a lot of things like dct:updated would be meaningless. Are there any plans to add a description for an API, or any other constantly updating dataset?

Cheers

--
Stuart Harrison
Web Developer
Open Data Institute

Sent with Sparrow<http://www.sparrowmailapp.com/?sig>