Re: Updates to RDF Interfaces, RDF API, and RDFa API

On Wed, Jun 20, 2012 at 7:58 PM, Manu Sporny <msporny@digitalbazaar.com> wrote:

> Changes include:
>
> * Update to latest version of ReSpec (3.0.0)
> * Updates to the Status of the Document section to reflect NOTE status.
> * Added issue markers to the Abstract and Status of the Document
>  sections clearly noting that development has stopped due to lack of
>  interest and a warning to implement with caution.

How much interest is necessary to proceed? For about a year I've been
maintaining an up-to-date implementation of RDF Interfaces for
Node.js, with a test suite, at <https://github.com/Acubed/node-rdf>.
Most of the library should be easily ported to the web browser. I know
I can't be the only one, the library is largely based off Nathan's
(absolutely incredible) work, and there's at least one other Node.js
library (<https://github.com/antoniogarrote/rdfstore-js>) that claims
to use RDF Interfaces.

If there's lack of interest in the RDF API and RDFa API, maybe it's
for a lack of definite use cases. I don't really understand the
problem these are supposed to solve. While I'd guess I'm in the target
audience -- I'm extremely interested in consuming information (triple
stores and relational databases, turtle and RDFa documents alike),
processing it, and generating RDFa annotated documents -- I'm not sure
how the APIs help in the context of the open-world assumption, the
more complex RDF data structures (Collections), inferring new
information (with RDFS, etc), and manipulating the DOM (how is this
more helpful than the standard DOM functions?).

(Also maybe because <http://www.w3.org/TR/rdf-api/> is a dead link.)

Austin Wright.

Received on Tuesday, 26 June 2012 11:58:55 UTC