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

Re: RDF Interface specification

From: Nathan Rixham <nathan@webr3.org>
Date: Wed, 2 Jul 2014 16:19:15 +0100
Message-ID: <CANiy74zPgPGV9SdifOfPu2kZfUzUCwnd8_LkEX9Myfyg1jBj_w@mail.gmail.com>
To: Adrian Gschwend <ml-ktk@netlabs.org>
Cc: semantic-web@w3.org, bergi <bergi@axolotlfarm.org>
Glad to see the work didn't go waste, and I wish you the best of luck
moving forward with the project.

>From my personal standpoint, RDF Interfaces was considered finished and
informally reviewed by timbl, pending any changes which would need to be
made after RDF 1.1 - although I tried to pre-guess them and keep it
compatible both forwards and backwards. you will know yourself what is
required, if anything.

Regarding being javascript specific, the original spec was oriented towards
js, but also catered for other languages, to ensure this I implemented it
in PHP as a side project whilst creating the spec. The specifications map
to WebIDL, and WebIDL maps to other languages.

IMHO the real value is in implementation and usage, where you have both
excelled. Kudos.


On Wed, Jul 2, 2014 at 3:36 PM, 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
>
> 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 Wednesday, 2 July 2014 15:19:44 UTC

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