Meeting minutes
no too many people here - have a short meeting only, but need to wait for kaz to come back
minutes
<kaz> Dec-4
McCool: minutes were approved, after typo fix
Logistics
McCool: Discovery meeting next week on Dec 18 is cancelled
… also cancellations due to holidays
… the next call is Jan 15
Resources
McCool: right now, we have a placeholder HTML
… it's good for now
… but we need to get registered with the DID registry
… need to coordinate with the TD repo as well
… have to get volunteers for that purpose next year
… myself will concentrate on the DID registry issue
… will make sure it will happen
… (adds a link for did-spec-registries/pull/486)
link for did-spec-registries PR 486
McCool: seems there is some conflict now...
… once the fix is done, can get published
Planning
Use Cases and Requirements
McCool: getting good shape but need go be reviewed
… probably need some re-organization
… but have clarified topics on Discovery
… need to send an email to the whole group
… to be sent to the IG?
Kaz: the Use Cases and Requirements document itself is done by the IG
… on the other hand, the use case topics are related to Discovery done by WG
… so you can send the review request to both the IG and the WG
McCool: what about the CG?
Kaz: technically, if CG Members would like to give reviews for an IG document, they should join the public-wot-ig mailing list
McCool: that's true
… would talk with Ege about that
Kaz: do you expect to get reviews by those who provided use cases but possibly still non-Members as well?
McCool: right
Kaz: btw, you might want to send it to public-wot-ig and public-wot-wg instead of the Member lists :)
McCool: ok
(review request sent out)
… ideally all the contributors should subscribe this public-wot-ig list
Resources - revisited
(discussion on how to generate HTML descriptions from the TTL ontologies)
McCool: at the moment, good placeholder
… but would be great if we could get your help, Jan
Jan: which ontology?
McCool: only one ontology for WoT Discovery
Kaz: in that case, I'd suggest Michael create an Issue describing which TTL file to be converted to what kind of HTML file
… then Jan could work on that to help you
McCool: ok
… what we do is
… 1. update the HTML content
… 2. replace the HTML in wot-resources
McCool: or maybe 3-step approach
Kaz: in that case, you should mention "what to be done at which repository how"
McCool: ok
… 1. set up the script to generate the HTML from TTL on wot-discovery
… 2. update the HTML to reflect the actual content of the TTL file on wot-discovery
… 3. replace the HTML on wot-resources
Status
McCool: would create some more issues on wot-use-cases
Kaz: I can understand the current situation and the difficulty of how to manage the use case calls at the moment
… however, technically, WoT Use Cases discussion is done by the WoT IG
… and some of the IG-only participants might want to join the discussion too
… so we should think about how to hold the use cases discussion in a broader manner
McCool: yeah
… let me create an issue
wot-usecases Issue 253 - Update Status of each Discovery Requirement
<McCool> wot-discovery Issue 534 - Link Work Items to Requirements in UC&R document
Resources - revisited
Kaz: btw, wot-discovery issue 533, which was created during this call, and an older one Issue 524 are identical. right?
Issue 533 - Update HTML for Discovery ontology
Issue 524 - Generate HTML file for ontology/discovery-core.ttl
<McCool> Issue 509 - Create and Publish an Ontology File for DID Vocabulary
McCool: Issue 509 also
… (closes 509 and 524)
Issue 515 - Publish Context and Ontology
McCool: 515 can be also closed
<McCool> Issue 518 - Publish JSON Schema for TDD at stable URL
McCool: 518 also can be closed
Next call
McCool: will be Jan 15
[adjourned]