See also: IRC log
<scribe> scribe: dape
<scribe> scribeNick: DP
<inserted> scribenick: dape
Johannes: Goes over agenda
... 1. tech landscape deliverable
... 2. current-practices deliverable
... 3. charter candidate items
... 4. WoT API
... any comments/additions?
<none>
Johannes: did outreach to
Jeremy... maybe he and Peter St. Andre might join
... sorry for the short notice
Johannes: can be found here,
http://w3c.github.io/wot/landscape.html
... points transfered from Wiki
... need someone taking care of HTTP/2
... Dave will contribute to WebSocket
... Matthias for CoAP
Matthias: OK, can do that... was so far working on TD document
Johannes: Yes, the two documents
confuse
... MQTT handled by Dave and Michael
... I (Johannes) will provide infos and outreach to XMPP
... we need someone for STOM
Carsten: think we should skip protocols if no-one thinks it is useful
Johannes: agree
... Kaz to provide infos about MMI
Kaz: Did outreach already
Johannes: Claes added Thread..
thanks for that
... Discovery section might be moved to a dedicated section..
will clarify that with Soumya
... Carsten/Matthias can you take care of IETF CoRE protocol
mapping, also move it accordingly.
Carsten: Matthias, can you co-ordinate the efforts.. I am happy to help providing text
Johannes: description in TD, protocol-related to this document
Matthias: Not sure if I fully
understood the split between the 2 documents...
... can try to make a good divide
... OMA... Mohammed could you contribute?
Mohammed: Yes, I will...
... may also merge OMA and OMA lightweight part
Johannes: Agree, feel free to
merge them
... fyi: the 4 topics in the end of Section "4.2" are meant to
be filled in in all entries
... Got API and lightweight M2M still separate?
Mohammed: I think we should have one OMA section with those 2 as subsections
Johannes: Michael to provide OIC part?
Michael: yes, I am in contact with relevant Samsung people already
Carsten: BTW, At next research group meeting we are going to get in contact with them
Johannes: Michael again for IPSO Alliance?
Michael: I am not directly involved anymore.. but I can provide information
Johannes: w.r.t. oneM2M, Soumya
planned to outreach Martin B and Omar
... not sure about Hyper Cat
... will maybe talk to Soumya
Michael: think it is more about
thing description... but the topics are expanding
... just a template. no vocabulary.
... however I know people. I could reach out to Hyper Cat
people
Johannes: OGC: Dave will outreach
Michael: they do have something
called sensor thing API.. I think it is relevant
... Steve Liang might be able to respond questionnaire
Johannes: adds empty
questionnaire template
... the same questionnaire for ECHONET
Naka-San: added information to wiki already
Johannes: thanks!
... w.r.t API section
... added 4.3 section
... content from wiki
... server-side links to backend projects
... client-side scripting APIs I copied from wiki
... W3C fetch API
... presentation API
... geo-location API... Kaz might outreach?
... NFC and Bluetooth.... also Kaz
... scripting APIs
... Generic sensor API.. we had contact with Tobie Langel
... Vehicle API.. Kaz
... will outreach johnnyfive developer
... embedded runtimes next
Matthias: there was a project from Samsung.. embedded JS
Johanens: Jerryscript... good point, will add this item
Johannes: End of tech
landscape.
... should try to be done by next conference... in 2 weeks
http://w3c.github.io/wot/current-practices/wot-practices.html
Matthias: outlines the current
state of current practices document
... not a technical specification
... more about providing current status... w.r.t. building
blocks
... so far only the outline
... aligned structure according to charter...
... 1. thing description
... first building block
... TD talks about metadata
... TD also talks about Capabilities/Interactions
... Discovery is also part of TD
... security considerations of TD finalize the TD part
... 2. block is protocol mapping
... as part of it resource models are handled
... next available bindings
... and also the security considerations
... last part is Scripting API
... is about servients, discovery API, client, server API, and
physical API
... also security considerations w.r.t to Scripting API
... Section 4 is about previous plugfests
... findings should be mentioned there
... Conclusions is more about arguments "why is it as it
is"
Johannes: Questions/comments?
Matthias: What do people think about "new" structure... not having a 100% fit of task forces?
Kaz: sorry but had difficulty with audio connection, and would ask about the landscape document. I've started some discussion with Tobie and automotive guys, but everybody adding content to github.. not wiki, correct?
Johannes: Yes, I think it is
better to add it do document directly..
... document provides direct "edit" link
Kaz: between Tobie and Automotive guys two interfaces arised (Script, WoT socket Interface)
Johannes: How should we best proceed?
Kaz: Will ask them about availability for next AP call
Johannes: ...back to current
practices document
... comments on document and also on the structure?
Michael: we discussed about Web API and scripting API. We could put API under protocol?
Johannes: resource model is meant
to be Web API...
... does that work for you Michael?
Michael: Yes
Matthias: TD and resource
model
... not sure whether it helps to explain WebAPI
... even not sure whether needed... have TD and protocol
mappings
Johannes: might be useful to say "resource model/WebAPI" .. not sure about wording
Michael: scripting API has TD
Matthias: not sure.. maybe some
parts only...
... TD on higher level... rename "protocol mapping" to
"WebAPI"
... is a working document... can clarify it step by step
Michael: WebAPI with protocol mapping subsection
Johannes: yes, should work
Darko: Do we need section in TD for integration with other contextual semantic work?
Daniel: Feel free to fire pull request...
Johannes: Yes, good point. Please add comments/pull requests and such
Johannes: Sebastian merged
document from TD, AP, SP, and DI
... Oliver mentioned it is better to have security aspects in
dedicated parts
... now we should try to conclude on this
... deadline is next Friday...
... however, please still comment
... any comments here?
<none>
Johannes: I added
pull-request
... is merged aleady
<kaz> Johannes's pull request
Johannes: will try to move it to
current practices document
... so far we had interface "Thing"
... now we have "ExposedThing"
... one can add handlers
... might end up with a well-known eventName for events
... the "Thing" interface was renamed to "ConsumedThing"
... about get/set property... call action
... nothing in the document about physical API yet
<scribe> ... ongoing discussion
UNKNOWN_SPEAKER: commit was
mainly about splitting server-side and client-side
... in Nice we also discussed there are commonalities
Johannes: feel free to edit ...
or raise issues
... so far we have 3 issues..
... one by Claes w.r.t. to security
<kaz> security/privacy issue
Johannes: we might need to have a
token ... or handled in callbacks
... need to address that
... next issue is about ThingFilter...
-> https://github.com/w3c/wot/issues/50 ThingFilter issue
scribe: Louya proposed a new
filter class
... we might have different types of filter
... third discussion about API use
-> https://github.com/w3c/wot/issues/63 Thing Observe Property issue
Daniel: place for issues.. e.g. name clashed
Darko: What do you mean by name clashes
Daniel: TD allows you have the
same "name" for action and properties
... API does not allow you to do so...
Johannes: Not sure whether we have assumptions on the model...
Darko: yes, we might have those
assumptions stated in TD
... in plugfest we currently did not encounter those issues
Daniel: Agree, we need to state our assumptions somewhere
Johannes: I think the current practices document is a good place
Matthias: text could be in document... but validator by means of TD ontology also
Johannes: wrap up
<Darko_Anicic> Darko: yes, we can add such restrictions to TD ontology
Johannes: tech landscape deadline
in 2 weeks
... WG charter items.. deadline, please comment
... Thanks!
This is scribe.perl Revision: 1.144 of Date: 2015/11/17 08:39:34 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: i/Goes over/scribenick: dape Succeeded: s/God/Got/ FAILED: s/Evreryone/started discussion with Tobie and automotive guys. BTW, everybody/ Succeeded: s/ask for/ask them about/ Succeeded: s/Everyone/sorry but had difficulty with audio connection, and would ask about the landscape document. I've started some discussion with Tobie and automotive guys, but everybody/ Succeeded: s| s/Evreryone/started discussion with Tobie and automotive guys. BTW, everybody/|| Succeeded: s/dateline ended last Friday.../dateline is next Friday.../ Succeeded: s/dateline/deadline/ Succeeded: s/handler/handlers/ Succeeded: s|https:|-> https:| Succeeded: s|50|50 ThingFilter issue| Succeeded: s|63|63 Thing Observe Property issue| Succeeded: s/Dark/Darko/ Succeeded: s/... tech/Johannes: tech/ Found Scribe: dape Inferring ScribeNick: dape Found ScribeNick: DP WARNING: No scribe lines found matching ScribeNick pattern: <DP> ... Found ScribeNick: dape ScribeNicks: dape, DP Present: (no one) Johannes_Hund Ari_Keranen Carsten_Bormann Dan_Romascanu Daniel_Peintner Darko_Anicic Frank_Reusch Katsuyoshi_Naka Kaz_Ashimura Matthias_Kovatsch Daniel_Peinter Francois_Daoust Michael_Koster Mohammed_Dadas Roy_Kawada Takuki_Kamiya Toru_Kawaguchi Sebastian_Kaebisch Agenda: https://lists.w3.org/Archives/Public/public-wot-ig/2016Feb/0032.html Got date from IRC log name: 10 Feb 2016 Guessing minutes URL: http://www.w3.org/2016/02/10-wot-ap-minutes.html People with action items:[End of scribe.perl diagnostic output]