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

Re: RDF Interface specification

From: Melvin Carvalho <melvincarvalho@gmail.com>
Date: Thu, 3 Jul 2014 13:49:06 +0200
Message-ID: <CAKaEYhKsXyVo5Gm2PEKSopR0H9z_3-XQwB+4C+BgLiFOgYR9NA@mail.gmail.com>
To: Adrian Gschwend <ml-ktk@netlabs.org>, public-rww <public-rww@w3.org>
Cc: Semantic Web <semantic-web@w3.org>, bergi <bergi@axolotlfarm.org>
On 2 July 2014 16:36, Adrian Gschwend <ml-ktk@netlabs.org> wrote:

> hi group,
>
> For about two years the RDF Interfaces spec is in limbo:
>
> http://www.w3.org/TR/rdf-interfaces/
>
> 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.
>
> Announcement:
>
> http://lists.w3.org/Archives/Public/public-rdfjs/2014Jun/0008.html
>
> Followup with motivations:
>
> http://lists.w3.org/Archives/Public/public-rdfjs/2014Jul/0001.html
>
> 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
>

Glad to see ongoing work on this project!

The RWW Community Group has already agreed to incubate this spec 1-2 years
ago.

Adrian, Thomas and Nathan are already participants in this group. [1]

My understanding was that this spec was essentially complete.  From what I
remember it was on REC track, pending some minor details to RDF 1.1.

I think Nathan was a bit pushed for time to support and maintain this work,
and from what I remember it was changed from REC track, to Note, due to
what was felt to be insufficient resources ...

Now that RDF 1.1 is baked, it should be possible to finish this work, if
indeed it's not finished already.

The RWW would be really happy to help out any way we can.  Alternatively
another community or working group could pick up the ball, if wished.  Very
happy to help here, just let us know what you feel need doing or the next
steps

[1] http://www.w3.org/community/rww/participants


>
> regards
>
> 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 Thursday, 3 July 2014 11:49:35 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 07:42:52 UTC