W3C home > Mailing lists > Public > public-wot-ig@w3.org > December 2016

Re: [Charter]: include both Scripting and REST API

From: Kis, Zoltan <zoltan.kis@intel.com>
Date: Thu, 8 Dec 2016 14:08:10 +0200
Message-ID: <CANrNqUdVYB64SOvBgfd3LzofggKHqQNS0DPb0R6XY4cSJFjWwQ@mail.gmail.com>
To: Dave Raggett <dsr@w3.org>
Cc: Dominique Guinard <dom@evrythng.com>, Public Web of Things IG <public-wot-ig@w3.org>
[We'd need to set the WoT github repo to send emails on issue comments...]

On Thu, Dec 8, 2016 at 1:36 PM, Dave Raggett <dsr@w3.org> wrote:

> Just to point out that W3C already has a standard API for REST as part of
> the Open Web Platform, so we would need to justify why a new API is needed.
>
>
That's a good point. Which one did you mean? I have found these:
https://www.w3.org/2012/ldp/charter (expired), general spec here:
https://www.w3.org/TR/ldp/
https://www.w3.org/community/hydra/ (
http://www.hydra-cg.com/spec/latest/core/ )

The above are good input for WoT REST. The latter is a special application,
with specific use cases (which are shared with the WoT Scripting API). We
can't expect to work on a WoT REST API in that WG/CG, right? For instance
Thing Descriptions are not discussed there, either.

We can discuss and then embrace, drop or transfer REST API work, but the
point is, can we arrive to this in the WoT WG, and does the WoT WG charter
allow working on that.

Thanks,
Zoltan
Received on Thursday, 8 December 2016 12:08:50 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 8 December 2016 12:08:50 UTC