W3C

– DRAFT –
WoT Discovery

04 March 2024

Attendees

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

Meeting minutes

Minutes

Feb-26

McCool: (goes through the minutes)

approved

Meeting schedule

McCool: any updates?

(none)

McCool: I was thinking to take vacation some time in May
… not sure about the exact date yet, though

Issues and PRs

PR 544

PR 544 - fix(ontology): extract current version from .ttl file

McCool: this is a kind of bug fix

Jan: we need to visit the TTL file
… to get the version information

McCool: ok
… we don't increase the version with only changing the rendering script

(merged)

DID Registry

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

McCool: (visits the PR)
… still not merged yet

Issue 533

Issue 533 - Update HTML for Discovery ontology

McCool: the first three check points have been already done
… maybe we could have some more check points
… for missing steps
… (adds several more check points)

[updated check points]

- [ ] Align versioning with the group consensus policy, and consistent with the
      TD specification
- [ ] Fix domain/range issue
- [ ] Update the HTML file to reflect the actual content of the discovery ontology
      - PR into wot-discovery repo
- [ ] Replace the HTML resources in wot-resources (the publication is by redirection,
      so this will update the published resource at the official URL) - PR into
      wot-resources repo

Kaz: putting the updated draft resources for Discovery under the "publication" area would be confusing
… if all the resources correspond with some specific publication draft, maybe we can put it under the "publication" area every time
… but if it's not the case, it would be better to put the draft WoT Discovery resources under "draft-resources" or somewhere like that separately from the "publication" area

McCool: either is fine
… let's think about it

Issue 541

Issue 541 - Add domain and range to ontology

Jan: would talk with Mahda

Issue 467

Issue 467 - Resolve Remaining DID issues

McCool: do we still have anything to do this?

(none)

(closed)

Issue 402

Issue 402 - Register DID service names

McCool: still pending
… depending on the did-spec-registries 486 issue

Issues with "defer to Discovery 2.0" label

McCool: not really relevant any more to have the label of "defer to Discovery 2.0" now
… should we simply remove the label?
… then reorganize things

Jan: agree

Kaz: ok

McCool: (removed the "defer to Discovery 2.0" label)

Issue 445

Issue 445 - Implementation Report Fixes

McCool: (goes through the issue)
… (shows the WoT Discovery implementation report also)

WoT Discovery Implementation Report

McCool: (make the bullet points to check points within the Issue 445)
… (also makes "Assertion tdd-notification-data-diff-unsupported..." done)
… since the assertion is removed now
… would ask Farshid for clariication for "tdd-things-list-pagination-order-utf-8..."
… (then visits the wot-testing repo)

wot-testing/data/input_2022/Discovery/VAIMEE/manual.csv

wot-testing/data/input_2022/Discovery/siemens-logilab/manual.csv

McCool: need to see the results again

wot-testing/data/input_2022/Discovery/Results/

McCool: seems there are related issues

Issue 413 - Improve wording of tdd-absolute-time assertion

Kaz: you can check the detail later offline :)

McCool: yeah, agree

Requirements issues

McCool: there are many requirements issues

Issue 328

Issue 328 - CR WD review June 2022

McCool: can close this
… but this issue is actually related to the use cases discussion
… should rename it
… (rename it to "Discovery Use Case for finding TDs in a given security realm")

Issue 510

Issue 510 - Update Requirements

McCool: how about changing the title to "Update Discovery Requirements"?

(renamed)

Kaz: should add a label on "requirements"?

McCool: rather "use case"?

Kaz: that's also fine

McCool: and maybe we should move this over to the wot-usecases repo

(moved to wot-usecases repo)

Issue 534

Issue 534 - Link Work Items to Requirements in UC&R document

McCool: how to handle this?

Kaz: we should think about inter-TF issues as the whole WG
… but putting some kind of label "collaboration", etc., could be a starting point

McCool: ok
… why don't to call it "organizational"?

Kaz: that's fine

Issue 209

Issue 209 - Thing Description Framing

McCool: has "move to TD" label
… also very old (in 2021)
… it's also an issue on the output as JSON (not TD)
… anyway, not really a Discovery issue
… let me transfer it to wot-thing-description repo
… (also changes the title)

wot-thing-description Issue 1981 - Thing Description Framing for RDF/JSON-LD round-tripping

[adjourned]

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