– DRAFT –
WoT Architecture/Profile

Agenda

<kaz> Agenda for today

https://github.com/w3c/wot-profile/pull/297#issuecomment-1324843743

Lagally: any changes to the agenda?

Ege: The PR 297 seems to have deadlock

Lagally: we can talk about that too

Lagally: What is the issue?

Ege: it is stated there

Minutes Review

23 November

Nov-23

Kaz: the minutes from 23rd meting were reviewed on the 24th, weren't they?

Lagally: I do not think so

Kaz: we should have a policy to review the minutes always on wednesdays or something like this

Lagally: We should limit inline parts in minutes

Lagally: no objections for the minutes, approved

24 November

<kaz> Nov-24

Lagally: anything to change?

Pull Requests

Architecture PR 883

<kaz> wot-architecture PR 883 - Update Implementation Report (add indices, assertions to template)

<kaz> rendered HTML of the draft Implementation Report for Architecture

Lagally: everybody have approved it, thank you Michael McCool

Profile PR 327

<kaz> wot-profile PR 327 - Implementation Report Update (indices, assertion text in template.csv)

<kaz> rendered HTML of the draft Implementation Report for Profile

Lagally: what are the automatic tests here?

McCool: we do not have automatic tests for now

Lagally: Ege can we use existing tooling of TD?

Ege: no without additional implementation

McCool: we can have them in theory

Kaz: this time during the current Charter period specifically Profile and Architecture, we should concentrate on clarifying the procedure for the manual tests rather than starting to apply potential tools for this.

Lagally: cannot be sure that I will be there at the testing call but it is not so complicated

Lagally: we should document the requirement

McCool: It is already in the implementation report but we do not say anything about consumer assertions

McCool: there is one part that is who implements it but also how to organize the report

<mlagally> proposal: to satisfy the W3C requirements to test the implementability of the profile specification, we need two implementations of consumers and things as appropriate.

RESOLUTION: to satisfy the W3C requirements to test the implementability of the profile specification, we need at least two implementations of consumers and things as appropriate.

Lagally: then we can merge the PR

PRs for Architecture

Lagally: nothing for CR transition

Issues

Issue 854

<kaz> Document At-Risk items

Lagally: we can close it

Issue 850

<kaz> Issue 850 - Contradiction with the WoT Profile spec on protocol bindings

Lagally: PR is being prepared, this can be closed

Issue 867

<kaz> Issue 867 - Siemens-Logilab implementation description

Ege: this is done

Issue 861

<kaz> Issue 861 - Normative section points to document which is WIP

Lagally: we have made the whole section informative

Issue 852

<kaz> Issue 852 - Duplicate assertion for presence of TDs

Ege: they mean the same thing for me

McCool: do they though? Maybe it is a context issue

McCool: we cannot change assertions at this point

Kaz: would suggest we explicitly mention at the 2nd assertion text that the assertion was already mentioned somewhere before the 2nd assertion in an informative manner.

Lagally: we can defer for now

issue 851

<kaz> Issue 851 - Duplicate assertion for data schemas

McCool: we should check if they are really redundant

McCool: Ege are there bindings that specify data schemas?

Ege: none of the protocol bindings actually

McCool: the may and should do not match though

Kaz: we should not do any normative changes

Ege: I think we should clean them up, I think these assertions would contradict each other if they have different results in testing

Kaz: would suggest we stop adding changes to the specs but concentrate on Testing and next Charter discussion.
… because we can't add any normative changes. If we really want to continue to add changes, we should rather record them as Editor's Notes in an informative manner. (If the changes are fatal, of course, we should add them, though.)

Issue 796

<kaz> Issue 796 - Accessibility (APA) review

McCool: the bot will add it back

PR 297 of Profile

<kaz> wot-profile PR 297 - Revised Abstract and Introduction - fixes #115 and fixes #190

Lagally: this is too difficult to review in reasonable time
… I do not know if this blocks anything
… we can still do testfest

<kaz> Sebastian's comments

Ege: Sebastian said he cannot proceed with a PR (unless this PR 297 is merged), it is not about blocking the tesfest

PR 331

<kaz> wot-profile PR 331 - narrowing down oauth required flows

McCool: you should change to another flow

Kaz: we're out of time. If needed, we should continue the discussion during the Testing call later.

[adjourned]