- From: Kazuyuki Ashimura <ashimura@w3.org>
- Date: Mon, 12 Jul 2021 16:56:22 +0900
- To: public-wot-wg@w3.org
available at:
https://www.w3.org/2021/05/05-wot-td-minutes.html
also as text below.
Thanks a lot for taking the minutes, Michael Koster!
Kazuyuki
---
[1]W3C
[1] https://www.w3.org/
– DRAFT –
WoT-WG - TD-TF
05 May 2021
[2]Agenda. [3]IRC log.
[2] https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf#May_5.2C_2021
[3] https://www.w3.org/2021/05/05-wot-td-irc
Attendees
Present
Cristiano_Aguzzi, Daniel_Peintner, Ege_Korkan,
Fady_Salama, Kaz_Ashimura, Michael_Koster,
Michael_McCool, Sebastian_Kaebisch, Tomoaki_Mizushima,
Victor_Charpenay
Regrets
-
Chair
Sebastian
Scribe
mjk
Contents
1. [4]agenda review
2. [5]minutes review from last meeting
3. [6]Publication
4. [7]PR reviews
1. [8]PR 937
2. [9]PR 943
3. [10]PR 1085
4. [11]PR 1120 - validation for icon links
5. [12]PR 1121 - introduce profile term
6. [13]PR 937 (revisited)
7. [14]PR 1104 - Data schema issues
8. [15]PR 1085 - Add Validation
9. [16]PR 1113 tm:required and tm:ref
10. [17]PR 1122 - terminology
11. [18]PR 1123 - tm namespace
12. [19]PR 1124 - canonicalization
5. [20]Working draft review
6. [21]Issue 940
Meeting minutes
agenda review
<kaz> [22]Agenda for today
[22] https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf#May_5.2C_2021
Sebastian: focus on review of PRs and prepare for final
document review
McCool: issue #940, question around signing
minutes review from last meeting
<kaz> [23]Apr-28
[23] https://www.w3.org/2021/04/28-wot-td-minutes.html
Sebastian: walking through the PRs that we reviewed last week
Sebastian: we decided to allow as much of JSON schema as we
can, and include the missing terms
McCool: there were also some arbitrary extension points that we
discussed
… we should not allow extensions because it prevents good
checking for typos
Sebastian: discussion on selection where multiple forms are
present
… discussion on URI variables
… PR for tmRequired and tmRef
… there will be a new namespace and prefix convention for TM
… they will be tm:required and tm:ref using the new namspace
Sebastian: does the SDF use of required apply to anything or
just interactions?
Koster: sdfRequired can point to any JSON node, including
interactions and sdfChoice (enum) elements
Sebastian: minutes themselves have been approved
Publication
Sebastian: call for review after this TD call, and we're
planning to publish the updated TD draft May 19
Sebastian: we can add a sentence to clarify the use of
tm:required
PR reviews
PR 937
<kaz> [24]PR 937 - WIP: swap securtiy and securityDefinition in
context file
[24] https://github.com/w3c/wot-thing-description/pull/937
Sebastian: #937
PR 943
<kaz> [25]PR 943 - WIP: Add proof and proofChain sections
[25] https://github.com/w3c/wot-thing-description/pull/943
Sebastian: #943
McCool: we are rebasing the PR so should close this one
McCool: the new PR will be based on issue #940
PR 1085
<kaz> [26]PR 1085 - WIP: Add Validation Section
[26] https://github.com/w3c/wot-thing-description/pull/1085
Sebastian: Validation section
McCool: could merge but the tagging is not done yet
Sebastian: agree to merge
… maybe we could think more about the naming of the categories
McCool: we could change it to minimum + basic
McCool: will add an editor note about the tagging and make the
name change
PR 1120 - validation for icon links
<kaz> [27]PR 1120
[27] https://github.com/w3c/wot-thing-description/pull/1120
Cristiano: it validates the size metadata
Cristiano: adds a validation rule when sizes is present
PR 1121 - introduce profile term
<kaz> [28]PR 1121
[28] https://github.com/w3c/wot-thing-description/pull/1121
Sebastian: optional term for indicating the profile mechanism,
URI pointing to a wot profile
Ege: it could be an array with "and" validation of all profiles
… the definition should have a statement about how multiple
profiles are applied
… a consumer may only need to support one of the offered
profiles
McCool: a producer may support more than one profile at the
same time
… need to add this explanation to the profile specification
Sebastian: there could be a question of which form to consume
when there are multiple choices in forms
Koster: the profile may inform that, do we need to provide
additional guidance in the spec?
McCool: probably can leave it up to the consumer
dape: why doesn't the shape for interaction affordances have an
order number?
Victor: it is intended to allow any or none (?)
PR 937 (revisited)
<kaz> [29]PR 937 - WIP: swap securtiy and securityDefinition in
context file
[29] https://github.com/w3c/wot-thing-description/pull/937
Sebastian: why does securityDefinitions not appear in the
ontology?
McCool: it may be a mistake in the file
McCool: it could be incorrectly generated
Victor: securityDefinitions is just a container, like
definitions in JSON schemas
… it's only a reference
McCool: there is confusion between the information model and
the serialization
<victor> [30]https://w3c.github.io/wot-thing-description/#thing
[30] https://w3c.github.io/wot-thing-description/#thing
McCool: when converted to RDF, they are all flattened to the
same RDF property
McCool: for canonicalization, we need to preserve all of the
nodes in the original document
… it's probaby easier to pass them through round trip rather
than regenerate
Victor: should the information model then be changed?
McCool: there is the same issue with named dataschemas in
additional responses
Victor: what changes need to be made?
McCool: start with the rendering
McCool: we may want to change security to allow objects for
names schemes
Victor: it would align better with RDF
Sebastian: this isn't critical for the specification
McCool: it blocks progress due to the dataschema issue
Victor: can provide a TD normalization script
McCool: sounds similar to canonicalization
McCool: we can discuss offline and track on the issue tracker
Sebastian: should we involve JSON-LD people?
Sebastian: it seems related to #1077
PR 1104 - Data schema issues
<kaz> [31]PR 1104 - Address multiple DataSchema issues
[31] https://github.com/w3c/wot-thing-description/pull/1104
Sebastian: adds a new term "default"
Sebastian: adds a note on the "format" term being removed in
future versions
Ege: it has been replaced in JSON schema with a new vocabulary
feature which we could continue to use
<McCool> @dape that's what I did, not rendering. Trying
"section" (that is what is done in architecture)
Sebastian: also adds "pattern" term for constraints using regex
<Ege> [32]https://json-schema.org/understanding-json-schema/
reference/regular_expressions.html
[32] https://json-schema.org/understanding-json-schema/reference/regular_expressions.html
McCool: use of regex should exclude script execution
McCool: the JSON schema subset is reasonable
McCool: maybe we could just use the regex subset definition
text on the JSON schema website
<McCool> mm: probably the solution is to copy that text into
our spec, but we need to ask for permission to do so
Sebastian: merge conflict...
… merged
PR 1085 - Add Validation
<kaz> [33]PR 1085
[33] https://github.com/w3c/wot-thing-description/pull/1085
McCool: added the editors note for no tags and changed the
validation category names
Sebastian: ready to merge?
PR 1113 tm:required and tm:ref
<kaz> [34]PR 1113
[34] https://github.com/w3c/wot-thing-description/pull/1113
Ege: implementation of this PR is in the script that generates
the files
PR 1122 - terminology
<kaz> [35]PR 1122
[35] https://github.com/w3c/wot-thing-description/pull/1122
Sebastian: merge conflict resolved
… merged
PR 1123 - tm namespace
<kaz> [36]PR 1123
[36] https://github.com/w3c/wot-thing-description/pull/1123
Sebastian: new tm namespace and ontology
… initially we have only three concepts but more will be added
… reviewing changes in the rendered document
Sebastian: added a rule that extended definitions must be valid
wrt the base definition
… merged
PR 1124 - canonicalization
<kaz> [37]PR 1124
[37] https://github.com/w3c/wot-thing-description/pull/1124
Sebastian: adds some clarifications
McCool: addressed some issues and bugs
Sebastian: merge conflicts, mm will fix and merge
Working draft review
Sebastian: take the next 2 weeks to review this document for
working draft publication
Sebastian: still some remaining issues
McCool: we are working on a signing section and have some
proposals
Issue 940
McCool: will make a PR that we can comment on
Sebastian: any other issues to look at?
<kaz> (none)
<kaz> [adjourned]
Minutes manually created (not a transcript), formatted by
[38]scribe.perl version 131 (Sat Apr 24 15:23:43 2021 UTC).
[38] https://w3c.github.io/scribe2/scribedoc.html
Received on Monday, 12 July 2021 07:56:28 UTC