13:55:06 RRSAgent has joined #wot-td 13:55:06 logging to https://www.w3.org/2021/07/14-wot-td-irc 13:55:20 Mizushima has joined #wot-td 14:01:52 meeting: WoT-WG - TD-TF 14:02:03 present+ Kaz_Ashimura, Cristiano_Aguzzi 14:02:26 present+ Daniel_Peintner 14:03:06 present+ Ege_Korkan, Sebastian_Kaebisch 14:03:21 cris has joined #wot-td 14:03:21 Agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf#July_14.2C_2021 14:03:38 present+ Ben_Francis 14:03:56 sebastian has joined #wot-td 14:04:01 dape has joined #wot-td 14:06:02 present+ Michael_McCool 14:06:27 McCool has joined #wot-td 14:07:42 present+ Tomoaki_Mizushima 14:07:47 scribe: dape 14:09:04 SK: Agenda bashing 14:09:16 -> https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf#Agenda 14:10:16 TOPIC: Minutes approval 14:10:23 -> https://www.w3.org/2021/06/16-wot-td-minutes.html 14:10:32 present+ Michael_Koster 14:11:03 SK: talked about publication plans 14:11:20 s/SK: Agenda/topic: Agenda/ 14:11:26 ... VF2F TD topics 14:11:33 rrsagent, make log public 14:11:37 ... looked into PRs 14:11:37 rrsagent, draft minutes 14:11:37 I have made the request to generate https://www.w3.org/2021/07/14-wot-td-minutes.html kaz 14:11:39 q? 14:11:46 ... merged some PRs 14:12:48 MMC: some security PRs should be ready by next week (expect review from Oliver) 14:14:38 present+ Ryuichi_Matsukura 14:16:23 SK: RDF PR might be closed... need to check with Victor 14:17:13 SK: looked at issues 14:19:10 q+ 14:20:06 SK: AOB about Ege / Henry and JSON schema definitions 14:22:32 Ege: had meeting with Henry.. 14:22:42 SK: Objections to approve minutes? 14:23:06 -> none -> minutes approved 14:23:29 SUBTOPIC: F2F minutes 14:23:48 -> https://www.w3.org/2021/06/21-30-wot-vf2f-minutes.html#day6 Day 6 14:24:18 SK: talked about round tripping 14:24:38 ... Victor could fix all issues (RDF <-> JSON-TD) 14:25:03 ... gave overview about 1.1 features / updates 14:25:11 ... talked about thing models 14:25:46 ... use-case from Eclipse Ditto 14:26:15 ... McCool gave presentation about validations 14:26:25 ... talked about action model 14:26:34 ... sync vs async 14:27:04 SK: objections to merge? 14:27:15 -> none -> minutes approved 14:27:30 TOPIC: WoT Bindings 14:27:41 Ege: main point is Modbus binding 14:27:41 https://github.com/w3c/wot-binding-templates/pull/109 14:27:47 ... Cristiano created PR 14:27:59 ... binding is reviewed also by Sebastian 14:28:04 ... looks good 14:28:22 ... talked with Cristiano about schema validation 14:28:36 ... concern for other protocols as well 14:28:46 ... make sure to use the right terms 14:28:54 ... TD is flexible w.t.r. 14:29:05 ... Cristiano provided schema file 14:29:12 https://github.com/w3c/wot-binding-templates/pull/109/files?file-filters%5B%5D=.html&file-filters%5B%5D=.json&file-filters%5B%5D=.md#diff-4f12601df63ec09f14c2309b51f3a27ea60aa7a01d87718d46b9e09172464709 14:30:02 CA: >shows rendered version< 14:30:32 ... improvements from last time is introduction of schema 14:30:42 ... we have SHACL 14:30:47 ... we have JSON schema file 14:31:16 ... made some assumptions 14:31:27 ... TD needs to use same prefix 14:31:50 ... otherwise we need pre processing step 14:32:11 ... JSON schema checks context url and prefix 14:32:59 SK: We could check with Victor about other solutions 14:33:14 ... prefix usually can be used randomly 14:33:32 (I'm back) 14:33:37 CA: For SHACL file there is a specific place 14:33:46 ... for JSON schema this is not the case 14:34:28 SK: wonder about canonicalization and how it is done there 14:34:43 MMC: 1. keep prefix or 2. substitute prefixes 14:34:54 ... 3. create new names for all Urls 14:35:30 ... other concern I had was with having multiple schemas 14:35:50 ... how to do proper validation 14:36:14 CA: JSON schema needs to be replicated 14:36:26 ... in form level "own" schema is added 14:36:46 MMC: What about more extensions 14:37:09 ... we look for a wrapper schema 14:37:22 CA: Having one schema makes validation simple 14:37:48 ... saw other use-cases on the Web doing the same 14:38:49 MMC: using canonical form for validation? 14:38:58 ... fills in default values 14:39:20 ... validation should be done before canonicalization 14:39:53 ... validation process could be some specific pre-processing 14:40:20 SK: Maybe we can talk with JSON schema people 14:40:50 ... suggest we keep the current proposal 14:40:59 ... keeping prefix "modbus" 14:41:07 ... should be made clear in text 14:41:22 MMC: template would make this behavior clear 14:41:57 CA: having {{modbus}} template cannot be used as it is 14:42:29 Ege: did some tests with JSON schema 14:42:43 ... having Modbus and non-Modbus seems to fail 14:43:01 ... "modv" is also used in some examples 14:43:13 CA: will take a look, thanks 14:43:47 ... suggest to merge the PR soon.. and move on from there 14:44:17 q? 14:44:20 ack dape 14:44:39 CA: added small readme also 14:44:40 q+ 14:44:55 SK: support merging 14:45:48 DP: noted that github "preview" link does not work any longer 14:45:55 ack dape 14:46:40 https://github.com/w3c/wot-binding-templates/pull/109 14:47:16 CA: Yes, would be good if it can handle files other than index.html 14:50:03 Kaz: Let's merge and see whether it can be resolved 14:50:21 ... comment: the header should not link directly 14:50:29 CA: temporary situation 14:50:38 Ege: OK with merging also 14:50:58 ... no more concerns mentioned 14:51:17 ... will do the merge 14:51:27 SK: use same pattern for other bindings also? 14:51:29 Ege: Yes 14:51:39 TOPIC: PRs Overview 14:51:58 SUBTOPIC: Add subscribeallevents and unsubscribeallevents operations - closes #1082 14:52:05 -> https://github.com/w3c/wot-thing-description/pull/1191 14:52:37 Ben: helps getting WebThings platform to be compliant 14:52:46 ... observing in one operation 14:53:41 ... a bit unclear what has to be modified manually.. and what is auto-generated 14:53:50 ... I think I got it right in the end 14:54:02 SK: looks good to me 14:54:47 Ben: updates for architecture are to be followed 14:54:53 +1 for merging :) 14:54:56 SK: Any comments? 14:55:13 ... looks we can merge 14:55:36 ... thank you Ben 14:55:59 SUBTOPIC: correct element for ComboSecurity assertion and add unique id #1184 14:56:04 -> https://github.com/w3c/wot-thing-description/pull/1184 14:56:11 SK: seems to be a typo fix 14:56:33 Ege: yes, span vs scan 14:57:04 q+ 14:57:44 SK: Fady is not yet an official W3C member 14:58:04 ... we work on fixing the situation 14:58:30 Kaz: Do we want to wait or continue.. marking as non-substantial 14:58:55 ... given this is just a typo fix merging seems ok 14:59:11 SK: merging ... 14:59:38 SUBTOPIC: fix: replace "name" with "title" in TM example #1175 14:59:42 -> https://github.com/w3c/wot-thing-description/pull/1175 15:00:05 SK: fix is okay 15:00:16 ... issue that it is changed in index.html only 15:00:59 Kaz: editorial fix again 15:02:11 s/again/again, but we need to fix the index.template.html as well. so would suggest you create another PR to fix the index.template.html (and index.html as the result of the tooling)/ 15:02:34 SK: will let Jan know that both files have to be updated 15:03:18 SUBTOPIC: TD Signatures #1151 15:03:22 -> https://github.com/w3c/wot-thing-description/pull/1151 15:03:33 MMC: Oliver will take a look 15:03:42 ... still some things to do 15:04:03 ... using "Signature" term caused conflicts 15:04:21 ... terminology vs vocabulary 15:06:16 ... issue in Section 5.2 15:06:47 q? 15:06:53 q- 15:06:59 ... will create issue about that 15:07:19 ... once we get feedback from Oliver the rest should be rather minor 15:07:41 SK: will also ping Oliver 15:08:21 SUBTOPIC: Other PRs 15:08:35 SK: other PRs are about auto-updating and such 15:09:02 ... changing package versions 15:09:37 MMC: should test these changes before merging 15:09:44 SK: Daniel will have a look 15:10:15 SUBTOPIC: WIP: swap securtiy and securityDefinition in context file 15:10:19 -> https://github.com/w3c/wot-thing-description/pull/937 15:10:24 SK: should check with Victor 15:10:34 MMC: Yes, I think this should be fixed by other PRs 15:10:50 ... but let's ask Victor 15:11:13 TOPIC: Issues 15:11:27 SUBTOPIC: Describing initial connection #878 15:11:30 -> https://github.com/w3c/wot-thing-description/issues/878 15:11:39 q+ 15:11:41 SK: Old issue 15:12:00 ... metadata about initial connection 15:12:12 ... subprotocol et cetera 15:12:52 ... WebSocket, MQTT, ... mention the endpoint ... no more special information on interaction level 15:13:22 ... idea: using top-level information 15:13:37 ... example from Ben by means of WebThing 15:13:58 ... no need to repeat the same information over and over again 15:14:12 ... we have "base" but we might need more complex structure 15:14:41 ... introduce new term "bases" .. 15:14:59 ... define endpoints and refer to it on interaction level 15:15:14 ... another proposal from Ben .. using global form 15:15:31 ... more opinions / solutions 15:15:44 MMC: 2 issues come to my mind 15:15:48 ... what about security 15:15:59 ... initial security bootstrapping 15:16:32 SK: forms can contain security 15:16:52 MMC: Yes, but we might need to override it 15:17:13 ... first getting thing link 15:17:22 ... afterwards the full TD 15:17:56 ... anyhow, security should be considered for these examples 15:18:20 Ben: i don't think we have security bootstrapping issue 15:18:30 ... multiple bases is orthogonal 15:18:56 ... this is more about having a persisting connection 15:19:34 ... in case of WebSocket and subprotocol it should know when to use it and to setup just one connection 15:19:50 CA: I reviewed the proposal 15:19:56 ... none is solving all problems 15:20:08 ... moreover, backward compatibility is also an issue 15:20:23 ... shift some features to 2.90 15:20:33 s/2.90/2.0 15:20:35 q? 15:20:37 ack m 15:21:03 ... otherwise go on with Bens proposal that does not breaking changes 15:21:19 SK: backward compatibility is a real issue. right 15:22:28 ... ignoring is ok... but interoperability is not working 15:22:41 Ege: we have 2 things 15:22:50 ... base 15:22:56 ... and initial connection 15:22:57 q+ 15:23:25 MMC: what about using action for onboarding 15:23:39 ... can be used by "older" implementations 15:24:06 Ege: How to know that one actions depends on another action 15:24:22 MMC: needs to be labelled 15:24:45 Ege: node-wot for example would not keep connection 15:25:01 ... no good solution for old consumers 15:25:19 MMC: Do we properly support MQTT in 1.0 ? 15:25:43 ... if not, no need to further tackle this 15:27:14 Ben: Initial problem: never really defined properly... everyone doing it in its own way 15:27:23 ... hence no backwards compatibility 15:27:27 MMC: Agree 15:27:52 Ege: minimal change ... old consumer should not fail 15:28:04 .. eg. uses bases and not base 15:28:37 CA: I was thinking more about syntax 15:28:55 ... forms at root level seems less intrusive 15:29:06 Ege: does not solve multiple base 15:29:18 CA: Yes, should be post-poned to 2.0 15:29:49 https://github.com/w3c/wot-thing-description/issues/1192 15:30:13 Ege: Bug in current editors draft (see link above)? 15:30:42 Ben: what does "with default" mean 15:30:54 Ege: if nothing is defined, default kicks in 15:31:35 SK: I was thinking about "initconnection" op value 15:32:24 Ege: consequence would be to check first about "initconnection" 15:32:36 ... mixes concepts 15:33:26 CA: href required by TD .. but not by WebSocket 15:33:34 Ege: Yes, having empty string 15:34:09 Ben: Yes, forms is mandatory.. not needed by WebSocket only 15:34:36 SK: Another path could be saying we need to post-pone till 2.0 15:34:46 .. or form needs to be present for now 15:35:35 Ben: my goal is to make WebThings compliant 15:35:49 ... option 1: using link 15:36:03 ... option 2: use bug with empty forms 15:37:15 CA: should first talk how to handle the bug 15:37:37 MMC: like the suggestion to have a new op (like proposed by Sebastian) 15:37:53 Ben: in the case of WebThing... the op is "all" 15:38:31 ... single websocket connection 15:38:41 Ege: kind of a mis-use of semantics 15:38:48 .. why not listing them all 15:39:13 https://github.com/w3c/wot-thing-description/issues/1070 15:39:14 https://github.com/w3c/wot-thing-description/issues/1070 15:39:34 s|https://github.com/w3c/wot-thing-description/issues/1070|| 15:39:42 Ben: created issue, see link above 15:40:06 SK: wonder why it closed? 15:40:21 Ben: I did close it.. assuming op can be blank 15:40:40 MMC: "all" is bit weird 15:40:51 .... maybe you just want to do some 15:41:16 ... still like op "open" or so 15:41:34 Ege: How to know when to do this form 15:42:05 CA: once it is there.. every affordance should use it 15:42:18 MMC: same protocol 15:43:01 ... using same connection 15:43:50 CA: WebThing has just top-level form... 15:44:00 MMC: how to distinguish href? 15:44:06 Ben: are the same 15:45:28 ... pubsub in WebThings is not yet fully supported 15:45:38 ... looking for simplest solution 15:46:15 MMC: having top level form looks like simplest solution 15:47:11 Ben: if we had op "open" and forms in each interaction. Does this work for MQTT? 15:47:23 Ege: makes sense 15:47:56 q+ 15:48:20 MMC: does prefix part indicate broker? 15:48:23 Ege: Yes 15:48:25 ack McCool 15:49:10 q+ 15:49:45 Ege: annoying problem. mqtt://localhost:1883/myThings/temp 15:50:55 ... in form in property myThings/temp it is not set whether to use with or without slash 15:52:45 MMC: using fragment identifier may help 15:53:00 Ege: might work 15:54:17 .... in MQTT # is special... like wildcard 15:54:22 ... should use $ 15:54:40 MMC: MQTT never sees the pound sign (#) 15:54:49 s/.... in/... in/ 15:54:58 s/# is/"#" is/ 15:55:20 s/should use $/should use "$" instead/ 15:56:16 SK: Suggest getting back to global connection information 15:56:27 ... does new op type work 15:56:41 MMC: Looks like 15:57:34 DP: wonder whether we need the counterpart "close" to 15:57:43 MMC: Suggest to wait for use-case 15:58:00 s/" to/" too/ 15:58:19 ... or call it "initialized" to avoid questions 15:59:29 s/initialized/initialize/ 15:59:59 (another option would be "connect" for the global op) 16:00:28 Ben/Ege: >discussions about WebThings and base< 16:01:05 Ben: not sure about the problem we are solving 16:01:31 MK: WebThing still needs selector 16:01:35 q? 16:01:41 ack dape 16:02:08 MMC: Form is required .. but for example form can be inferred.. also in ECHONET 16:02:57 CA: problem we solve: put form there for WebSocket 16:04:04 Ben: for http and WS we do not have a problem 16:04:22 SK: suggest to continue the discussion in issue 16:04:33 ... root form looks promising 16:04:42 (sorry, another meeting, need to drop) 16:05:49 [adjourned] 16:05:53 rrsagent, make log public 16:06:01 rrsagent, draft minutes 16:06:01 I have made the request to generate https://www.w3.org/2021/07/14-wot-td-minutes.html kaz 16:09:03 Mizushima has left #wot-td 17:21:26 benfrancis2 has joined #wot-td 18:49:22 Zakim has left #wot-td