W3C home > Mailing lists > Public > semantic-web@w3.org > July 2014

RDF Interface specification

From: Adrian Gschwend <ml-ktk@netlabs.org>
Date: Wed, 02 Jul 2014 16:36:26 +0200
Message-ID: <53B418EA.3040902@netlabs.org>
To: semantic-web@w3.org, bergi <bergi@axolotlfarm.org>
hi group,

For about two years the RDF Interfaces spec is in limbo:


It states:

"This document is not finished. Due to the lack of time, the RDF Web
Applications Working Group was unable to complete work on this document
before the end of their charter. At the time of publication of this
document, it was not known whether W3C will continue this work on the
Recommendation track in another Working Group. While a significant
amount of design work went into this document, at present there are no
known implementations of the specification. A number of design issues
have not been completely resolved. Developers wishing to implement this
API should be aware of incomplete nature of the specification."

However, in the JavaScript world RDF Interfaces is by now the base for
quite some projects and gets ongoing development by multiple developers.
There are at least 3 implementations available.

Last week Thomas Bergwinkl announced some new JavaScript libraries and
applications which build heavily on top of RDF Interfaces.



Followup with motivations:


He also proposes a new specification called RDF-Ext [1][2], which
extends RDF Interfaces with a store interface, async parsers &
serializers and an ES6 Promises interface.

The question now is what would be the best way to work on those
specifications. Currently it is published on a github page and the
content is residing in a github repo.

Is it the idea of W3C to standardize specifications which are more or
less language dependent? While RDF Interface never clearly stated it, it
is heavily oriented on JavaScript syntax and for that reason it most
probably won't be implemented in other languages. The same is true for
RDF-Ext. However, Thomas and I are interested in making it "official",
in case the group thinks that this makes sense.

I initiated the RDF JavaScript Community Group [3] for that reason so we
would also offer to take over both RDF Interfaces and RDF-Ext
specification development, if this makes sense.

comments would be appreciated


Thomas & Adrian

[1]: https://bergos.github.io/rdf-ext-spec/
[2]: Implementation of it: https://github.com/bergos/rdf-ext
[3]: http://www.w3.org/community/rdfjs/
Received on Wednesday, 2 July 2014 14:36:49 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:49:17 UTC