W3C home > Mailing lists > Public > public-openannotation@w3.org > May 2014

Re: OA API available?

From: Stian Soiland-Reyes <soiland-reyes@cs.manchester.ac.uk>
Date: Tue, 6 May 2014 17:31:17 +0100
Message-ID: <CAPRnXt=xedzBQu-rZQ3XopjmG8YHqCCzUobdgkgu2FEefiJkGQ@mail.gmail.com>
To: Jacco van Ossenbruggen <Jacco.van.Ossenbruggen@cwi.nl>
Cc: Neal Audenaert <nealaudenaert@tees.tamus.edu>, Leyla Jael García Castro <leylajael@gmail.com>, public-openannotation <public-openannotation@w3.org>
Normal HTTP usually work well for retrieving Linked Data.

.. for publishing that depends a bit about your application - if you
want to have a generic server for maintaining collections of
oa:Annotations, then perhaps building on the
http://www.w3.org/TR/ldp/#ldpc Linked Data Platform Container  API
would work?

I should not mention the old Annotea Server approach.



On 6 May 2014 16:39, Jacco van Ossenbruggen
<Jacco.van.Ossenbruggen@cwi.nl> wrote:
> Hi Neal,
>
> On May 6, 2014, at 4:21 PM, Neal Audenaert <nealaudenaert@tees.tamus.edu>
> wrote:
>
> Jacco, my take is that that API should focus on the core data model and be
> independent of any particular representation of that data model. Or, stated
> another way, support for a specific format such as JSON-LD should be
> something that could be plugged into the system.
>
>
> Ah… I blindly assumed that by 'API' we were talking about a REST-style Web
> API to store and retrieve annotations from some web service, and that the
> programming languages referred to where simple the languages to implement
> this web api.
>
> Now I understand we were really talking about API in the plain software
> library sense of word… In which case I agree with your observation above.
>
> But let's assume I _am_ looking for the REST api… I would be curious what
> people on this list would consider a proper Web API…
> Jut plain HTTP GET/POST/PUT/DELETE requests, using the URLs of the
> annotations as the main request URL and JSON-LD serialisations of the RDF
> data model as the representation?
>
> Anything else would require some form of standardisation that is not
> currently in the spec, while the option above ties the annotation to a
> specific server and makes it hard to move to another server without changing
> the annotation url. So I think implementing a good REST api does require
> some standardisation.
>
> Jacco
>
>
>
>
>
>



-- 
Stian Soiland-Reyes, myGrid team
School of Computer Science
The University of Manchester
http://soiland-reyes.com/stian/work/ http://orcid.org/0000-0001-9842-9718
Received on Tuesday, 6 May 2014 16:32:06 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:22:06 UTC