10:59:03 RRSAgent has joined #wot-profile 10:59:03 logging to https://www.w3.org/2022/05/25-wot-profile-irc 10:59:48 meeting: WoT Profile 10:59:50 present+ Kaz_Ashimura 11:00:37 present+ Michael_McCool 11:01:53 present+ Michael_Lagally 11:02:45 mlagally has joined #wot-profile 11:03:27 Mizushima has joined #wot-profile 11:04:33 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Architecture_WebConf#WoT_Architecture_.28Profile.29_-_May_25th.2C_2022 11:04:49 present+ Tomoaki_Mizushima 11:08:02 Ege has joined #wot-profile 11:08:52 present+ Ege_Korkan 11:10:55 topic: Minutes 11:10:56 topic: Minutes Review 11:11:03 ml: minutes are approved 11:11:07 topic: agenda 11:11:13 ml: we have some carry overs 11:11:24 i|minutes are|-> https://www.w3.org/2022/05/11-wot-profile-minutes.html May-11| 11:11:40 s/topic: Minutes Review// 11:11:49 s/topic: Minutes/topic: Minutes review/ 11:11:54 rrsagent, make log public 11:12:01 rrsagent, draft minutes 11:12:02 I have made the request to generate https://www.w3.org/2022/05/25-wot-profile-minutes.html kaz 11:12:40 topic: Explainer 11:13:05 -> https://github.com/w3c/wot-profile/pull/199 PR 199 - Profile Explainer 11:13:16 i/minutes are app/scribenick: Ege/ 11:13:55 merged 11:13:59 topic: Issues 11:14:06 subtopic: Issue 184 11:14:36 -> https://github.com/w3c/wot-profile/issues/184 Issue 184 - Check RFC assertions / only single keyword per assertion 11:15:07 -> https://github.com/w3c/wot-profile/pull/205 related PR 205 - Check RFC assertions 11:15:41 Ege has joined #wot-profile 11:16:01 merged 11:16:12 topic: PR 183 about privacy considerations 11:16:48 mm: it would be better if it is in the end of the document 11:16:56 i|it would be|-> https://github.com/w3c/wot-profile/issues/183 Issue 183 - New Section: Privacy Considerations| 11:17:12 s/topic: PR 183/subtopic: Issue 183/ 11:17:29 ... we can do a pr to move them 11:17:45 ... this is not how we do it elsewhere 11:17:52 ... it is a good place to start 11:17:57 i|it would be better|-> https://github.com/w3c/wot-profile/pull/206 related PR 206 - Security + privacy section| 11:18:03 rrsagent, draft minutes 11:18:03 I have made the request to generate https://www.w3.org/2022/05/25-wot-profile-minutes.html kaz 11:18:19 ml: then let's merge it 11:19:05 ml: I will do an editorial cleanup 11:20:25 ml: Issue 182 can be also closed since we merged that PR 11:21:09 i/Issue 182/(PR 206 merged, and Issue 183 closed)/ 11:21:32 ml: I will reopen it since we need to move it to another section 11:21:58 Topic: Issues 11:22:49 ml: td angle is fit to all, device which does not want limits, consumers which need reasonable limits 11:23:30 q+ 11:24:07 subtopic: length limit issue 11:24:32 ml: I have done some homework and looked at databases 11:26:14 ek: why taking data limits of databases 11:26:17 McCool has joined #wot-profile 11:26:23 sebastian_ has joined #wot-profile 11:26:29 ml: databases have published limits 11:26:31 q+ 11:26:31 present+ Michael_McCool 11:26:39 q+ 11:27:15 ml: programming languages as well 11:27:27 q+ not done 11:28:39 q- not 11:28:44 q- done 11:29:05 rrsagent, draft minutes 11:29:05 I have made the request to generate https://www.w3.org/2022/05/25-wot-profile-minutes.html kaz 11:30:40 q? 11:30:47 ek: we will need to pick a side and that can be politically wrong since we would be biased 11:31:03 ml: I think we should take the common maximum 11:31:35 ml: Also, we can make a logical thing and say that no id need to be more than 128 bytes 11:31:42 chair: Lagally 11:31:44 rrsagent, draft minutes 11:31:44 I have made the request to generate https://www.w3.org/2022/05/25-wot-profile-minutes.html kaz 11:31:54 sk: these links are pointing to specific implementations 11:32:36 s/topic: Issues/subtopic: Issue 220/ 11:33:22 sk: We also do not know what the limits can be in the future 11:33:29 s|td angle is fit to|-> https://github.com/w3c/wot-profile/issues/200 Issue 200 - Revisit length limits| 11:33:33 s/220/200/ 11:34:08 rrsagent, draft minutes 11:34:08 I have made the request to generate https://www.w3.org/2022/05/25-wot-profile-minutes.html kaz 11:34:32 sk: so I do not understand why we need these limits, a TD should not overwhelm that 11:34:48 ml: databases will confuse the values if they exceed a certain length 11:35:25 s|-> https://github.com/w3c/wot-profile/issues/200 Issue 200 - Revisit length limits|td angle is fit to| 11:35:32 i|td angle is fit to|-> https://github.com/w3c/wot-profile/issues/200 Issue 200 - Revisit length limits| 11:35:36 mm: we need to look at the implementations and take the common denominator 11:36:14 mm: we have to look at the different fields and their values 11:36:33 s/Topic: Issues/subtopic: Issue 220/ 11:36:45 q? 11:36:51 ack e 11:36:52 ack s 11:36:54 ack m 11:36:56 ack m 11:37:14 rrsagent, draft minutes 11:37:14 I have made the request to generate https://www.w3.org/2022/05/25-wot-profile-minutes.html kaz 11:37:34 s/Issue 220/Issue 200/ 11:37:42 q+ 11:38:08 s/subtopic: length limit issue// 11:38:15 rrsagent, draft minutes 11:38:15 I have made the request to generate https://www.w3.org/2022/05/25-wot-profile-minutes.html kaz 11:38:22 mm: we should consider different database products 11:38:49 q+ 11:40:13 ek: how will we pick the top 10, the most deployed? 11:40:18 mm: yes we can take that 11:40:37 ml: let's ask her 11:41:12 ack e 11:41:14 q+ 11:41:54 mm: we should think of community adoption and limit ourselves to what currently exists 11:42:33 q+ 11:43:38 ack k 11:43:42 kaz: I tend to agree with sebastian, wot itself does not have any limits 11:44:06 +1 kaz 11:45:17 s/any limits/any limits. Limitations are caused by the other parts, e.g., existing implementations and related external frameworks. So we should be clear about the distinction within the Profile spec if we need to describe the limitation./ 11:45:31 s/with sebastian/with Sebastian/ 11:45:39 s/wot itself/WoT itself/ 11:45:49 ek: what are limiting? TD length, key length or value of the key? 11:46:13 mm: key length is a valid point, affordance names can be very long 11:46:15 q? 11:46:19 ack e 11:46:21 ack m 11:46:22 ack m 11:46:59 ml: I think we should target all of them 11:47:37 ml: let's come up with concrete proposals 11:48:09 mm: let's start with the use cases, what is constraining 11:50:05 s/describe the limitation./describe the limitation. Also how to deal with the relationship with the existing external frameworks should be discussed by the Binding Templates from my viewpoint./ 11:53:26 q+ 11:54:11 ek: I think we need to be specific with what we are looking at 11:54:27 ml: so we have databases, data formats, UI renderers, programming languages 11:55:51 ack k 11:55:52 kaz: we would need to sync with binding templates 11:56:47 topic: PR 208 about webhooks 11:57:25 q+ 11:57:44 s/we would need to sync with binding templates/having this kind of survey of existing IoT frameworks is fine, but actual data from those external frameworks will come into WoT via Binding Templates. So I think we need to think about how to deal with limitation information (and transfer the information to the core WoT building blocks) within Binding Templates as well./ 11:59:12 ack e 11:59:20 ek: we should take draft 7 11:59:49 mm: let's wait the issue at the td to be resolved before moving on with this pr 12:00:22 i|we should take|-> https://github.com/w3c/wot-profile/pull/208 PR 208 - adding missing image| 12:00:30 i|we should take|merged| 12:02:30 i/we should/topic: PR 179/ 12:03:04 https://github.com/w3c/wot-thing-description/issues/1514 12:03:12 https://github.com/w3c/wot-thing-description/issues/1513 12:03:31 i/let's wait/topic: TD issue 1514 and 1513/ 12:03:50 topic: PR 203 12:04:16 -> https://github.com/w3c/wot-profile/pull/203 PR 203 - Cleanup core with baseline / information model 12:04:20 need further review 12:04:33 [adjourned] 12:04:42 rrsagent, draft minutes 12:04:42 I have made the request to generate https://www.w3.org/2022/05/25-wot-profile-minutes.html kaz 12:05:31 https://github.com/w3c/wot-profile/issues/209 created for 1513 and 1514 12:05:33 rrsagent, draft minutes 12:05:33 I have made the request to generate https://www.w3.org/2022/05/25-wot-profile-minutes.html kaz 13:05:08 Mizushima has left #wot-profile 13:59:26 Zakim has left #wot-profile