W3C home > Mailing lists > Public > public-rdfa-wg@w3.org > January 2011

Comments on the RDFa API

From: Ivan Herman <ivan@w3.org>
Date: Wed, 12 Jan 2011 13:28:42 +0100
To: W3C RDFa WG <public-rdfa-wg@w3.org>
Message-Id: <124DD98A-A142-49CA-81C4-E1F11F1C5E52@w3.org>
This mail, from Dave Reynolds, came through a different discussion, but some of the comments are directly relevant to the RDF(a) API. Actually, I think most of the comments are relevant to the published version only and no longer issues for the generic RDF API, but it is still better to check and record this. So here it is...

Begin forwarded message:

> From: Dave Reynolds <dave@epimorphics.com>
> Date: January 12, 2011 13:02:21 GMT+01:00
> To: Ivan Herman <ivan@w3.org>
> Hi Ivan,


> However, there is also the question of whether the goal is a Javascript
> RDF API or a Javascript-in-a-browser RDF API. The current RDFa draft is
> clearly intended only for in-browser use whereas Javascript is also used
> server side. A general purpose Javascript RDF would require making the
> DOM Node links optional, decoupling the literal encoding from the
> document encoding, support for multiple graphs and SPARQL Datasets etc.
> It may also be helpful to review existing APIs to see if there are
> capabilities in them that should be in a general purpose Javascript RDF
> API. For example, unless I'm missing something (which is always
> possible) the WD just supports forward link traversal whereas finding
> all incoming links to a node is a commonly used feature of other APIs.
> [Though I see, via Andy, that the Editor's draft has changed rather a
> lot from the publish WD and may already have addressed issues like
> that.]
> Dave

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 Wednesday, 12 January 2011 12:29:24 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:19:50 UTC