- From: <kajimoto.kazuo@jp.panasonic.com>
- Date: Sun, 21 Jun 2015 13:17:24 +0000
- To: <johannes.hund@siemens.com>, <public-wot-ig@w3.org>
- CC: <kajimoto.kazuo@jp.panasonic.com>
- Message-ID: <FF475F4E041C8C41B696C42C4516BB8F0BE766@WEX00081.jp.corp.sanyo.com>
Dear Johannes-san and all, I'd like to add some comments in [3] by attached pdf. [3] https://github.com/w3c/wot/wiki/Architecture-Model The comments consist of 2 parts. 1) I agree 2 layers in the basic architecture as [3] And then notification flow from physical device, creation and register entry WoT servient(virtual object) flow, delete WoT servient(virtual object) flow, Those 3 might be missing. 2) Treatment of implementation Implementation is just reference, TF-AP would like to discuss abstract API. On the other hand, everyone has his own reference architecture, so it seems to be harder to agree the API concept. So, I try to make it clear where is common API across whole implementation examples. ---- Kazuo Kajimoto Senior Councillor of Groupwide Software Strategy, Groupwide CTO Office kajimoto.kazuo@jp.panasonic.com -----Original Message----- From: Hund, Johannes [mailto:johannes.hund@siemens.com] Sent: Friday, June 19, 2015 10:58 PM To: public-wot-ig@w3.org Subject: [TF-AP] Minutes of the TF-AP call on 17.06.2015 Dear task force, please find the minutes of your last call here: http://www.w3.org/2015/06/17-wot-ap-minutes.html Thanks to Vlad for scribing & presenting. Key findings: - We will have a joint F2F with IRTF's RG on thing-to-thing communication in July (in Prague). We should identify what topics we want to discuss there in the next calls. - There has been many updates in the proposed thing model on github [1], which is meant as a discussion starter. Please feel free to comment and suggest changes. - The framework implementation from Dave et al. [2] is based on the same principles, but differs in some aspects to what is currently discussed in the TF. We will need to see how to better stay in sync. - For the WoT IG F2F end of July, we will provide three submissions from the task force: 1. A model for the Architecture applicable to the use cases. (arch-model) 2. A model of resources and interactions used to concretely discuss the WoT interactions. (thing-model) 3. A landscape of protocols and technologies we see relevant for a standardization work in WoT. (tech-landscape) - We were preparing "arch-model" in the github wiki [3] - The "thing-model" will be generated out of the files and folders in [1]. - Lastly, we need input for the "tech-landscape", which would be relevant protocols or IoT frameworks resp. APIs that should be investigated for the standardization work. I have put up a brief wiki page at [4], where I ask everyone to contribute. Best Regards, Johannes [1] https://github.com/w3c/wot/tree/master/TF-AP/wot-compose-recommendation/web-things-model [2] https://github.com/w3c/web-of-things-framework [3] https://github.com/w3c/wot/wiki/Architecture-Model [4] https://www.w3.org/WoT/IG/wiki/Technology_Landscape
Attachments
- application/pdf attachment: W3C_WoT_TF_AP_Kajimoto_Panasonic_20150621.pdf
Received on Sunday, 21 June 2015 13:18:10 UTC