W3C

– DRAFT –
WoT Discovery

15 January 2024

Attendees

Present
Jan_Romann, Kaz_Ashimura, Kunihiko_Toumura, Michael_McCool, Tomoaki_Mizushima
Regrets
-
Chair
McCool
Scribe
JKRhb, kaz

Meeting minutes

Minutes Review

<kaz> Dec-11

McCool: (Goes over the minutes of last time)
… did not see anything critical
… (summarizes the last meeting)
… any objections to publishing?
… hearing no objections, minutes are approved

Logistics

McCool: I'd like to archive all the old agendas in the Wiki, as they are taking up space
… hearing no objections, will edit the Wiki and link them from the main page

Meeting Schedule

McCool: I don't have the time to be the TF lead of four taskforces
… want to step down as TF lead of discovery and security
… can ask the group if someone wants to take over the TF lead of one of them
… if no one volunteers, I can continue as TF lead of either discovery or security
… I also want to focus more on use cases in the future
… I kind of want to pause our meetings until the end of January, to make space for the work on use cases

Kaz: We can pause the work on security and discovery for a while based on the current state of the TFs
… but we should think about who should take the lead of these two TFs

McCool: Yeah, we will need to go through process of electing new leads
… need to define the policy here
… should not pause the meetings undefinitely but define a concrete date when we are going to resume
… we could, for example, resume on February 19
… that would give us a month to work on use cases
… does that make sense?

Kaz: Yeah

McCool: Let me add that to the agenda to remind myself
… (edits the agenda in the wiki)

Resources

HTML for ontology

McCool: There is a PR

<McCool> w3c/wot-discovery#535

McCool: this is related to issue 533

<McCool> w3c/wot-discovery#533

McCool: there are two things
… setting up the scripts and rendering the ontology and then pushing it to wot-resources

Jan: (describes the PR 535)
… actual logic is written in "renderOntology.js"
… something is missing at the moment
… asking Farshid, Andrea and Mahda for review but have not got response yet

McCool: where the DID description come from?

Jan: you can look into the diff

McCool: so you're modifying the TTL file (discovery-ontology.ttl)
… do we update it on site? or add any versions?
… these are almost annotations

Jan: yes

McCool: defined the prefix

Jan: yes

McCool: default prefix to be described as ":"

Jan: right

McCool: modifying the content in the root directory
… not "publication"
… we need to update the resources until the they're completely fixed
… shouldn't break any things
… doesn't change any existing names
… good opportunity for us all as the WG to think about how to manage the changes
… guess we could do this right now
… because this is updating the resources in-place
… but one question is how to identify the versions

Jan: should go to the TTL file?

McCool: we have the status of the document
… where did the status information come from?

Jan: should the information go to the status section?
… or some dedicated appendix section?
… maybe link to the change log description at appendix

McCool: suggestion is
… Version 1.0.1
… See [[ChangeLog]]
… within the Status section
… then description at the Change Log section within appendix

Kaz: TD TF is also discussing how to manage the changes using the version numbers
… so should have joint discussion about version management with the TD TF too
… McCool, do you think you can join the TD call at some point, Wed or Thu?

McCool: have conflicts this week
… maybe next week
… meanwhile let's not merge this PR itself

McCool: how to proceed?
… is there an Issue on the wot-thing-description repo already?

Kaz: you can create an issue on wot-discovery side mentioning Ege's name :)

McCool: seems there is an issue on wot repo about spec versions

wot Issue 1082 - Versioning Discussion

McCool: (creates another issue around ontology versions)

<kaz> rrsagetn, draft minutes

McCool: I think we need a common way to manage resources
… this is just a description, not a natural policy
… but we can create one and then discuss it, linking back to this issue
… does that make sense?

Kaz: Yeah, is a good starting point

McCool: The discovery thing can serve as a good example
… can you continue working on the PR, Jan?
… we can merge now and then fix the remaining issues later

Jan: Yeah, applied some minor fixes

McCool: We can merge now, then apply additional fixes to .ttl file
… any objections to merging?
… no objections, merging, then we can open an issue for the remaining issues

PR is merged

<kaz> Issue 533 - Update HTML for Discovery ontology

McCool: (adjusts issue 533, adding another checkbox for updating the remaining TODO comments)
… I think what that means is that we have the first one checked
… (ticks the checkbox)
… third one is partially done
… (adds another ticked checkbox regarding the generation of an interim HTML output with TODOs)
… after this interim step, we can make another PR in the discovery repo and then make a another PR in the wot-resources repository

DID Registry

<kaz> did-spec-registries PR 486 - Add WotThing and WotDirectory service types

McCool: Haven't looked into this PR in a while
… so I asked for review
… has been reviewed, they did some language tweaks
… (reads through one suggestion)
… this suggestion regarding "either" does not make sense to me
… I will commit these changes and then make some minor tweaks (e.g., adding a comma) to get us past the review
… (looks at the resulting PR diff, adds another suggestion regarding the comma)
… (commits it)
… so let's resolve the conversation
… (adds a comment saying the suggested changes have been accepted with a minor tweak for clarity)
… (adds another comment asking for a final review)
… let's leave it for now and I will at it again in a while

Use Case Call

McCool: Anything else? When is the use case call again

Kaz: On Wednesday before the main call. I'll allocate a Zoom, and then distribute it to the groups.

McCool: Let's continue the discussion there

[adjourned]

Minutes manually created (not a transcript), formatted by scribe.perl version 221 (Fri Jul 21 14:01:30 2023 UTC).