See also: IRC log
<trackbot> Date: 08 July 2015
<scribe> meeting: Web of Things Descriptions
<scribe> scribenick: dsr
<Soumya> Joint meeting between TF-TD and TF-DI
Sebastian presents some slides that provide an overview of the high level requirements for thing descriptions.
The 3 building elements include the data model, the vocabulary and the serialisation
We’ve had a number of technology presentations in previous calls, e.g. IETF CoRE link format, the RDF data model, SSN ontology, JSON-LD, Spatial data ontology (SDWWG), SenML, IPSO, RDF serialisatio with EXI, Hydra (resource description), and functional semantics for WoT devices.
Sebastian proposes to distinguish information for identification/localisation, resource descriptions, and data descriptions.
How to describe what a thing does at a functional level is still a research topic
He presents an example of a temperature sensor located in “room 10” and which has a value in Celsius.
Dan: Sebastian’s approach mixes protocols and data
Dan talks about defining operations relating to sensors
Dave wonders why we aren’t talking about the simple linked data approach as presented in earlier introductions to the web of things
Sebastian: we should focus on use cases to drive discussion
We need to plan for our face to face at the end of the month.
Who of us will be in Sunnyvale? [most of us]
Soumya presents an overview of the work in the task force on discovery
Discussion on discovery in general, requirements, purpose, use cases, scopes and dimensions, and building blocks.
Device registation and lifecycle
4 categories: beacon based, discover on my network, searching in directories, and metadata
[Dave notes that this discussion omits disccovery based upon social connections, and also thingsonomies]
Soumya: we want a common vocabulary for thing description and discovery
Sebastian: Soumya, what do you mean by registration, how would it work?
In particular, how does a device know where to register?
Soumya: the registry location could be hard coded into the device’s software
[Dave: or the device could first discover a registry, e.g. a hub on the local network]
Soumya: devices can advertise themselves e.g. via Bluetooth beacons
IPSO have a specific vocabulary for things to identify themselves with
Victor: when you’re searching directories, how do you specify the scope?
Soumya: excellent question. We can have a local and remote scope.
Victor: you mean local networks?
Soumya: yes
Victor: what about sensor networks?
Dave: there are many possibilities, e.g. peer to peer based queries
Soumya invites Victor to join the discovery task force
Sebastian sums up and sets his expectations for the face to face.
… end of meeting
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) Succeeded: s/simpled/simple/ Found ScribeNick: dsr Inferring Scribes: dsr WARNING: No "Topic:" lines found. Present: Dave Dan Ken Louay Simon Soumya Victor Found Date: 08 Jul 2015 Guessing minutes URL: http://www.w3.org/2015/07/08-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]