11:01:10 <RRSAgent> RRSAgent has joined #wot-profile
11:01:10 <RRSAgent> logging to https://www.w3.org/2022/06/15-wot-profile-irc
11:01:19 <kaz> meeting: WoT Profile
11:03:18 <Mizushima> Mizushima has joined #wot-profile
11:03:50 <kaz> chair: Lagally
11:04:02 <kaz> present+ Kaz_Ashimura, Michael_Lagally, Michael_McCool
11:06:13 <kaz> present+ Tomoaki_Mizushima
11:06:59 <mlagally> mlagally has joined #wot-profile
11:07:35 <kaz> agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Architecture_WebConf#WoT_Architecture_.28Profile.29_-_June_13th.2C_2022
11:08:10 <McCool> McCool has joined #wot-profile
11:08:45 <kaz> scribenick: McCool
11:08:48 <kaz> topic: Minutes
11:08:57 <kaz> -> https://www.w3.org/2022/05/25-wot-profile-minutes.html May-25
11:11:26 <mlagally> https://github.com/w3c/wot-profile/issues/179
11:12:59 <McCool> reviewing minutes, notes about JSON Schema, using version 7
11:15:36 <McCool> ml: point is there is another spec for validation that includes particular formats like date-time
11:16:33 <McCool> ml: there is an issue, see minutes
11:16:59 <McCool> ... issue #209 in wot-profile
11:17:19 <McCool> ml: approve?
11:17:25 <McCool> ml: no objections, approved
11:17:38 <McCool> topic: Housekeeping
11:17:48 <McCool> subtopic: issue #203
11:18:18 <McCool> ml: replace "core" with "baseline"
11:18:44 <McCool> ... some comments from bf about other changes needed, ml wanted to limit scope
11:19:51 <Ege> Ege has joined #wot-profile
11:20:02 <Ege> q+
11:20:14 <kaz> i|replace|-> https://github.com/w3c/wot-profile/pull/203 PR 203 - Cleanup core with baseline / information model|
11:20:20 <kaz> present+ Ege_Korkan
11:20:26 <kaz> zakim, who is on the call?
11:20:26 <Zakim> Present: Kaz_Ashimura, Michael_Lagally, Michael_McCool, Tomoaki_Mizushima, Ege_Korkan
11:20:34 <McCool> mm: are "baseline profile" and "HTTP baseline profile" different>
11:21:23 <McCool> ml: yes, a little inconsistent
11:21:50 <McCool> ege: not a small issue, Baseline = core, but HTTP Baseline is more specific
11:22:14 <McCool> ml: this PR is a cleanup pass, not a reorg
11:23:18 <kaz> q+
11:23:21 <kaz> ack e
11:24:05 <McCool> mm: still, would it be possible to fix all ocurrences of "Baseline" to "HTTP Baseline"?
11:24:20 <McCool> ml: propose we do that in another iteration
11:24:33 <McCool> mm: ok, but need an issue
11:25:46 <kaz> kaz: I'm OK with that but we should fix the spec asap
11:25:50 <McCool> ... bottom line is we agreed to use "HTTP Baseline Profile" only, so any use of "Baseline Profile" is a mistake and needs to be fixed
11:25:59 <kaz> i/I'm OK/sribenick: kaz/
11:26:14 <kaz> i/bottom/scribenick: McCool/
11:26:27 <kaz> s/... bottom/mm: bottom/
11:28:03 <McCool> ml: creates issue #210
11:28:13 <McCool> ege: image also needs to be updated
11:28:30 <McCool> ml: as image has other problems, will create another issue for that
11:28:44 <McCool> ml: creates issue #211
11:30:22 <McCool> ml: assigning both to ege
11:30:39 <kaz> i|image also|-> https://github.com/w3c/wot-profile/issues/210 Issue 210 - Consistent use HTTP baseline profile|
11:31:12 <kaz> i|assigning|-> https://github.com/w3c/wot-profile/issues/211 Issue 211 - Image update for HTTP baseline profile|
11:32:23 <McCool> mm: how exactly should figure be updated?
11:32:35 <McCool> ege: is it generic, or for a specific profile?
11:35:32 <McCool> mm: I think this depends on the context of the text; the current text is specific but if we edit it to be more generic, figure will change in different ways
11:36:12 <kaz> q?
11:36:19 <kaz> ack k
11:36:31 <kaz> rrsagent, make log public
11:36:35 <kaz> rrsagent, draft minutes
11:36:35 <RRSAgent> I have made the request to generate https://www.w3.org/2022/06/15-wot-profile-minutes.html kaz
11:36:41 <McCool> ml: also a large section marked as at-risk; the data model
11:36:58 <McCool> mm: this was the section that bf was concerned about?
11:37:23 <McCool> ml: yes; so is in there, but marked as being at-risk, with reference to the issue where it is being discussed
11:37:34 <kaz> s/issue #203/PR #203/
11:37:36 <kaz> rrsagent, draft minutes
11:37:36 <RRSAgent> I have made the request to generate https://www.w3.org/2022/06/15-wot-profile-minutes.html kaz
11:37:49 <kaz> s/sribenick:/scribenick:/
11:37:50 <kaz> rrsagent, draft minutes
11:37:50 <RRSAgent> I have made the request to generate https://www.w3.org/2022/06/15-wot-profile-minutes.html kaz
11:38:12 <McCool> mm: anyway, ok with merging this PR for now, even if imperfect
11:38:31 <McCool> topic: Issue #200
11:38:39 <McCool> ml: length limits and constraints
11:39:13 <McCool> ml: agree these values are arbitrary...
11:39:32 <McCool> ... let's talk about whether we want constraints or not
11:42:49 <McCool> mm: couple of thoughts; interconversion to/from; constrained devices; TM constraints
11:43:26 <McCool> ml: example, ids that exceed length limits, first 512 are identical
11:43:32 <McCool> ... that would break use cases
11:43:57 <McCool> ... so these constraints are a contract, compliant things must not provide longer values
11:44:55 <McCool> mm: and even high-end systems, e.g. relational databases, may have finite limits
11:47:13 <Ege> q+
11:48:33 <McCool> mm: think we should lay out use cases; I see three, interconversion, constrained devices, and other systems with limits (databases)
11:48:56 <McCool> ... interconversion though is very difficult, may be many format in conflict with each other
11:49:16 <McCool> ege: agree that interconversion raises a very complicated set of issues
11:49:50 <McCool> ... think we should drive with basis on constrained devices and databases
11:50:23 <kaz> rrsagent, draft minutes
11:50:23 <RRSAgent> I have made the request to generate https://www.w3.org/2022/06/15-wot-profile-minutes.html kaz
11:50:35 <McCool> ege: btw prog langs don't make sense a driver of limits, tend to be very high
11:50:51 <McCool> ... need to look at other constraints, e.g. relational databases
11:51:31 <McCool> ... also watch out for "bytes" vs "characters"
11:51:39 <kaz> q+
11:51:39 <McCool> mm: should use UTF-8 and bytes
11:51:41 <kaz> ack e
11:52:11 <McCool> ege: need to relate to JSON string lengths
11:52:43 <McCool> kaz: can think about this by ourselves, but might want to talk to other SDOs, i.e. IETF, OneM2M, etc.
11:52:59 <McCool> ml: did give a couple of spec references
11:54:09 <McCool> mm: not only what limits are, but how they are defined, e.g. bytes vs chars
11:54:19 <McCool> kaz: also IEC dictionary people
11:54:59 <McCool> mm: right, UTF-8 "character" can expand to up to 4 bytes in memory...
11:56:17 <McCool> ml: agree that bytes are better, less confusing
11:56:43 <McCool> mm: and also gives a tighter limit
11:57:05 <McCool> ege: JSON validation is troublesome, may need a special validator
11:57:54 <McCool> ml: ok, let's go with bytes, let's start with a strawman
11:59:17 <kaz> [adjourned]
11:59:23 <kaz> rrsagent, draft minutes
11:59:23 <RRSAgent> I have made the request to generate https://www.w3.org/2022/06/15-wot-profile-minutes.html kaz