Meeting minutes
Minutes
McCool: DeutscheTelekom gave ok on reusing their slides in the conference
McCool: We did resolutions to proceed to PRs
McCool: We have agreed on the profile resolution in the call just before
McCool: We could not join the same call with Ege so we could not meet
Kaz: Have you contacted Takenaka about using their slides?
McCool: Not yet, I need information from Sebastian as well
Kaz: Takenaka contributed to last TPAC, it would be better to mention them as well
McCool: I will make sure to dedicate same time to DeutscheTelekom and Takenaka
McCool: I would like some slides from Echonet as well
CCNC Presentation
McCool: give me your slides please, I want to have a balanced
Ege: do you want me to ask for permissions?
… otherwise the slides are on the cg repo
McCool: yes it would be nice
Kaz: maybe one-two pagers like ECHONET/Takenaka provided for the TPAC breakout
McCool: right
Ege: do you want sifis home too?
McCool: maybe yes but we want to focus on commercial implementations
Cancellations
McCool: we have some cancellations due to charter discussion
https://
<kaz> Use Cases call will be held on Jan 10
<kaz> WebEx already available; McCool will send out an updated calendar
<kaz> Marketing call will be cancelled on Jan 10
Testfest
McCool: I have merged some results from the testfest for all specs
McCool: We will review them in the testing call
McCool: any updates?
McCool: we did some progress but still many at risk items, especially discovery
McCool: TD is in a good shape
Kaz: I agree we are getting in a better direction, but am still wondering why some of the basic assertions are not covered yet, e.g., Architecture's abstraction of device interface using TD. We should clarify what's happening during the Testing call later.
Ege: I think giving a deadline for contributions would also work
McCool: let's talk in testing
Kaz: agree we talk the detail during the Testing call
Publications
Architecture, TD, Discovery
McCool: publication prep still ongoing
… good point is we can use auto publication for CR as well
… Kaz will continue to work on that
McCool: We have issue 809 of architecture in the agenda, but it is a carryover from last wekk
Kaz: we can skip the issue 809 discussion it
McCool: on the other hand, Kaz pointed out several issues
McCool: we have to ignore some link checker errors, they are false positive
McCool: but need to add some fixes, and Kaz will work on that
IANA Entry for Discovery
IANA registry for WoT entries changed the text entry
McCool: The TXT key fields within the IANA registry entry for WoT have been modified.
DID Entry
McCool: we did not define a URL in our document so we cannot do a DID endpoint name
McCool: We can also split the discovery document in the next charter, one for intro and one for exploration
Profile
McCool: WD to be published after 3 CRs
WG Charter discussion
McCool: how to deal with the agenda?
(no specific opinions)
McCool: let's add initial agenda right below this schedule section then
Sebastian: we should talk about liaisons with related SDOs
… including industry-based digital approaches, etc.
<sebastian_> https://
Sebastian: we already have OPC UA, BACnet, etc.
… Matter, ECHONET, etc.
McCool: let's put that on Wednesday
… and let's use the 4th day, Thursday for final drafting
Kaz: We should clarify our policy for liaisons a bit and prioritize industrial applications
Kaz: that would be useful to draft the text of the charter
McCool: Let me update this, we have to clarify how we handle them
Ege: Will we discuss arch update for the new charter? maybe tomorrow?
Lagally: The agenda is empty at the moment, we can do that
McCool: I can also add overall organization
Kaz: maybe the first day can be a brainstorming and the other days focused on the deliverables
McCool: that's possible but let's see
McCool: we have a coverage gaps file at the use cases repository
McCool: we will work on it again on January 10th
McCool: we have some topics in the agenda but we will get back to it after the charter discussion
Liaisons
Koster: I am discussing regarding BACnet collaboration but I need some help with the official parts about the liaisons
McCool: We need a consistent way to organize that
McCool: so starting with OPC UA and echonet would help us come up with a template as well
McCool: I am also looking at Matter at the moment
https://
Ege: there is IDTA Liaison idea from Sebastian in the issue I have linked above
McCool: we should separate the liaisons I guess. Some are protocols other are more like data modelling
Kaz: yeah, that's why I suggested we should clarify our policy and priority for our expected liaisons with related SDOs like OPC, ECHONET and DTDL.
Kaz: btw, Koster, do you want to establish an official liaison with Matter, BACnet, etc.?
Koster: I just have the contacts
Koster: I cannot represent W3C
Ege: I can present the implications of registry track
Kaz: we should say what our requirements first, the concrete policy can come later
TF Updates?
Daniel: We have decided to make Cristiano a co-Moderator for the Scripting TF
<kaz> [adjourned]