<scribe> scribenick: jhund

agenda

soumya asks for additions & comments

none heard

recab of last call

Soumya: explains the definition of scope

logistics

Soumya: meeting will be @ 1am CEST next week

brainstorming

Soumya asks for use cases

Arne is volounterring to look at smart building/smart home use cases

Soumya: did you have a background there already?

Arne: will have a look at it

Danh: all use cases should be considered instead of proposing new ones specifically for each TF

Soumya: we will base our research/definition on the contributed use cases

Danh: is there an agreement on the use cases

Soumya: those are the use cases we will use to derive requirements from
... do you want to take over one of those?

Danh: my area of expertise is more industrial

https://w3c.github.io/wot/wot-ucr.html

jhund: use cases can of course still be contributed

eduardo: I'll have a look at the oxford flood network for discovery requirements
... I'll take ver one additional UC, will post on the list

Soumya: I'll take over health monitoring and integrated home automation

Danh: will take over public transport
... is the list on github different from the list in the wiki

jhund: yes, the wiki list will get merged into github

Requirements from the woT Framework

Soumya: what would be a first point to start?
... let's go round the table for a starting point
... of high-level requirements

Arne: the categorisation presented last time was good
... centralized vs. distributed, web-based and the means of discovery

rrsagent make logs public

Arne: which approach would be prefferable
... braod scope, but TDL indicates a drift towards link-based, web-like discovery

s/broad/broad/

RRSAgent: , draft minutes

Danh: discovery could be a service-based discovery
... the question is "how do you query the data model that represents your system?"
... discovery is a query based oin this data model
... so the TF should focus about the desciption of the context of the Things
... which is beyoun d thing description

Soumya: could you give a presentation?

DanhLePhuoc: yes, but in two weeks time

thx, kaz ;)

DanhLePhuoc: need to be clear on what we mean by discovery
... as people from different backgrounbds will interprete the term differently
... we are trying to push web tech, so we should put network discovery out of scope
... and focus on service discovery, data-based discovery, e.g. search engines
... question: should we scope to this kind of discovery or also look at low-level network discovery

Soumya: could you provide content?

DanhLePhuoc: will start discussion on the mailing list

Soumya: any other comment?

jhund: +1 for DanhLePhuoc's question if we scope to data discovery
... or also look at network discovery

Soumya: in the TF-AP discussions, was discovery a topic?

jhund: we identified the need for an API to discover, but would base that on the input of the TF-DI

scopes & dimens of discovery

Soumya: scope could be local or remote scope for wide-area

DanhLePhuoc: sope could be one-time (as in the web) or long-standing like in a Pub/Sub system

Soumya: so discovery could be querying or streaming?

DanhLePhuoc: right, some discovery is more like pubsub
... in the WoT. In the web nowerdays its more a one time query

Soumya: I'll add it as dimension

<DanhLePhuoc> +1 for quality of data/measurement

Edoardo_Pignotti: dimensions could also be: location, accessibility (e.g. paywalls), context, quality

Soumya: what is meant by quality?

Edoardo_Pignotti: I'll work on an example for next time

DanhLePhuoc: example: in SSN, same sensor types can be provided in different quality (e.g. resolution in temperature or wind speed)

Edoardo_Pignotti: exact. accuracy could be one example for the quality

DanhLePhuoc: could be used for the ranking in discovery

Soumya: ranking as in the reply of the discovery service

DanhLePhuoc: exactly, it will be crucially needed

jhund: difference between the observed object and the observing device

Arne: also known as feature of interest in the SSN

Soumya: is sharing a presentation on the TF goals in the next weeks
... distribute work on use cases (done)
... call for presentations
... joint session with TF-TD in mid-june
... joint session with IG-SP
... and set up a working document
... to be populated with the requirements resulting from the UCs
... will be set up in the wiki for starters

jhund: we had the tooling question in the TF-AP as well

Soumya: requirements draft will be ready for the F2F
... I'll give a presentation about the discussion of the TF
... other comments?

none heard

Soumya: closing the meeting
... was a good meeting. I'll update the outcomes into the wiki

<scribe> Meeting: W3C WoT IG Task force on discovery regular call on 2015-05-20

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)

FAILED: s/broad/broad/
Found ScribeNick: jhund
Inferring Scribes: jhund
Present: Soumya_Kanti_Datta Edoardo Pignotti
Got date from IRC log name: 20 May 2015
Guessing minutes URL: http://www.w3.org/2015/05/20-wot-di-minutes.html
People with action items: