W3C

- DRAFT -

Web of Things Interest Group Teleconference

13 Jul 2016

See also: IRC log

Attendees

Present
DarkoAnicic
Regrets
Chair
SV_MEETING_CHAIR
Scribe
DarkoAnicic

Contents


<mkovatsc_> test

Johannes: do we have atomic use cases?

https://github.com/w3c/wot/tree/master/ucr-doc

Johannes: the document cross domain use cases with so called atomic use cases/building blocks (BB)

Matthias: there is a BB: Push Service relevant for the discussion

Johannes: introduces available material from the document

Matthias: the content in the document is not clear enough. Explains what's needed.

Johannes: we need to define a taxonomy based on the requirements so that we better understand what we are talking about

YongJing: We should define communication patterns
... and should consider QoS

Matthias: explaining what is required for events of type Alarams

Johannes: we need to define requirements and taxonomy for classes/types of events
... will provide minutes containing requirements and taxonomy for classes/types of events collected during the break out session.

Joerg: we should spend some time on CETC use cases

Kaz: how shall we group application patterns into one? I agree we should start with these atomic use cases, but after finishing that initial discussion we might want to how to integrate more than one use case or some big use cases which includes many capabilities like automotive. for that purpose, we need how to manage and synchronize multiple atomic use cases and domains

Johannes: the purpose of this exercise is to better understand events and use this work later on in Plug Fests

Matthias: on methodology - we will work on implementations and if it turns out that something does not work we need to go to the use cases

CETC presenting their viewpoint

NanWang: presenting use cases from CETC
... presenting Thing Descriptions from use cases from CETC

Joerg: shell we use one use case (e.g., from Smart Home domain) and try to provide a Thing Description in CETC and W3C format?

NanWang: yes, we can do this.

Meeting ends.

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.144 (CVS log)
$Date: 2016/07/13 07:46:00 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.144  of Date: 2015/11/17 08:39:34  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/how shell/how shall/
Succeeded: s/into one?/into one? I agree we should start with these atomic use cases, but after finishing that initial discussion we might want to how to integrate more than one use case or some big use cases which includes many capabilities like automotive. for that purpose, we need how to manage and synchronize multiple atomic use cases and domains/
No ScribeNick specified.  Guessing ScribeNick: DarkoAnicic
Inferring Scribes: DarkoAnicic

WARNING: No "Topic:" lines found.

Present: DarkoAnicic

WARNING: Fewer than 3 people found for Present list!


WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 13 Jul 2016
Guessing minutes URL: http://www.w3.org/2016/07/13-wot-ap-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]