14:55:09 RRSAgent has joined #wot-td 14:55:09 logging to https://www.w3.org/2022/02/09-wot-td-irc 14:55:25 meeting: WoT-WG - TD-TF 14:57:26 Mizushima has joined #wot-td 15:00:41 thjaeckle has joined #wot-td 15:02:39 ryuichi has joined #wot-td 15:06:11 dape has joined #wot-td 15:07:07 JKRhb has joined #wot-td 15:08:22 cris has joined #wot-td 15:09:00 present+ Kaz_Ashimura, Sebastian_Kaebisch, Cristiano_Aguzzi, Daniel_Peintner, Ege_Korkan, Jan_Romann 15:09:12 present+ Michael_McCool, THomas_Jaeckle 15:09:55 I just use the initials of the speaker and write? 15:10:33 present- THomas_Jaeckle 15:10:41 present+ Thomas_Jaeckle 15:10:41 sk: Outlook to next week: A guest presenting the BACnet Binding for WoT 15:10:50 i/Outlook/topic: Agenda/ 15:10:57 q+ 15:11:13 sk: would like to look at a couple of PRs to merge today 15:11:27 q+ 15:11:32 ack d 15:11:36 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf#Feb_9.2C_2022 15:11:39 https://github.com/w3c/wot/blob/main/charters/wg-2021-extension-plan.md 15:11:41 number 4 15:12:05 i/https/dp: pub schedule was updated today/ 15:12:07 ack dape 15:12:28 sk: final goal today: freeze of all the sections to see in the TD WD 15:12:42 rrsagent, make log public 15:12:48 rrsagent, draft minutes 15:12:49 I have made the request to generate https://www.w3.org/2022/02/09-wot-td-minutes.html kaz 15:12:53 --> pr -> https://github.com/w3c/wot/pull/1012/files 15:13:02 q? 15:13:53 ka: is the BAC binding agenda item for next week a presentation or are there use cases for the binding template? 15:14:01 s/BAC/BACnet/ 15:14:39 s/next week/next week,/ 15:14:45 s/is the/regarding the/ 15:15:17 s/a presentation/would it be a presentation/ 15:16:08 s/use cases/concrete use case description, etc.,/ 15:16:42 jkrhb_ has joined #wot-td 15:16:58 sk: talk about BACnet binding and the opportunities next week 15:17:38 kaz: whichever is fine (just a presentation or concrete proposal) but wanted to clarify the topic 15:18:11 rrsagent, draft minutes 15:18:11 I have made the request to generate https://www.w3.org/2022/02/09-wot-td-minutes.html kaz 15:18:29 topic: Prev minutes 15:18:37 sk: checking meeting minutes of last week: agreed last week that "dataResponse" element is provided in event affordance 15:18:46 i|checking|-> https://www.w3.org/2022/02/02-wot-td-minutes.html Feb-2| 15:19:06 chair: Sebastian 15:19:07 q? 15:19:08 ack k 15:19:27 jkrhb__ has joined #wot-td 15:19:29 i/Outlook to/scribenick: thjackle/ 15:19:39 sk: decided against "schemaDefinition" on global level for TD 1.1 last week 15:19:46 i/pub schedule was/scribenick: kaz/ 15:20:03 i/final goal today/scribenick: thjaeckle/ 15:20:18 i/whichever is/scribenick: kaz/ 15:20:28 i/checking meeting/scribenick: thjaeckle/ 15:20:34 rrsagent, draft minutes 15:20:34 I have made the request to generate https://www.w3.org/2022/02/09-wot-td-minutes.html kaz 15:21:54 sk: last week a feature freeze for upcoming WD was agreed on 15:23:21 (minutes approved) 15:23:56 topic: Wide reviews 15:24:04 sk: requests done for accesibility, i18n, security groups 15:24:29 -> https://github.com/w3c/a11y-request/issues/21 Accessibility 15:24:38 -> https://github.com/w3c/i18n-request/issues/171 I18N 15:25:07 -> https://github.com/w3c/wot-thing-description/pull/1382 Security 15:25:29 mm: hope to have security issue done by next wednesday 15:26:15 s/1382 Security/1382 Security review preparation/ 15:27:23 sk: TAG is very busy, that's why we already setup request for review, expecting them to review the request in couple of months 15:27:36 sk: let's look at PRs 15:27:40 JKRhb has joined #wot-td 15:27:47 topic: Pull Requests 15:29:03 sk: manifest PR #1340 regarding "manifest" in links 15:29:48 i|manifest|subtopic: PR 1340| 15:30:06 i|manifest|-> https://github.com/w3c/wot-thing-description/pull/1340 PR 1340 - Manifest| 15:30:33 sk: idea is to create another PR in order to only include relevant text change in it 15:31:09 +1 15:31:34 sk: manifest PR will be included in WD 15:32:36 subtopic: PR 1368 - $id field in index template 15:33:54 -> https://github.com/w3c/wot-thing-description/pull/1368 PR 1368 - Adding $id to JSON Schema 15:34:01 ek: good practice to add "$id" field 15:34:25 ek: if using multiple JsonSchemas, one can use "$id" field to reference them 15:37:40 q+ 15:39:02 sk: merges PR 1368 15:39:12 ack k 15:39:32 subtopic: PR 1376 15:39:52 q+ 15:39:52 -> https://github.com/w3c/wot-thing-description/pull/1376 PR 1376 - refactor: remove MD5 from alg example list 15:40:28 sk: we agreed to not include the enum with existing algorithms any more 15:41:31 dp: the JsonSchema "ext-td-json-schema-validation.json" was not updated for 5 months, it seems outdated 15:42:06 sk: this document should not be used anywhere 15:42:34 mm: reason we have it is we have a strict version and a version allowing extensions - the none-strict version allows using extensions 15:42:35 i|this doc|-> https://github.com/w3c/wot-thing-description/blob/main/validation/ext-td-json-schema-validation.json ext-td-json-schema-validation.json| 15:43:19 ek: does not know this file, never used it 15:43:50 q+ 15:44:14 ack dape 15:44:17 ack k 15:44:23 ka: can we clarify which schema files are used in playground? 15:46:11 https://github.com/thingweb/thingweb-playground/blob/master/packages/core/td-schema.json is the one used by playground 15:46:38 sk: creates issue to discuss removal of `ext-td-json-schema-validation.json`: #1386 15:47:05 subtopic: PR 1377 15:47:20 -> https://github.com/w3c/wot-thing-description/pull/1377 Add dataResponse to event affordance 15:47:28 q? 15:49:51 sk: thinks addition of "dataSchema" is enough for supporting the webhook use case 15:50:14 sk: merges PR 1377 15:50:53 dp: fixed PR 1376 (circling back to MD5 PR) 15:51:08 sk: merges PR 1376 15:51:36 subtopic: PR 1380 15:51:48 -> https://github.com/w3c/wot-thing-description/pull/1380 Add profile to JSON Schema 15:54:08 sk: main intention to have the "profile" in JsonSchema for validation 15:55:09 sk: merges PR 1380 15:55:34 subtopic: PR 1383 15:55:48 -> https://github.com/w3c/wot-thing-description/pull/1383 Top level URI Variables 15:57:12 ek: additionally defined that uriVariables on interaction affordance level take precedence when also defined on top level 15:58:17 sk: inspects example with top level forms and top level uriVariables 15:59:15 ek: btw, this also solves the issue how to "readmultipleproperties" via HTTP 15:59:39 +1 15:59:55 sk: merges PR 1383 16:00:32 sk: other PRs to decide/look at after the WD 16:01:02 subtopic: PR 1360 16:01:18 -> https://github.com/w3c/wot-thing-description/pull/1360 Update Security and Privacy Considerations 16:01:36 mm: not completely done, but still ok to merge for the WD 16:03:49 sk: ok with the PR to merge as is 16:04:02 mm: will do another PR to just include the actual changes 16:06:13 topic: Check Issues 16:08:08 subtopic: Issue 1384 16:08:27 -> https://github.com/w3c/wot-thing-description/issues/1384 Issue 1384 - A TD should be able to define which Properties are required 16:09:45 q+ 16:11:08 sk: mentions "additionalResponses" in order to define error codes / responses 16:11:55 q+ 16:14:55 ek: thinks "required" is the wrong english word 16:15:48 dp: what happens if there are multiple forms? should a consumer try other forms until it can access a propery not present in the first form? 16:18:19 ack dape 16:18:22 ack e 16:18:23 ack Ege 16:18:36 subtopic: Issue 1368 16:18:56 -> -> https://github.com/w3c/wot-thing-description/issues/1368 Refactoring JSON Schema to have less duplication 16:19:28 sk: marking with V1.1 label 16:19:49 subtopic: Issue 1354 16:19:50 s/-> ->/->/ 16:20:07 -> https://github.com/w3c/wot-thing-description/issues/1354 ThingModel composition and TD relation 16:20:43 sk: not yet a solution to avoid the confusion of the composition concept 16:21:05 jkrhb_ has joined #wot-td 16:22:16 q+ 16:23:10 tj: proposes to explain limit of extension, that only one model can be extended, which can be solved by using composition instead 16:24:04 McCool has joined #wot-td 16:24:32 (aside: cleaned up PR for security and privacy considerations now ready: https://github.com/w3c/wot-thing-description/pull/1387) 16:24:57 q+ 16:25:12 ka: a nicer example would help, if possible to provide typical composition example 16:25:41 ack k 16:25:42 ack m 16:25:53 mm: examples in the wild: multi sensors and power outlets 16:26:27 mm: first example being a collection of different things, second one a collection of same things 16:26:44 mm: multi sensors is probably a more common example 16:27:49 sk: a room could also be a TM and could have different submodels in there 16:28:00 q+ 16:28:12 mm: a room is more of a location consideration 16:29:12 q- 16:29:18 sk: example from last test fest: a line which contains multiple machines as submodels 16:30:32 mm: multiple power outlet strips is also a good use case to consider how to model that 16:31:28 mjk: brings up also LED strips example 16:35:17 mm: the point is that for an outlet strip, you reference one defined submodel outlet several times in the top TM 16:36:06 mm: examples for both, multi sensor use case and mutliple power outlet strips, would help 16:37:03 sk: asks for the oneDM light strip example 16:37:40 sk: let's go for a more clear example 16:37:56 subtopic: Issue 1347 16:38:41 -> https://github.com/w3c/wot-thing-description/issues/1347 Unclearly defined DataSchema "type" 16:39:17 ek: there is a PR which was accidentally merged and should be reverted 16:40:09 -> https://github.com/w3c/wot-thing-description/pull/1254 allow type to be an array 16:40:31 ek: this breaks backwards compatibility 16:40:57 q+ 16:41:01 sk: we should do a new PR reverting that 16:43:05 ek: array of types was intended as a basic "one of" construct 16:44:06 dp: is it intended to be possible in TD 2.0? 16:44:24 ek: from his point of view: yes - should be possible in TD 2.0 16:44:55 ek: will provide PR reverting that change 16:45:58 sk: Ege can merge directly to have it available in WD 16:46:43 mm: the Security and Privacy considerations PR is ready 16:47:25 ack dape 16:47:25 -> https://github.com/w3c/wot-thing-description/pull/1387 16:47:34 brb 16:47:47 sk: merges PR 1387 16:48:12 sk: do we have some other business talking about? 16:48:17 s|pull/1387|pull/1387 PR 1387 - Update Security and Privacy considerations for WD| 16:49:09 proposal: from today we freeze the normative sections for TD 1.1 REC 16:49:38 proposal: from today we freeze the normative sections for TD 1.1 CR candidate 16:50:00 resolution: from today we freeze the normative sections for TD 1.1 CR candidate 16:50:50 [adjourned] 16:50:58 rrsagent, draft minutes 16:50:58 I have made the request to generate https://www.w3.org/2022/02/09-wot-td-minutes.html kaz 19:15:14 Zakim has left #wot-td