See also: IRC log
<trackbot> Date: 17 June 2015
current state Wiki:
What is relevant to TD?
<Darko_Anicic> who is here?
Darko: last week recap. 2 talks: (1) W3C/OGC Spatial Data on the Web working Group and (2) SenML
relevance of SenML for TD?
Soumya: SenML used to encode sensor data. To put in parallel with CoRE Link Format
Presentation from Jaime about IPSO Smart Objects
Jaime: IoT issues already solved by Web techs.
On the Web, stateless interactions/focus on resources -> everything is a resource
apply this model to constrained devices -> CoAP
difference with the standard Web: OBSERVE (pub-sub), resource directory, IPv6 native support (6LowPAN)
Web Linking for IoT with CoRE Link (provides a .well-known URI)
query string params for discovery, 2 formats: "application/link-format", "application/link-format+json"
OMA Lightweight M2M (LWM2M)
based on CoAp
targets constrained device management
Objects stored on the devices, access to device objects from a LWM2M server
object-based model
IPSO defines a set of objects
(on top of LWM2M, see stack on slide 7)
IP for Smart Objects (IPSO)
goal is to achieve PnP between devices and applications
transport protocol-independant
CoAP, LWM2M, MQTT...
encoding-independent
JSON, TVL, SenML
tested over CoAP -> implemented, claim it works.
ARM, Intel, Ericsson, a.o, involved in this tests.
basic idea: objects are sensors/actuators
resource structure: <object ID>/<#instance>/<resource ID>
reusable IDs
fits to CoAP. But is also compatible with MQTT
(resource ID = topic)
Ex. of IPSO Humidity Sensor
extensible: new extensible object based on this Humidity Sensor (ex: make a prop. writable/readable)
composite objects (based on LWM2M : mapping physical objects with real-life thigs)
IPSO Object Linking -> new LWM2M data type: Object Link. Serialized in SenML
Roadmap: deal with UPnP, schema.org, BLE/ZigBee
<scribe> Done: Drafts for SO Data Model Design & Expansion Pack for Basic Objects
Missing: Draft for Domain Specific Objects
Sebastian: publicly accessible?
Jaime: Basic Objects, yes. Links will be addded to the slides
Dan: mechanism to define own domains?
Jaime: Objects IDs are registered with the OMNA
Sebastian: IDs not human-friendly.
Jaime: Translation layer can be implemented. Independent
Sebastian: targetted devices?
Jaime: broad focus. Started with small micro-controllers. But Rasp Pi introduced later
Darko: where to get a list of available objects?
Jaime: 17 objects in the spec, 20 coming soon. Most important is the application-specific objects
Darko: Interoperability with reusable objects?
Jaime: through root objects. Ex. of 2 systems using different Humidity Sensors
Still have a common interface through the root object
Sebastian: objects properties have a type. Where are they defined? What about complex types?
Jaime: basic types defined by LWM2M.
Complex types -> multiple resources?
Sebastian: example of a RGB LED
Jaime: to check.
Sebastian: wrap-up + next week. (1) carry on the discusion about IPSO, (2)Presentation about embedded semantics (ESWC publication). TODO match technologies reviewed until now with use cases.
This is scribe.perl Revision: 1.140 of Date: 2014-11-06 18:16:30 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) No ScribeNick specified. Guessing ScribeNick: Victor Inferring Scribes: Victor WARNING: No "Topic:" lines found. Present: DanhLePhuoc Soumya Danh Darko Jaime Joerg Kathy Lonay Victor Dan Arne Joel Sebastian WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Found Date: 17 Jun 2015 Guessing minutes URL: http://www.w3.org/2015/06/17-wot-td-minutes.html People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option. WARNING: No "Topic: ..." lines found! Resulting HTML may have an empty (invalid) <ol>...</ol>. Explanation: "Topic: ..." lines are used to indicate the start of new discussion topics or agenda items, such as: <dbooth> Topic: Review of Amy's report[End of scribe.perl diagnostic output]