W3C home > Mailing lists > Public > public-wot-ig@w3.org > June 2015

AW: [TF-DI] Meeting details and agenda for 27/05

From: Hund, Johannes <johannes.hund@siemens.com>
Date: Tue, 2 Jun 2015 08:08:53 +0000
To: Dave Raggett <dsr@w3.org>, Soumya Kanti Datta <Soumya-Kanti.Datta@eurecom.fr>
CC: Public Web of Things IG <public-wot-ig@w3.org>
Message-ID: <C271054E16F8474D9104E1146C767BF145EFFB@DEFTHW99EK1MSX.ww902.siemens.net>
Hello Dave,

If there is not a compelling reason to do otherwise, I would prefer not to open another use-case document, but rather to merge any additionally needed use cases into the existing one.
Even better would IMHO be to (also) map the requirements you mention below to one or several of the existing use cases, as it’s underlining the real-life relevance.

We have a document that is planned to be a use case deliverable, which is modified through the xml file at [1], resulting in the page [2].
We also still have the collection of contributed use cases in the wiki at [3], where we unfortunately did not yet have much progress in merging those use cases into the above-mentioned doc.

Best regards,
Johannes

[1] https://github.com/w3c/wot/blob/master/ucr-doc/wot-ucr.xml

[2] http://w3c.github.io/wot/wot-ucr.html

[3] https://www.w3.org/WoT/IG/wiki/Use_case_contributions




Von: Dave Raggett [mailto:dsr@w3.org]
Gesendet: Mittwoch, 27. Mai 2015 19:01
An: Soumya Kanti Datta
Cc: Public Web of Things IG
Betreff: Re: [TF-DI] Meeting details and agenda for 27/05

Thanks. It sounds like we need a broader range of use cases that would allow us to cover a broader range of metadata requirements, as listed on slide 20 of http://www.w3.org/2015/05/wot-framework.pdf and repeated below:

● Thing descriptions

          • Data models & relationships between things
          • Dependencies and version management
          • Discovery and provisioning
          • Bindings to APIs and protocols
● Security related metadata
          • Security practices
          • Mutual authentication
          • Access control
          • Terms & conditions, and relationship to liability
          • Payments
          • Trust and Identity Verification
          • Privacy and Provenance
          • Resilience
● Communication related metadata
          • Protocols and ports
          • Data formats & encodings
          • Multiplexing and buffering of data
          • Efficient use of protocols
          • Devices which sleep most of the time

What is the best way to proceed?  We could just start to document this as part of the IG Note on the Web of Things Framework starting with an outline in GitHub and revising it through the GitHub issue tracking mechanism.

p.s. I wonder if I am the only one who keeps forgetting the TF-?? abbreviations?

Best regards,
   Dave

On 27 May 2015, at 12:55, Soumya Kanti Datta <Soumya-Kanti.Datta@eurecom.fr<mailto:Soumya-Kanti.Datta@eurecom.fr>> wrote:

Dear Dave,

In the TF-DI we decided to stick to the use cases already contributed and listed in WoT wiki. I am trying to further analyse them to see if they have the need for comm. metadata. Perhaps by the next meeting I can give you a better answer.

Regards
Soumya

Quoting Dave Raggett <dsr@w3.org<mailto:dsr@w3.org>>:


Hi Soumya,

My regrets as I will be meeting with the Open Group in Reading UK at  that time.

Do we have use cases that stress the need for communications  metadata?  For instance, imagine an electrocardiograph where you  need to log the waveform from several sensors.  In such cases, the  data is sent in blocks rather than as single values.

I am also interested in use cases where the sensors/actuators spend  most of their time asleep to conserve battery life, and as such can  only receive instructions at certain times. There are several common  patterns for this.  The problem is only present if there is a need  to send messages asynchronously to the IoT device. A simple  thermostat for a home heating system only needs to send messages and  not to receive them. The receiver module connected directly to the  heating system could be mains powered, so that it just listens all  the time.

? Dave


On 26 May 2015, at 09:50, Soumya Kanti Datta  <Soumya-Kanti.Datta@eurecom.fr<mailto:Soumya-Kanti.Datta@eurecom.fr>> wrote:

Dear All,

Please find here the meeting details and a draft agenda. If you  have other items to address, do not hesitate to send me an email  and I'll include them in the agenda.

Meeting details -

Conf name: wot-tf-1am-cest
Meeting number(Access code): 643 742 707
Meeting password: wot
Audio connection: +1-617-324-0000 US Toll Number
Meeting link:  https://mit.webex.com/mit/j.php?MTID=me54d402392c9e1aaf3eb31ae761949dd


Draft Agenda -

- Brief recap of past meetings
- Discussion on requirements derived from use cases
- Scopes and dimensions of discovery
- Discussion on a working draft for requirements
- Wrap up



Best Regards,
Soumya Kanti Datta

Research Engineer, EURECOM, France
Phone: +33658194342
Website: https://sites.google.com/site/skdunfolded






-------------------------------------------------------------------------------
This message was sent using EURECOM Webmail: http://webmail.eurecom.fr



?
  Dave Raggett <dsr@w3.org<mailto:dsr@w3.org> <mailto:dsr@w3.org>>






-------------------------------------------------------------------------------
This message was sent using EURECOM Webmail: http://webmail.eurecom.fr<http://webmail.eurecom.fr/>

—
   Dave Raggett <dsr@w3.org<mailto:dsr@w3.org>>



Received on Tuesday, 2 June 2015 08:09:20 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 2 June 2015 08:09:20 UTC