- From: <kajimoto.kazuo@jp.panasonic.com>
- Date: Wed, 29 Apr 2015 23:52:29 +0000
- To: <kajimoto.kazuo@jp.panasonic.com>, <johannes.hund@siemens.com>, <public-wot-ig@w3.org>
- Message-ID: <FF475F4E041C8C41B696C42C4516BB8F0A7379@WEX00081.jp.corp.sanyo.com>
Johannes-san and all participants, In the last input slides by me, I forgot important use case "Notification". I added 1 slide and input again for Apr 30 TF-AP teleconference I hope those input would be helpful for discussion and further understanding of abstract WoT architectures. BR, ---- Kazuo Kajimoto Senior Councillor of Groupwide Software Strategy, Groupwide CTO Office kajimoto.kazuo@jp.panasonic.com -----Original Message----- From: kajimoto.kazuo@jp.panasonic.com [mailto:kajimoto.kazuo@jp.panasonic.com] Sent: Wednesday, April 29, 2015 9:42 PM To: johannes.hund@siemens.com; public-wot-ig@w3.org Subject: [TF-AP] Panasonic Input for the first call of WoT IG task force on APIs and protocols Johannes-san and other participants, I'd like to input Home Automation APIs and Protocols mapping example. My input is still more abstract than real implementation of Home Automation Use Cases. But it would be good for APIs and Protocol Mapping Model discussion. BR, ---- Kazuo Kajimoto Senior Councillor of Groupwide Software Strategy, Groupwide CTO Office kajimoto.kazuo@jp.panasonic.com<mailto:kajimoto.kazuo@jp.panasonic.com> -----Original Message----- From: Hund, Johannes [mailto:johannes.hund@siemens.com] Sent: Wednesday, April 29, 2015 12:26 AM To: Public Web of Things IG Cc: Kajimoto, Kazuo (梶本 一夫) Subject: [TF-AP] Draft Agenda for the first call of WoT IG task force on APIs and protocols Dear Task Force, see here a draft agenda for the call on Thursday 9AM CEST. - Additions & Changes to the Agenda - Input about data structures and interactions / Bluetooth SIG and Google Doc - Input from iotkit-comm / Intel - call for AI: architectural figures for use case based on abstract architecture discussed on F2F - call for AI: example sketch of REST-APIs and/or sketched script for a use case - Examples from Claes for the eldercare use case. Best regards, Johannes Call-In data: Topic: WoT APIs and Protocols Date: Thursday, April 30, 2015 Time: 9:00 am, Europe Summer Time (Berlin, GMT+02:00) Meeting Number: 641 161 687 Meeting Password: WoT-API ------------------------------------------------------- To join the online meeting (Now from mobile devices!) ------------------------------------------------------- 1. Go to https://mit.webex.com/mit/j.php?MTID=m53bff0c509c4d7823883005565aae59a 2. If requested, enter your name and email address. 3. If a password is required, enter the meeting password: WoT-API 4. Click "Join". To view in other time zones or languages, please click the link: https://mit.webex.com/mit/j.php?MTID=m5586447ce418dd58e388b577b361656b ------------------------------------------------------- To join the audio conference only ------------------------------------------------------- To receive a call back, provide your phone number when you join the meeting, or call the number below and enter the access code. US Toll Number: +1-617-324-0000 Access code:641 161 687 ------------------------------------------------------- For assistance ------------------------------------------------------- 1. Go to https://mit.webex.com/mit/mc 2. On the left navigation bar, click "Support". You can contact me at: abird@w3.org<mailto:abird@w3.org> 1-617-2537823 To update this meeting to your calendar program (for example Microsoft Outlook), click this link: https://mit.webex.com/mit/j.php?MTID=mc26c232542b911201ddacb6265ac1249 WebEx will automatically setup Meeting Manager for Windows the first time you join a meeting. To save time, you can setup prior to the meeting by clicking this link: https://mit.webex.com/mit/meetingcenter/mcsetup.php
Attachments
- application/pdf attachment: W3C_TF-AP20150430v2_Panasonic_Kajimoto.pdf
Received on Wednesday, 29 April 2015 23:53:14 UTC