- From: Ruben Verborgh <ruben.verborgh@ugent.be>
- Date: Wed, 20 Nov 2013 15:52:20 +0000
- To: Martynas Jusevicius <martynas@graphity.org>
- Cc: public-lod <public-lod@w3.org>
Hi Martynas,
> - URI templates: Linked Data API vocabulary
> https://code.google.com/p/linked-data-api/wiki/API_Vocabulary
Cool, I do like that. Have you thought about extending to RFC6570?
Do you know about usage of this vocabulary?
The one thing that I like less is the notion of endpoints.
While this is perfect for SPARQL, which is indeed an endpoint
or “data-handling process” that expects a “block of data” [1],
it does not work well in resource-oriented environments.
I’m looking for predicates that work with groups of resource, such as:
</topics/Global_Warming> :belongsTo </topics>.
</topics> a :ResourceList;
api:itemTemplate "/topics/{topicID}".
That is, I don't consider there to be a "topics" endpoint;
instead, there is a "topics" resource which lists several topics,
and individual topics can be accessed by ID.
The reason I would still need the template is because /topics/ is not exhaustive,
and new elements can be created by following the template.
This would be equivalent to a HTML GET form.
> - HTML forms: RDF/POST encoding http://www.lsrn.org/semweb/rdfpost.html
Interesting, thanks!
Best,
Ruben
[1] http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.5
Received on Wednesday, 20 November 2013 15:52:56 UTC