Re: [WoT IG] Proposals for potential work items of a WoT WG

Hi Heuer and all,

I think it would be a good starting point looking for future work items.

I think we need to add one more description field for clarifying who is the real customer of potential work items.

 - who is the customer(using and implementing) of this work item

If we want to make market useful standardization, it would be a really important point.

Best Regards,

--- Jonathan Jeon

2015. 8. 10. 06:55 Heuer, Joerg <Joerg.Heuer@siemens.com<mailto:Joerg.Heuer@siemens.com>> 작성:

Dear all,

It seems that we still try to make the second step (setting up the WG Charter) before the first one (identify and discuss the relevant work items and timeframe for a WG). As discussed in the Sunnyvale meeting we want first to compile a list of proposed work items for a potential WoT WG before concluding on a charter.

So let’s first compile a list of these proposed work items before starting to go into a detailed formulation of a charter without having consensus on the work items in the first place.

A format to collect proposals could be:


-          Objective / WoT Building Block

-          Why is this a white gap?

-          Why is this in scope of W3C?

-          What are the risks of the proposal and what are mitigations?

To not miss proposals a wiki page to list those was set up:
https://www.w3.org/WoT/IG/wiki/Proposals_for_WoT_WG_work_items#Proposal_Structure


To provide a sample proposal, I would like to pick up API for the WebThing model, which I think was also referred to by a comment from Jonathan.

WoT API
=======

-          Objective / WoT Building Block

o   Abstract WoT API, which can be mapped on scriptiong languages

-          Why is this a white gap?

o   Currently no protocol independent API for WoT interactions exists

-          Why is this in scope of W3C?

o   Traditionally W3C standardises APIs e.g. web socket API

-          What are the risks of the proposal and what are mitigations?

o   Acceptance of API without concrete mapping and implementations

o   Provide specifications and sample code for concrete mappings into different script languages

Please contribute your proposals and comments to the wiki and the email list.

BR,
Joerg