10:02:23 <RRSAgent> RRSAgent has joined #wot-arch
10:02:23 <RRSAgent> logging to https://www.w3.org/2022/06/30-wot-arch-irc
10:02:29 <McCool> McCool has joined #wot-arch
10:02:55 <ktoumura> ktoumura has joined #wot-arch
10:03:03 <kaz> present+ Kaz_Ashimura, Kunihiko_Toumura, Michael_Lagally, Michael_McCool
10:03:13 <kaz> meeting: WoT Architecture
10:06:26 <kaz> present+ Tomoaki_Mizushima
10:06:59 <kaz> agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Architecture_WebConf#Architecture_June_30th.2C_2022
10:08:20 <kaz> q?
10:08:51 <kaz> scribenick: kaz
10:08:54 <kaz> topic: Minutes
10:09:03 <kaz> -> https://www.w3.org/2022/06/23-wot-arch-minutes.html June-23
10:09:05 <kaz> approved
10:09:15 <kaz> topic: Schedule
10:09:26 <kaz> -> https://github.com/w3c/wot/blob/main/charters/wg-2021-extension-plan.md extension plan
10:10:06 <kaz> mm: fyi, TD decision for CR has been deferred till Aug-3 to wait for the feedback from the next Testfest
10:10:48 <kaz> ml: who to do what for Architecture?
10:10:57 <kaz> mm: mainly manual checks
10:11:14 <kaz> ... we need two different implementations
10:11:20 <kaz> ... node-wot and something
10:11:43 <kaz> ... we've delayed the next Testfest to July 25-29
10:12:16 <kaz> ... actual CR transition resolution to be made on Aug 3
10:12:19 <kaz> ml: sounds good
10:12:46 <kaz> present+ Sebastian_Kaebisch
10:13:06 <kaz> mm: note that Toumura-san is proposing we highlight the features at-risk
10:13:30 <kaz> ml: ok
10:13:36 <kaz> ... we can update the schedule
10:13:39 <kaz> mm: can do that
10:13:55 <kaz> ml: Test 3 to be held...
10:14:01 <kaz> mm: July 25-29
10:14:29 <kaz> ml: CR transition one week earlier than TPAC?
10:14:32 <kaz> mm: yeah
10:14:49 <kaz> ... TPAC discussion should concentrate on the next Charter
10:15:18 <kaz> ml: TPAC 2022 on September 12-16
10:15:43 <kaz> mm: but kind of doubt much participation in person
10:15:56 <kaz> ... should consider remote/hybrid Plugfest
10:16:24 <kaz> ... August 3 we should make resolution for CR for Architecture, TD and Discovery
10:16:29 <kaz> ... and next week for Profile
10:17:02 <kaz> ml: expectation for Profile?
10:17:23 <kaz> mm: a month from now to see the actual Profile
10:17:37 <kaz> q?
10:17:37 <kaz> q+
10:18:29 <kaz> ack k
10:18:42 <kaz> mm: assuming we'll finish Profile work in one month
10:18:47 <mlagally> mlagally has joined #wot-arch
10:19:53 <kaz> kaz: concrete date for the plan?
10:20:04 <kaz> mm: August 31 as the current plan says
10:21:13 <kaz> (CR candidate on July 30; CR transition on August 31)
10:21:38 <kaz> topic: PRs
10:21:42 <kaz> subtopic: PR 779
10:21:56 <kaz> -> https://github.com/w3c/wot-architecture/pull/779 PR 779 - Editorial fixes
10:21:59 <kaz> merged
10:22:19 <kaz> subtopic: PR 780
10:22:29 <kaz> -> https://github.com/w3c/wot-architecture/pull/780 PR 780 - Generate static HTML file for CR publication
10:22:51 <kaz> q+
10:23:39 <kaz> ack k
10:24:13 <kaz> kaz: the next publication will be a "WD", so the directory for the publication preparation should be "2-wd" or something like. right?
10:24:16 <kaz> mm: right
10:24:25 <kaz> tou: will change the directory name
10:24:49 <kaz> mm: we could merge the PR itself and Toumura-san can change the name later
10:25:06 <kaz> ... no highlight in this draft for publication
10:25:58 <kaz> ml: Toumura-san, are you ready for being merged yourself?
10:26:21 <kaz> ... need another path before merging?
10:26:48 <kaz> mm: we can review the detail later
10:26:57 <kaz> ... review and discussion by email
10:27:29 <kaz> ... would be easier to handle the draft for review and tooling if this is merged
10:27:31 <kaz> ml: ok
10:27:44 <kaz> ... Toumura-san, what do you want?
10:27:57 <kaz> ... another look by the end of this week, maybe?
10:28:28 <kaz> q+
10:29:15 <kaz> ack k
10:29:35 <kaz> kaz: I'm also OK with merging this PR itself if Toumura-san prefers doing so
10:29:48 <kaz> ... we can create another PR to fix the directory name
10:30:45 <kaz> ml: how to deal with this then?
10:30:56 <kaz> mm: think we should merge this after the other PRs
10:31:40 <kaz> kaz: in that case, let's review the other PRs/Issues
10:31:50 <kaz> ... and Toumura-san can work on further fixes for this PR
10:32:01 <kaz> ... and we can revisit this PR next week
10:32:05 <kaz> subtopic: PR 782
10:32:31 <kaz> -> https://github.com/w3c/wot-architecture/pull/782 PR 782 - Discovery deliverable
10:32:57 <kaz> mm: additional access control
10:33:05 <kaz> merged
10:33:21 <kaz> subtopic: PR 783
10:33:31 <kaz> -> https://github.com/w3c/wot-architecture/pull/783 PR 783 - Specify TLS and DTLS versions
10:33:41 <kaz> mm: based on the discussion during the Security call
10:34:03 <kaz> ... TLS 1.3 is recommended
10:34:33 <kaz> ... don't mention the previous versions by concrete number
10:34:39 <kaz> ... e.g., 1.1 or 1.2
10:34:58 <kaz> s/or 1.2//
10:35:20 <kaz> q+
10:35:49 <kaz> [[
10:35:49 <kaz>           <span class="rfc2119-assertion"
10:35:49 <kaz>               id="arch-security-consideration-dtls-1-2">
10:35:49 <kaz>             If DTLS 1.3 cannot be used for compatibility reasons
10:35:49 <kaz>             but secure transport over UDP is appropriate,
10:35:50 <kaz>             then DTLS 1.2 [[RFC6347]]
10:35:51 <kaz>             MAY be used.</span>
10:35:53 <kaz>           <span class="rfc2119-assertion"
10:35:55 <kaz>               id="arch-security-consideration-no-earlier-tls-or-dtls">
10:35:57 <kaz>             Versions of DLTS or TLS earlier than 1.2 MUST NOT be used for
10:35:59 <kaz>             new development.
10:36:01 <kaz> ]]
10:36:06 <kaz> mm: 1.3 (or later) is recommended
10:36:30 <kaz> ml: looks good
10:36:53 <kaz> kaz: it depends on the group's policy for dealing with TLS
10:37:00 <kaz> ... and I'm OK with this description
10:37:08 <kaz> merged
10:37:16 <kaz> subtopic: PR 784
10:37:39 <kaz> -> https://github.com/w3c/wot-architecture/pull/784 PR 784 - Intro text for the binding template section
10:38:17 <kaz> mm: "Binding Templates block" should be "Binding Templates building block"
10:38:20 <kaz> sk: right
10:39:03 <kaz> ml: (fix it)
10:40:14 <kaz> s/"Binding Templates block" should be "Binding Templates building block"/"Binding Templates block addresses" should be "Binding Templates addresses"/
10:41:35 <kaz> -> https://pr-preview.s3.amazonaws.com/w3c/wot-architecture/pull/784.html#sec-binding-templates preview - 7.5 WoT Binding Templates
10:41:39 <kaz> merged
10:42:07 <kaz> subtopic: PR 776
10:42:27 <kaz> -> https://github.com/w3c/wot-architecture/pull/776 PR 776 - WIP: June 2022 Implementation Report Update
10:42:38 <kaz> mm: would like to show the latest status on my PC
10:42:41 <kaz> ml: ok
10:43:38 <kaz> mm: (shows the HTML on his PC)
10:44:04 <kaz> ... the results are still all "0", though
10:44:13 <kaz> ... identified all the assertions
10:45:07 <kaz> ... let's include the atrisk.csv and template.csv as well
10:45:55 <kaz> ... (checks the status at "Files changed")
10:46:08 <kaz> -> https://github.com/w3c/wot-architecture/pull/776/files Files changed
10:46:29 <kaz> mm: various changes including assertion names
10:46:37 <kaz> merged
10:47:16 <kaz> topic: Issues
10:47:51 <kaz> subtopic: Publication blocker(s)
10:48:24 <kaz> -> https://github.com/w3c/wot-architecture/issues/766 Issue 766 - arch-schema: Thus, the corresponding Interaction Affordances SHOULD declare a data schema to provide more detailed syntactic metadata for the data exchanged.
10:48:37 <kaz> ml: Sebastian, could you give comments?
10:49:09 <kaz> mm: seems it's a high-level requirements
10:50:55 <kaz> -> https://w3c.github.io/wot-architecture/#media-types 6.8 Media Types
10:51:03 <kaz> [[
10:51:03 <kaz> Note that many media types only identify a generic serialization format that does not provide further semantics for its elements (e.g., XML, JSON, CBOR). Thus, the corresponding Interaction Affordances SHOULD declare a data schema to provide more detailed syntactic metadata for the data exchanged.
10:51:04 <kaz> ]]
10:51:25 <kaz> sk: it's kind of impossible to define schema for binary data
10:52:25 <kaz> q+
10:53:10 <mlagally> q?
10:54:38 <McCool> q+
10:54:50 <kaz> ack k
10:55:02 <kaz> kaz: tend to agree with Sebastian's point
10:55:12 <kaz> ... but I'm OK with the current text
10:55:54 <kaz> ... but we should clarify the detailed assertions are described by the Thing Description specification here again
10:56:36 <kaz> ml: (summarizes the discussion)
10:57:33 <kaz> ... the Interaction Affordance for structured data types SHOULD be associate with a data schema to provide more detailed syntactic metadata for the data exchanged.
10:58:31 <kaz> ... details should be specified in the TD spec.
10:58:46 <kaz> -> https://github.com/w3c/wot-architecture/issues/766#issuecomment-1171075131 Lagally's comments
10:59:05 <kaz> subtopic: Issue 608
11:00:15 <kaz> -> https://github.com/w3c/wot-architecture/issues/608 Issue 608 - Relationship between "8.7 Protocol Bindings" and "9.5 WoT Binding Templates"
11:00:36 <kaz> ml: Sebastian will create a PR for some text
11:00:39 <kaz> closed
11:00:51 <mlagally> Proposal: approve merging the agreed text in issue #766 off-line.
11:01:07 <kaz> i/766/subtopic: Issue 766/
11:01:09 <mlagally> Resolution: approve merging the agreed text in issue #766 off-line.
11:01:44 <kaz> s/subtopic: Issue 766/subtopic: Issue 766 - revisited/
11:02:00 <kaz> [adjourned]
11:02:05 <kaz> rrsagent, make log public
11:02:09 <kaz> rrsagent, draft minutes
11:02:09 <RRSAgent> I have made the request to generate https://www.w3.org/2022/06/30-wot-arch-minutes.html kaz
13:02:17 <Zakim> Zakim has left #wot-arch
13:56:38 <kaz> kaz has joined #wot-arch