- From: Kazuyuki Ashimura <ashimura@w3.org>
- Date: Wed, 23 Sep 2020 16:59:36 +0900
- To: public-wot-wg@w3.org
available at:
https://www.w3.org/2020/09/09-wot-td-minutes.html
also as text below.
Thanks a lot for taking the minutes, Michael Koster!
Kazuyuki
---
[1]W3C
[1] http://www.w3.org/
- DRAFT -
WoT-WG - TD-TF
09 Sep 2020
[2]Agenda
[2] https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf#September_09.2C_2020
Attendees
Present
Kaz_Ashimura, Michael_McCool, Ege_Korkan, Taki_Kamiya,
Daniel_Peintner, Tomoaki_Mizushima, Cristiano_Aguzzi,
Sebastian_Kaebisch, Michael_Koster
Regrets
Chair
Sebastian
Scribe
mjk_
Contents
* [3]Topics
1. [4]Agenda review
2. [5]Minutes from last week
3. [6]TPAC
4. [7]GitHub issues
5. [8]Issue #956 - iri-reference
6. [9]Issue 957
7. [10]Issue #941 geolocation model built into TD
vocabulary
8. [11]Issue #912 content type and encodings
9. [12]Outstanding PRs
10. [13]Restructure of documentation for Thing Model
11. [14]Swap securtiy and securityDefinition
12. [15]PR# 869
* [16]Summary of Action Items
* [17]Summary of Resolutions
__________________________________________________________
<kaz> scribenick: mjk_
Agenda review
[18]Agenda
[18] https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf#September_09.2C_2020
Minutes from last week
<inserted> [19]Sep-2
[19] https://www.w3.org/2020/09/02-wot-td-minutes.html
Sebastian: status of the rendering script
... other discussion items from last week oneOf in schema,
unobserve
McCool: correction to the minutes - "JSON schema *can* validate
oneOf
[20]Issue 955
[20] https://github.com/w3c/wot-thing-description/issues/955
Daniel: there are some limitations in general but JSON schema
can check the oneOf constraint
McCool: typo correction
TPAC
Sebastian: start to collect TD topics for TPAC
... JSON-LD specific topics, collect the open questions
... labeling github issues
<kaz> [21]JSON-LD specific issues
[21] https://github.com/w3c/wot-thing-description/labels/JSON-LD 1.1
Sebastian: versioning topic, how are we going to indicate the
version in the TD
... is the context sufficient?
McCool: there are some discovery issues for JSON-LD we could
combine
<sebastian> collecting all wot topics for JSON-LD joint
meeting: [22]https://github.com/w3c/wot/issues/933
[22] https://github.com/w3c/wot/issues/933
Sebastian: are there other topics for other groups? Security
issues with DID?
... what are some deep dive topics for the F2F sessions or
topics to discuss in the larger group?
Daniel: we should communicate and discuss the current thinking
on dynamic TD/Action status
Sebastian: thing model discussion (TD template)
GitHub issues
<sebastian>
[23]https://github.com/w3c/wot-thing-description/issues/958
[23] https://github.com/w3c/wot-thing-description/issues/958
#958 component mechanism for mashups
Sebastian: why not use link container
McCool: we should parallel the OneDM concept of "Object"
(sdfObject)
... also there is a potential for name conflicts with repeated
elements of the same type in a TD
... links are one option, another option is a nested structure
Sebastian: it could be related to the thing model topic
McCool: composability of TDs
Ege: related to the research we are doing in putting TD parts
into another TD
... also has mashup logic
... can present next week, it is published but maybe links
aren't out yet
McCool: there is a youtube
... use cases include modularity, mashup, and discovery by
function
<McCool> [24]https://www.youtube.com/watch?v=FGPbl8Occjw
[24] https://www.youtube.com/watch?v=FGPbl8Occjw
<McCool> sorry, that was on WADE
<Ege_>
[25]https://www.youtube.com/watch?time_continue=1&v=yOfA24lbGj0
&feature=emb_logo
[25] https://www.youtube.com/watch?time_continue=1&v=yOfA24lbGj0&feature=emb_logo
Koster: describes smartthings use cases
... can share the JSON file for device profile in SmartThings
... common pattern for oneDM and iotschema
<Ege_> [26]https://github.com/tum-esi/wot-system-description
[26] https://github.com/tum-esi/wot-system-description
Issue #956 - iri-reference
<inserted> [27]Issue 956
[27] https://github.com/w3c/wot-thing-description/issues/956
Daniel: it's complex because JSON schema is in flux
Ege: anyuri type maps to iri-reference (iri is a localization
of a URI)
... the feature is dropped from json schema due to complex
... it's not well supported and not required for validation
... the implementation in the PG doesn't support iri-reference
... the format keyword is removed and a new mechanism is being
created for typing
Cristiano: can remove format and use regex
... but it makes the solution difficult and not recommended
Ege: there is a new $vocabulary term in JSON schema
McCool: suggest to keep things as they are for TD 1.1 and look
at new features in 2.0
Issue 957
<sebastian> next issue:
[28]https://github.com/w3c/wot-thing-description/issues/957
[28] https://github.com/w3c/wot-thing-description/issues/957
<McCool> (sorry, I have to drop, have a conflicting meeting I
have to switch to)
Sebastian: some protocols don't need unsubscribe/unobserve
Ege: if there is no unsubscribe op, there should be a scripting
error
... there could be a default mechanism
Sebastian: how woud longpoll work?
Koster: there are many protocols that share streams, how does a
client filter get configured, for example?
Ege: there could be defaults
Cristiano: should be both subscribe and unsubscribe
<sebastian> wow
Ege: we should look algorithmic-ly that I look for the
instructions in a form to do what I want to do, before invoking
the actual mapped protocol
Daniel: based on this example, how do we describe different
locations for subscribe vs. un-
Koster: this would require multiple forms
<kaz> [29]Example 35
[29] https://www.w3.org/TR/2020/REC-wot-thing-description-20200409/#example-35-temperature-event-with-subscription-and-cancellation
Koster: it's not a default but a requirement to always specify
some form for unsubscribe, even if it's the same form as
subscribe
... this could use an array for the op value "op": ["observe",
"unobserve"]
Sebastian: suggest language that each operation is required to
have an entry in a form
Cristiano: agree
<cris> server sent event implementation in node-wot:
[30]https://github.com/eclipse/thingweb.node-wot/blob/591724445
065c7f05b4defb24ebb2a61e3bfd836/packages/binding-http/src/subsc
ription-protocols.ts#L71
[30] https://github.com/eclipse/thingweb.node-wot/blob/591724445065c7f05b4defb24ebb2a61e3bfd836/packages/binding-http/src/subscription-protocols.ts#L71
<sebastian> next issue:
Issue #941 geolocation model built into TD vocabulary
[31]https://github.com/w3c/wot-thing-description/issues/941
[31] https://github.com/w3c/wot-thing-description/issues/941
Sebastian: various public models and ontologies exist (examples
given)
Taki: spatial data on the web reference
... (SDW)
<kaz> [32]Spatial Data on the Web Best Practices
[32] https://www.w3.org/TR/sdw-bp/
Sebastian: schema.org example from Ben Francis
Ege: seems to be the best approach
... best to put the URI into a property affordance
Cristiano: this way we could also use different vocabularies
for different use cases
Koster: recap discussion from earlier meeting where the
tradeoff of built-in vs. common affordances was discussed
Sebastian: will put together a proposal for discussion at the
next TD meeting
Issue #912 content type and encodings
Sebastian: proposing "contentMediaType" and "contentEncoding"
form elements
<kaz> [33]Issue 912
[33] https://github.com/w3c/wot-thing-description/issues/912
Sebastian: is it possible to use contentType to also specify
the encoding?
Koster: RFC 6839
... structured syntax for media types
<kaz> [34]RFC6839
[34] https://tools.ietf.org/html/rfc6839
Outstanding PRs
<inserted> [35]PRs
[35] https://github.com/w3c/wot-thing-description/pulls
Sebastian: 3 PRs from McCool
... security related PRs
<kaz> [36]PR 945 - marked as "Draft"
[36] https://github.com/w3c/wot-thing-description/pull/945
<kaz> [37]PR 944 - OK but to be confirmed next week with McCool
[37] https://github.com/w3c/wot-thing-description/pull/944
<kaz> [38]PR-943 - marked as "Draft"
[38] https://github.com/w3c/wot-thing-description/pull/943
Restructure of documentation for Thing Model
<kaz> [39]PR 938
[39] https://github.com/w3c/wot-thing-description/pull/938
Swap security and securityDefinition
<kaz> [40]PR 937
[40] https://github.com/w3c/wot-thing-description/pull/937
PR# 869
<kaz> [41]PR 869 - to be discussed next week
[41] https://github.com/w3c/wot-thing-description/pull/869
Sebastian: 2 PRs from Taki
Taki: may not be relevant, will check
<kaz> [42]PR 768
[42] https://github.com/w3c/wot-thing-description/pull/768
<kaz> [43]PR 766
[43] https://github.com/w3c/wot-thing-description/pull/766
Sebastian: last topic, any other discussion?
(none)
<kaz> [adjourned]
Summary of Action Items
Summary of Resolutions
[End of minutes]
__________________________________________________________
Minutes manually created (not a transcript), formatted by
David Booth's [44]scribe.perl version ([45]CVS log)
$Date: 2020/09/14 04:25:16 $
[44] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
[45] http://dev.w3.org/cvsweb/2002/scribe/
Received on Wednesday, 23 September 2020 07:59:41 UTC