Meeting minutes
The meeting starts
Minutes
since last meeting, February 13th was cancel, there are no minutes to review
the agenda items are carried forward in today's meeting
<kaz> Jan-23
January 23th minutes are reviewed now
2 resolutions were proposed during the meeting
no objections or corrections on the minutes are presented
then minutes are published
CR Bugfixes
Pull #462: some changes do not need a new CR, they can be considered as editorial changes.
McCool: there is no rush on this, let's wait another week. Let me update the change log and have everything clean.
… the main impact will be testing time, since we will need to repeat the testing
McCool: seems that this can be closed since hitachi has two implementations covering
McCool: the only thing is that we need the ontology
Andrea: I can upload the ontology extension and the context for this
Kaz: Basically, we should use some specific URI as the basis for all the WoT specs' namespaces.
McCool: the base URI should be w3.org/2022/wot/ under which we could to anything we want
Kaz: We used "https://www.w3.org/2019/wot/td/v1" for WoT Thing Description 1.0 REC
... while we're using "https://www.w3.org/2022/wot/td/v1.1" for WoT Thing Description 1.1 CR.
... I still think that namespace URI is just a string to identify the resource, so I don't think we should use year-specific namespaces for each spec version. We can simply reuse the base URI of the 1.0 namespace, i.e., "https://www.w3.org/2019/wot/td/" for v1.1, i.e. https://www.w3.org/2019/wot/td/v1.1".
... If we really want to avoid including 2019 within the namespace URI for TD 1.1, it would be better to use "https://www.w3.org/wot/td/" as the base URI for both 1.0 and 1.1.
McCool: I'm going to add this to the PR #462
McCool: I will also publish a separate issue for this
issue #w3c/
<McCool_> w3c/
Kaz: BTW, I've just noticed (1) the WoT Thing Description 1.1 CR uses both "https://
McCool: need to talk with Sebastian again.
other topics
registrations #issue 187
McCool: is there anything left to check on this topic?
McCool: seems that with the DID done, there is nothing left
next topic: no other PR pending
next topic: review PRs
Issue #403
<kaz> Issue 403 - Refine DNS-SD Name Requirements and IANA Consideration
Review issue #403
McCool: this should be closed
the registration has been completed but the spec needs to be updated
(mccool links the issue with the pending PR)
Issue 448
<kaz> Issue 448 - Assertion for DNS referencing UDP may be split normative/informative
Review issue #448
the issue here is that if we clean up after the PR it will be easy to mark UDP as informative, let's resolve it after the PR
Issue 328
<kaz> Issue 328 - CR WD review June 2022
McCool: this issue could be closed (issue #328)
McCool: I think probably all the issues marked as "propose closing" can be closed, there are 30 open
… I suggest next meeting we will close them. Have a look at them and if there is any issue bring it for the next meeting
<kaz> [adjourned]