- From: Kazuyuki Ashimura <ashimura@w3.org>
- Date: Mon, 14 Sep 2020 13:30:20 +0900
- To: public-wot-wg@w3.org
available at:
https://www.w3.org/2020/09/02-wot-td-minutes.html
also as text below.
Thanks a lot for taking the minutes, Mizushima-san!
Kazuyuki
---
[1]W3C
[1] http://www.w3.org/
- DRAFT -
WoT-WG - TD-TF
02 Sep 2020
[2]Agenda
[2] https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf#September_02.2C_2020
Attendees
Present
Kaz_Ashimura, Taki_Kamiya, Daniel_Peintner,
Tomoaki_Mizushima, Cristiano_Aguzzi, Michael_McCool,
Ege_Korkan
Regrets
Sebastian
Chair
Taki
Scribe
Mizushima, kaz
Contents
* [3]Topics
1. [4]Prev minutes
2. [5]Issue and PRs
3. [6]PR 951
4. [7]Security issues
* [8]Summary of Action Items
* [9]Summary of Resolutions
__________________________________________________________
Prev minutes
<Mizushima> scribenick: Mizushima
<kaz> [10]Aug-12
[10] https://www.w3.org/2020/08/12-wot-td-minutes.html
Taki: approved
Issue and PRs
Daniel: victor take about updating rendering script.
<kaz> [11]PR 951
[11] https://github.com/w3c/wot-thing-description/pull/951
Kaz: note that this issue 951 has several conflicts, and we
need to resolve them before merging it
<kaz> [12]Issue 950
[12] https://github.com/w3c/wot-thing-description/issues/950
<inserted> [13]Related issue 957
[13] https://github.com/w3c/wot-thing-description/issues/957
Daniel: This is about unobserveproperty.
Taki: we find this as clarification in TD v1.1.
[14]Issue 952
[14] https://github.com/w3c/wot-thing-description/issues/952
Taki: This issue is about use case how to describe TD
<kaz> [15]Issue 617
[15] https://github.com/w3c/wot-thing-description/issues/617
Taki: This issue is about array. And this is continuing to
discuss.
[16]Issue 955
[16] https://github.com/w3c/wot-thing-description/issues/955
Cristiano: This is about validate "oneOf".
Taki: Is this a limitation pattern?
Cristiano: yes
... This is Security Schema.
Daniel: JSON schema can check oneOf constraint.
Taki: we should go on discussion.
<kaz> [17]Issue 956
[17] https://github.com/w3c/wot-thing-description/issues/956
Daniel: This issue is about JSON schema validation issue.
<kaz> [18]TD draft - 5.3.2.1 DataSchema
[18] https://w3c.github.io/wot-thing-description/#dataschema
Taki: we define JSON schema in TD.
Daniel: we should read iri-referece.
... Ege proposed.
Taki: First session is finished.
<kaz> [break for 5mins]
<kaz> scribenick: kaz
PR 951
[19]PR 951
[19] https://github.com/w3c/wot-thing-description/pull/951
Taki: Victor raised this issue fixing the rendering mechanism
McCool: rendering may not match up the current index.html
... not sure if it's tested
... would break the content of index.html
Daniel: it's the case here
... we need to update the ttl file as well
McCool: we can once merge this PR and see the difference
between the result and the current index.html
Kaz: +1
... during the 1st hour today, I also suggested we remove the
conflicts
Taki: (adds comment to PR 951)
Daniel: need to check the security schema too
McCool: mainly OAuth2 changes
... including new flows
... maybe Victor should once pull down the current index.html
and see the diff himself
Kaz: yeah, anyway we need to update the index.template.html
file as well
McCool: yeah
[20]Taki's comments
[20] https://github.com/w3c/wot-thing-description/pull/951#issuecomment-685806777
(tentatively use "index2.template.html" and "index2.html" to
see the rendering results)
<inserted> PR 951; or we can tentatively use
"wot-security2.ttl" as well)
(wot-security.ttl to be rebased before merging PR 951)
Daniel: will talk with Victor
Security issues
[21]Security issues
[21] https://github.com/w3c/wot-thing-description/issues?q=is:issue+is:open+label:security
McCool: three security PRs
[22]PR 945
[22] https://github.com/w3c/wot-thing-description/pull/945
[23]PR 944
[23] https://github.com/w3c/wot-thing-description/pull/944
[24]Preview - 5.3.1.1 Thing
[24] https://pr-preview.s3.amazonaws.com/mmccool/wot-thing-description/pull/944.html#thing
McCool: "security" term has "CombinationSecurityScheme"
... one more PR to clean up the combination
[25]diff
[25] https://pr-preview.s3.amazonaws.com/w3c/wot-thing-description/944/32ba69e...mmccool:080fbea.html#thing
McCool: Example 12 uses "combo_sc"
[26]Example 12
[26] https://pr-preview.s3.amazonaws.com/w3c/wot-thing-description/944/32ba69e...mmccool:080fbea.html#security-digest-example2
McCool: another example 16
[27]Example 16
[27] https://pr-preview.s3.amazonaws.com/w3c/wot-thing-description/944/32ba69e...mmccool:080fbea.html#example-16
Ege: ok with this change
McCool: functionally not adding anything
... feature we already have on proxying
... but different syntax
Ege: someone can easily test
... but not implemented yet
... so opened an issue
<Ege>
[28]https://github.com/w3c/wot-thing-description/issues/901
[28] https://github.com/w3c/wot-thing-description/issues/901
McCool: that's an issue on implementations
Cristiano: also issue on oneOf scheme
<taki>
[29]https://github.com/w3c/wot-thing-description/pull/945
[29] https://github.com/w3c/wot-thing-description/pull/945
<taki>
[30]https://github.com/w3c/wot-thing-description/pull/944
[30] https://github.com/w3c/wot-thing-description/pull/944
McCool: question of JSON in the proxy
... need an example on proxy
... easy to get multiple producers
... but getting consumers would be problematic
... can add an Editor's note on possible limitation
Ege: why do we need to include features which are not used by
any implementations?
Kaz: note that we should think about the need for features
based on the use cases and the requirements rather than the
implementation status
McCool: yeah
... think there are specific use cases for the combo features
... as mentioned, producer side is easier
... consumer side needs further work
Cristiano: possibly complex boolean as well?
McCool: possible assertion on whether you're allowed to use
complicated combination or not
... would be reasonable constraint
Cristiano: what about the backward compatibility?
McCool: let's say 2.0 spec would remove the restriction
Cristiano: so that's more forward compatibility
McCool: yeah, in the future
Taki: (adds comments to PR 944 based on the discussion)
McCool: can add restriction on nested combo setting
Cristiano: ok
Ege: note that node-wot doesn't support multiple security
schemes within a TD
McCool: think there is a use case of mashing up multiple micro
services
Kaz: yeah, given WoT is expected to be used for multiple-vendor
IoT systems, we should consider fusion of multiple micro
services
... maybe we need a separate mechanism for that purpose but we
could start with this proposal
McCool: I should add an Editor's note on the restriction for
now
Kaz: so this is an expected feature for a mashing up server
McCool: mashing up may require basic for a micro service and
another scheme for another micro service
Kaz: yeah, not only the security scheme but all the TD
capabilities to be handled in parallel for the multiple micro
services, e.g., one for TV and another for air conditioner
McCool: right
... let me think about how to modify this PR itself
[31]PR 945
[31] https://github.com/w3c/wot-thing-description/pull/945
McCool: "security" can just be treated as an array of
SecurityScheme objects
... security scheme object vs array
... let me go ahead and think about it
... will update the PR for further discussion next week
Ege: array of names or security scheme object
... or combination of those
McCool: on the consumer side it's easy
... there are different ways to write TDs for the same purpose
... maybe we should capture the point using another issue
... we need different description for assertion tests
Taki: (adds comments)
McCool: OK with holding off this PR 945 until the PlugFest
Taki: let's talk about when to merge later (after the PlugFest)
McCool: we have a preview version of this PR
... and could use it as the basis for PlugFest
[32]Taki's comment
[32] https://github.com/w3c/wot-thing-description/pull/945#issuecomment-685837711
<Zakim> kaz, you wanted to suggest we create a bigger issue on
mash up server which integrates multiple micro services
Kaz: issue on mashing up in general?
McCool: yeah
... all the actions/properties to be mashed up for that purpose
... probably we should create an issue
Kaz: yeah, and we need some concrete use case description
Taki: a possible issue for wot-architecture as well?
Kaz: good question
McCool: we already have use cases for digital twin, etc.
Kaz: so we should create a TD issue
McCool: yeah, add mashing up for components
Taki: (creates an issue on that)
[33]Issue 958 (content to be filled in later)
[33] https://github.com/w3c/wot-thing-description/issues/958
[adjourned]
Summary of Action Items
Summary of Resolutions
[End of minutes]
__________________________________________________________
Minutes manually created (not a transcript), formatted by
David Booth's [34]scribe.perl version ([35]CVS log)
$Date: 2020/09/09 14:14:26 $
[34] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
[35] http://dev.w3.org/cvsweb/2002/scribe/
Received on Monday, 14 September 2020 04:30:25 UTC