Meeting minutes
minutes
<kaz> Mar-9
Sebastian: March 9 minutes; last mtg before testfest
… at that time still working on WD publication
… and planning for testfest
… also discussed some wide review topics, explainer, etc; will talk about more today
… looked at some action topics
… some IANA registration topics
… context for TD, namespace, etc
Sebastian: any objections or concerns?
… hearing none, will publish
WD publication
Sebastian: new WD is "stable" version; same as CR transition
… we should revisit our schedule and plan for transition
McCool: think we still have a lot on the table, including normative changes, which will impact the IR, at-risk items, etc.
… think we need at least another month
Sebastian: concur, propose mid-May
… for CR transition
Kaz: although think we should try to review the issues and see what should go in an which should not
Sebastian: ok, let's update schedule to mid-May for CR transition, so CR *candidate* deadline is beginning of May
wide review
<kaz> PR 1382 - Create Security and Privacy Questionnaire Answers for Ver 1.1 CR Process
Sebastian: security questionniaire #1382
<sebastian> https://
McCool: done, but merged into architecture, also TAG issue updated to point to new location
explainer
<kaz> PR 1397 - Explainer 1.1
Sebastian: PR #1397
Sebastian: was feedback, but I have not addressed all the points yet
McCool: I suggest you can merge
Sebastian: ok, merging
<sebastian> https://
<sebastian> https://
<sebastian> https://
<sebastian> https://
McCool: ok, updated, finalized, and submitted. Marked as ready for review
Accessibility
<kaz> a11y-request/issues/21 - Web of Things (WoT) Thing Description 1.1 2021-01-26 > 2021-04-15
McCool: issue has been submitted, not much activity, but they did look at it last week (added link to wiki)
internationalization
<kaz> i18n-request/issues/171 - Web of Things (WoT) Thing Description 1.1 2021-02-02 > 2021-03-30
Sebastian: ongoing, in progress
TAG review
<kaz> w3ctag/design-revews/issues/715 - Web of Things (WoT) Thing Description 1.1: TAG and Security Review
Sebastian: also in progress, same as security
IANA
<kaz> 12.1 application/td+json Media Type Registration
Sebastian: registration of TM model
McCool: some points, there is a PR updating the IANA considerations for TD as well
McCool: not sure if we can update or need a new registration
Kaz: IANA is handled by PLH
… so need to talk to him
<McCool> s/hime/him/
McCool: suggest we update the TM proposed IANA registrations
… but also merge this PR so we can deal with the assertion changes in the security consideration sections
Sebastian: agree, let me record in the issue and PR
McCool: should point PLH at both issue with draft IANA for TM and updates to the section in the TD doc (after the PR above is merged)
Privacy
McCool: still have to file a review request to PING, I will do that, copying the content from the TAG/Security request
Testing
<kaz> draft implementation report
Sebastian: have new IR update (see PR), are not in bad shape, but still some "red" items we need to deal with
… suspect that the TM results are not being tested correctly, checking
McCool: note that we plan to rerun tests and report gen next Tuesday, please submit new examples, try to fill in gaps, etc. by next Monday
Sebastian: also, if you see red but you're sure you submitted an example, may be a testing problem, let ege/fady know or file an issue...
PRs
PR 1361
<kaz> PR 1361 - WIP: make hctl:hasTarget a datatype property
Sebastian: skipping for now, asking for feedback from Victor
PR 1402
<kaz> PR 1402 - Additional Security and Privacy Considerations
McCool: various new considerations, including vulnerability scanning, which is motivating "auto"
Sebastian: ok, let's merge; TAG review should point at editor's draft to see these
McCool: regarding TAG, I will add a note
PR 1447
<kaz> PR 1447 - fix: fix dataResponse definition
jan: this fixes a problem in the context file; if merge this first, diff for other things will be cleaner
… also a be/by typo fix
Sebastian: ok, let's merge this; objections?
… none, merging
PR 1419
<kaz> PR 1419 - Add auto value for the in field of SecuritySchemes
McCool: auto value for in field, allows negotiation
Sebastian: ok, will merge; may also be helpful for OPC-UA
PR 1421
<kaz> PR 1421 - feat: Add AutoSecurityScheme
McCool: this adds the auto *scheme* (above was just for "in")
Sebastian: looks like there is still a problem with the ordering
… also a conflict, if that can be cleaned up it would be helpful before we merge
jan: should we make auto the default?
McCool: already talked about that at length, is intentionally mandatory; adding a default would also break T1.0 compatibility
… but we can revisit in TD2.0
PR 1428
<kaz> PR 1428 - Cleanup Security, Privacy, and IANA Considerations
McCool: IANA/security considerations
Sebastian: unfortunately conflicts
McCool: if someone else (jan?) does minutes, I can fix
PR 1430
<kaz> PR 1430 - add link to tm schema and ednote
Sebastian: Just a small PR that provides information on how to get the TM schema for validation
… as a Note
… would be okay for me to merge this
… any comments?
Daniel: Just a comment: Why don't we also include the TM schema in the document itself like the TD schema, to be more consistent?
Sebastian: That's true
… good point
Daniel: I think we can merge it, but a follow-up PR could also point to the TD schema as well
Sebastian: There is a risk that the schema disappears
Jan: Do you mean that the TD schema should not be included at all?
Sebastian: Daniel's comment was more about being consistent
Sebastian: (adds a note to issue 1409 which was referenced by the PR)
PR 1421
<kaz> PR 1421 - feat: Add AutoSecurityScheme
Jan: PR is ready now
Sebastian: There are changes requested
Jan: There has been a comment by Michael regarding the proxy field
McCool: Should be fine as NoSec also includes proxy due to the inheritance from the base class
… currently correct, fields like name and in are not included
Sebastian: Then we can merge
PR is merged
PR 1432
<kaz> PR 1432 - split assertion on tmref overwrite
Sebastian: (reviews the diff)
… I think in the old version there was a big assertion that is now split into two
… problem is that we don't have any test results for these assertions now
… should be okay, though, as we had a lot of untested TM assertions in the testfest anyway
Sebastian: A there any objections to merging this PR?
There are none, PR is merged
PR 1433
<kaz> PR 1433 - Placeholder pattern fixes
Sebastian: This seems to be an update to the TM schema generation tools in the background
… placeholder code is updated
… also a global definition for the placeholder pattern is introduced that is referenced now in other parts of the schema
… all places where the placeholder definition is used point to the global one
… the generation script is updated accordingly
… any comments, objections to merging?
Sebastian: (proceeds to merging)
PR is merged
PR 1438
<kaz> PR 1438 - ComboSecurityScheme: oneOf and allOf can be strings according to vocab table
Sebastian: There are some fixes to assertions
… there is some discussion in the PR
Sebastian: Michael, does the PR look good?
McCool: Problem is, this PR overlaps with the ones I am working on
… merging this PR will break the PRs I am currently working on
… unless the changes to the Security Considerations were reverted
… if so, merging would be okay
Sebastian: (goes over the diff with mm)
McCool: Looks like Ege might have reverted the changes
… PR looks okay, go ahead and merge it, in the worst case I'll fix conflicts
Sebastian: proceeds to merging
PR is merged
PR 1437
<kaz> PR 1437 - Default text direction example and assertion
Sebastian: PR is by the i18n group
… there is some feedback by Addison that we should take into account
… we should wait for Ege to incorporate the changes
… let's talk about it again with Ege next week
PR 1442
<kaz> PR 1442 - add new context url to tm schema
Sebastian: seems like a JSON Schema update
… Ege updated the schemas with new @context URLs
… looks good to me, any comments?
Sebastian: (Proceeds with merging)
PR is merged
PR 1444
<kaz> PR 1444 - add text about case sensitive
Sebastian: What I try to take care of is that any values with enumerated values
Daniel: Nobody should actually try to change the values
Daniel: We could say enumerated values instead of values, then we should be fine
Sebastian: Problem is, did we specify enumerated values anywhere?
… if we use the term, we also need to explain it
Sebastian: Let us revisit this PR later, let me think about the issue a bit more
… we need to be careful with these kinds of changes
Daniel: Consumers are already expecting TDs to be case-sensitive
Sebastian: At the application level, there might be the decision to not use case sensitivity
Sebastian: (adds a comment to the PR that summarizes the discussion)
PR 1445
<kaz> PR 1445 - Instead replace remove tm:ThingModel
Sebastian: This problem came up in the discovery task force
McCool: You currently need to replace tm:ThingModel with Thing
… is Thing implied in @type at the moment?
Sebastian: No, this is not the case at the moment
McCool: TD directories is currently forced to add this value to their TD if they instatiate
… an empty @type might be illegal, though
Sebastian: I checked it, is legal according to JSON-LD
<McCool> seb: no, I tested, empty @type is ok
Sebastian: propose merging
PR 1428
<kaz> PR 1428 - Cleanup Security, Privacy, and IANA Considerations
McCool: conflicts have been resolved
Sebastian: I see these are normative sections now
McCool: yes, that is correct; IANA had assertions, moving them made this normative
… anyway, TAG had asked for that last time, so... does add to testing, though
Wrapup
Sebastian: ok, out of time, we still have more PRs, will continue next time
adjourn