11:00:26 <RRSAgent> RRSAgent has joined #wot-arch
11:00:26 <RRSAgent> logging to https://www.w3.org/2022/12/01-wot-arch-irc
11:00:55 <kaz> meeting: WoT Architecture/Profile
11:01:26 <kaz> chair: Lagally
11:01:32 <mlagally_> mlagally_ has joined #wot-arch
11:01:36 <kaz> present+ Kaz_Ashimura, Michael_Lagally
11:05:20 <kaz> present+ Ryuichi_Matsukura
11:07:16 <kaz> present+ Sebastian_Kaebisch, Tomoaki_Mizushima
11:07:52 <kaz> scribenick: kaz
11:08:13 <kaz> agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Architecture_WebConf#Architecture_.2B_Profile_-_Dec_1st.2C_2022
11:09:46 <kaz> topic: Agenda
11:09:53 <kaz> ml: (goes through the agenda)
11:10:12 <kaz> -> https://www.w3.org/WoT/IG/wiki/WG_WoT_Architecture_WebConf#Architecture_.2B_Profile_-_Dec_1st.2C_2022 agenda for today
11:12:28 <kaz> topic: Minutes
11:12:32 <kaz> -> https://www.w3.org/2022/11/30-wot-profile-minutes.html Nov-30
11:12:37 <kaz> ml: (goes through the minutes)
11:14:33 <kaz> approved
11:15:23 <kaz> topic: PR 297
11:15:48 <kaz> -> https://github.com/w3c/wot-profile/pull/297 PR 297 - Revised Abstract and Introduction - fixes #115 and fixes #190
11:15:58 <kaz> ml: hard to review
11:16:19 <kaz> sk: did you see the changes themselves?
11:16:29 <kaz> ... think it's a huge improvement basically
11:16:58 <kaz> ... I can't add further improvement until this PR is merged
11:17:02 <kaz> ml: did see it
11:17:51 <kaz> ... some of the changes are really useful
11:18:16 <kaz> ... but we should thoroughly review each PR
11:18:54 <kaz> sk: would like to update the introduction section as soon as possible...
11:19:22 <kaz> q
11:19:26 <kaz> s/q//
11:19:28 <kaz> q+
11:19:47 <kaz> ml: currently we're focusing on the Testing
11:20:12 <kaz> ... so if you could hold it, wouldn't be harmful
11:20:19 <kaz> ... McCool is working on splitting this big PR
11:21:21 <kaz> ack
11:21:25 <kaz> s/ack//
11:21:36 <kaz> kaz: we had discussion on this PR yesterday
11:21:56 <kaz> ... and decided that Michael McCool would split this PR into smaller pieces
11:22:19 <kaz> ... so Sebastian, if you want, you can also create a small PR to update the introduction section
11:22:38 <kaz> ... and let McCool and Lagally know about your new PR
11:23:26 <kaz> sk: would prefer merging this first and then add my modification
11:26:28 <kaz> kaz: again, the most of the proposed changes from this PR 297 should be included in the next WD
11:26:51 <kaz> ... but we want to review the whole changes thoroughly based on the decision yesterday
11:27:15 <kaz> ... in that case, Sebastian can generate his own smaller PR to modify the introduction section
11:27:23 <kaz> ... and maybe we can merge that PR first
11:27:46 <kaz> ... and review McCool's split smaller PRs for this PR 297 after that
11:27:50 <kaz> ml: agree
11:29:45 <kaz> sk: would be easier to merge this PR first for examples, etc.
11:29:58 <kaz> ... and add my modification referring to them
11:31:09 <kaz> ml: Sebastian, you can take several points from Ben's PR and generate your own PR
11:31:09 <kaz> sk: ok
11:31:15 <kaz> kaz: really appreciated
11:31:51 <kaz> s/topic: PR 297/subtopic: PR 297/
11:32:02 <kaz> i/subtopic: PR 297/topic: Profile/
11:32:41 <kaz> subtopic: Authentication constraints
11:34:16 <kaz> -> https://w3c.github.io/wot-thing-description/#oauth2securityscheme Thing Description 1.1 - 5.3.3.10 OAuth2SecurityScheme
11:34:56 <mlagally_> https://github.com/w3c/wot-thing-description/blob/186e1096b138e959a8e382da24185f1ad5624556/testing/all-TD-implementations.csv
11:35:12 <kaz> s/https/-> https/
11:35:24 <kaz> s/csv/csv all-TD-implementations.csv/
11:35:35 <kaz> ml: difficulty with implementing OAuth authentication
11:36:12 <kaz> ... the right thing should be adapting the code flow
11:36:23 <kaz> sk: Siemens has been trying to implement it
11:36:46 <kaz> ... however, no guarantee for the Testfest
11:37:23 <kaz> -> https://github.com/w3c/wot-profile/pull/331 PR 331 - narrowing down oauth required flows
11:38:01 <kaz> -> https://pr-preview.s3.amazonaws.com/w3c/wot-profile/331/6ac4097...af375ca.html#common-constraints-security diff - 6.4 Security
11:38:40 <kaz> q+
11:39:50 <kaz> ack k
11:39:56 <kaz> kaz: the content is ok
11:40:12 <kaz> ... but the description of the 2nd sentence is a bit odd
11:40:23 <kaz> ... first sentence: Conforant Consumers
11:40:29 <kaz> ... 2nd: A Thing
11:40:45 <kaz> ... 3rd: Conformant Consumers
11:40:54 <kaz> ... 4th: Conformant Things
11:41:19 <kaz> ... so the 2nd sentence should also say "Conformant Things", shouldn't it?
11:41:25 <kaz> ml: would be better
11:42:11 <kaz> sk: does this question go to the Providers or Consumers?
11:42:56 <kaz> ... a Consumer might not support it due to performance issue
11:43:03 <kaz> q?
11:43:04 <kaz> q+
11:45:04 <kaz> kaz: do you mean a potential intermediary which supports OAuth security for a Consumer?
11:45:12 <kaz> ack k
11:45:20 <kaz> sk: don't want to make the story complicated, though
11:45:36 <kaz> ml: what we could do is requiring security
11:46:11 <kaz> ... BasicSecurityScheme is mandated and OAuth2SecurityScheme is optional
11:47:31 <kaz> ... let's ask McCool for opinion again
11:48:06 <kaz> subtopic: Links
11:48:44 <kaz> -> https://github.com/w3c/wot-profile/pull/315 PR 315 - Improve link assertions
11:49:06 <kaz> ml: changes requested
11:50:13 <kaz> ->  https://pr-preview.s3.amazonaws.com/w3c/wot-profile/315/f041378...0d9d2e3.html#common-constraints-links diff - 6.5 Links
11:50:21 <kaz> ml: (goes through the changes within the diff)
11:51:05 <kaz> q+
11:51:26 <kaz> ... (explains the Note)
11:51:27 <kaz> [[
11:51:38 <kaz> NOTE
11:51:38 <kaz>  These links enable consumers to interpret linked content that is provided by the link target in an unambiguous way. This interpretation is a "best effort" mechanism, that depends on the capabilities of the consumer. A consumer with a browser could render HTML content, a consumer with a PDF engine can display PDF content, a consumer with a dot-matrix display only can display icons.
11:51:39 <kaz>  For consumers that can render images or documents this implies to display appropriate documentation to a human reader.
11:51:40 <kaz>  Consumers that are capable of working with nested things and thing model structures are able to navigate between things and thing models in a well defined way.
11:51:43 <kaz> ]]
11:53:30 <kaz> kaz: does this mean we expect the implementers to handle expected data to be negotiated between the server side and the client side like the language negotiation mechanism?
11:53:52 <kaz> ... e.g., en.html, ja.html, fr.html
11:54:18 <kaz> ml: not really sure about language negotiation mechanism...
11:54:54 <kaz> sk: what you have there at section 6.5
11:55:15 <kaz> ... maybe you can list the possible link relation types there
11:55:48 <kaz> ... to be supported by TD
11:55:57 <kaz> ... can quickly check it
11:56:17 <sebastian> sebastian has joined #wot-arch
11:56:18 <sebastian> https://w3c.github.io/wot-thing-description/#link
11:56:54 <kaz> s/https/-> https/
11:57:05 <kaz> s/link/link Thing Description 1.1 - 5.3.4.1 Link/
11:57:52 <kaz> sk: link parameters listed within the section 5.3.4.1 of Thing Description 1.1
11:58:09 <kaz> ... with the assignment of mandatory or optional
11:59:00 <kaz> q+
12:00:03 <kaz> ... the first entry (href) and the last entry (hreflang) from the table within section "6.5 Links" to be removed
12:00:34 <kaz> ack k
12:01:09 <kaz> kaz: all the information from the table is redundant, given there is already a table within TD
12:01:17 <kaz> s/TD/TD, isn't it?
12:01:29 <kaz> ml: Sebastian, you can create an issue about this
12:01:52 <kaz> [adjourned]
12:01:56 <kaz> rrsagent, make log public
12:01:59 <kaz> rrsagent, draft minutes
12:01:59 <RRSAgent> I have made the request to generate https://www.w3.org/2022/12/01-wot-arch-minutes.html kaz