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
Received on Tuesday, 6 May 2014 15:40:24 UTC