Re: Potentials of the RDFa DOM API

On May 25, 2010, at 11:32 , Toby Inkster wrote:

> On Tue, 25 May 2010 10:19:49 +0200
> Ivan Herman <ivan@w3.org> wrote:
> 
>> it is also not 100% whether the community would accept and/or would
>> be interested in having a standard RDF API. What language(s) (Java,
>> Python, Javascript, etc)? What happens to the deployed applications
>> of Jena vs. Sesame vs. Redland vs....? Etc, etc.
> 
> As far as having a standard common API for RDF in general, we already
> do: Jena, Sesame and Redland already all provide SPARQL. Once SPARQL
> Update is more standardised, that API will become read-write.
> 

Yes, that is certainly an argument that is used a lot against starting such standardization work. I should have mentioned it. The comparison that is usually given is PHP's access to SQL: there is no API, just using SQL textually.

Ivan


> The RDFa DOM API is something different though, distinguishing itself
> from existing RDF APIs by taking advantage of RDFa's embeddedness in
> host languages, integrating with the existing API of the host language
> (i.e. the HTML/XML DOM).
> 
> -- 
> Toby A Inkster
> <mailto:mail@tobyinkster.co.uk>
> <http://tobyinkster.co.uk>
> 


----
Ivan Herman, W3C Semantic Web Activity Lead
Home: http://www.w3.org/People/Ivan/
mobile: +31-641044153
PGP Key: http://www.ivan-herman.net/pgpkey.html
FOAF: http://www.ivan-herman.net/foaf.rdf

Received on Tuesday, 25 May 2010 10:10:18 UTC