See also: IRC log
(no specific comments)
jhund: input from Kajimoto-san
and Nimura-san
... next is technology landscape
... and then "any other business"
-> https://github.com/w3c/wot/wiki/Architecture-Model Architecture Model wiki
k_nimura: (explains)
... need to clarify what the servient and gw are like
("Real Implementations for legacy devices" section)
k_nimura: several options for "Behavior of WoT Servient":
WoT Servient gets a device profile on discovery.
WoT Servient invokes a virtual instance and installs a Device Driver (Thing Description) that corresponds to the device profile.
WoT Servient exposes APIs of the virtual instance.
k_nimura: and "Assumptions of BT GW"
BT GW has a media conversion capability such as BLE or Bluetooth 2.1.
BT GW accommodates an API such as GATT API, WebBluetooth, or HDP(Health Device Profile) in order to expose functions of a real thing.
WoT Servient binds the real thing and the Virtual Instance through the BT GW.
k_nimura: to understand the legacy device side, we need that kind of supplementary information
jhund: what need to be done by the WoT Servient for legacy devices. Right?
k_nimura: yes
jhund: nice input to understand
the mechanism
... any comments?
(no comments)
jhund: would move forward to Kajimoto-san's input
("Real Things accessible via Servients in the Web" section)
jhund: virtual instances
... lifecycle flow
(slides from Kajimoto-san)
-> https://lists.w3.org/Archives/Public/public-wot-ig/2015Jun/att-0068/W3C_WoT_TF_AP_Kajimoto_Panasonic_20150621.pdf Kajimoto-san's slides
jhund: skelton architecture
... and treatment of implementation
... would ask Kajimoto-san for clarification when he is
available
kaz: basically he suggests we
should consider the mapping between the architecture model and
actual system implementations
... and he shows four possible system implementations:
Web-based, smartphone as UI, set top box as a GW, cloud-based
services
jhund: ok
... we should put these slides as well on the wiki
... let's talk with Kajimoto-san and ask him clarifications as
well
... "smartphone centric" model is related to what Nimura-san
explained
... and cloud-based service figure is related to the GW-based
model. These figures are useful to understand the mechanism
k_nimura: yes, and Kajimoto-san thinks some more different possible protocols as well
jhund: would add these figures to the wiki
+1
-> http://www.w3.org/WoT/IG/wiki/APIs_and_Protocols_TF AP TF wiki
jhund: looking at existing
technologies
... bluetooth-related technology should be also added
... what do you think?
... need Invited Experts?
kaz: do we want to invite the MMI
WG Chair, Debbie Dahl?
... she can explain the MMI Architecture briefly
jhund: fine by me
kaz: can send a message to invite her to the next call CCing you
jhund: ok
<scribe> ACTION: kaz to send an invitation to the MMI WG Chair to join the next AP TF call [recorded in http://www.w3.org/2015/06/23-wot-ap-minutes.html#action01]
<trackbot> Created ACTION-9 - Send an invitation to the mmi wg chair to join the next ap tf call [on Kazuyuki Ashimura - due 2015-06-30].
jhund: regarding bluetooth, anybody familiar with its profile?
k_nimura: can make some contribution
jhund: great
... I'm familiar with XMPP
... and would explain it during the next call
... also ask some other MQTT experts as well
... maybe we can get somebody for CoAP protocol as well
... if anything missing on the list, please let me know
... what are the major findings
... to gather a more complete picture
... to talk about Web of Things
... you can add items if there is anything missing
... also need to discuss "resource models" and "potential API
patterns"
... resource models to describe related resources
... mapping to legacy devices as well
... if we can find common denotation mechanism, that would be
great
jhund: two f2f meetings in
July
... IETF joint meeting in Prague
... joint discussion on CoAP, etc.
... data layer and application layer
... also we'll have a WoT IG f2f meeting
... in Silicon Volley
... technology landscape, etc.
... other TFs like device discovery as well
... how does a device find other devices
... our discussion today would be useful for that as well
... joint discussion on things description too
... actual content and data structure
... any comments?
(no specific comments)
jhund: ok, let's close the call then
[ adjourned ]