Meeting minutes
Agenda
McCool: (goes through the agenda for today)
McCool: anything else?
(none)
Minutes
McCool: as already mentioned, I don't have much time this year...
… need somebody to handle Discovery as well
… discussion on HTML for ontology
… there is a new PR also
… (goes though the minutes)
… any objections for the minutes?
(none)
approved
Archive old agendas
McCool: will do later
HTML for ontology
PR 537
PR 537 - Expand rdfs:comments in Discovery ontology
McCool: added actual content for the HTML?
Jan: yes
McCool: let's review it
… (goes through the changes one by one)
McCool: would like to merge this PR and try another iteration
… wondering about the style...
Jan: that's the result of the tool based on the TTL file
McCool: (looks into the TTL instead)
McCool: think we need a couple of iterations
… and would be better to have a rendered version
HTML preview of the PR changes
Kaz: we can use HTML Preview for that purpose as above
McCool: good to know
Kaz: I'm OK with merging this PR itself as the first iteration
(merged)
<McCool> related Issue 533 - Update HTML for Discovery ontology
<McCool> tick off third box: comments filled in
PR 536
PR 536 - Render changelog in discovery ontology from RDF
McCool: some branch conflicts
… do you want to fix them, Jan?
Jan: will do
HTML preview for discovery-ontology.html
(Jan has updated it)
McCool: still no introduction
Jan: updates on metadata
… this is a mocked version now
… still checking the content locally
Kaz: we still need further discussion about version management policy within the WG, but maybe we could call the initial placeholder "0.0.0" instead of "1.0.0", couldn't we?
McCool: or we can use tentative versions for a while
… and then change it to official versions after clarifying the versioning policy
Jan: (describe rederOntology.js)
McCool: should we change the version to "0.0.0" as suggested?
Kaz: or if this is a Alpha/Beta kind of test version, we could add "a" or "b" to the version number instead
McCool: like "1.0.0-a2"
… meaning Alpha 2 version for "1.0.0"
… technically we've already published a "1.0.0" version for DID repository application
… don't want to change the version number which has been already published
Jan: in that case, should the main branch be "1.0.0"?
McCool: hmm
… let's see the ones which are already published again...
discovery/v1/ontology/discovery-otology.ttl
McCool: maybe we could create a "7-resources" under wot-discovery/publication to see how to handle the proposed changes
Jan: makes sense
Kaz: using the "publication" area under wot-discovery would be confusing because it's not related to spec publication itself
… so would be better to have a "draft" area under the wot-resources repository instead
McCool: yeah
… something like wot-resources/discovery/Alpha
… or draft
… anyway, still need to fix this PR itself
Jan: yeah
McCool: then discuss this next week
Jan: ok
Kaz: another comment on the PR
… regarding the tool generating the HTML from TTL, we should collaborate with the TD TF
McCool: right
DID registry
<McCool> DID PR 486 - Add WotThing and WotDirectory service types
McCool: will update the PR and then ping the DID guys
… btw, wondering about domain and range for ontology
Use Cases and Requirements
<McCool> Issue 534 - Link Work Items to Requirements in UC&R document
Kaz: each smaller PR from Discovery TF has been merged
… but we still need to clarify the whole process for Use Cases
… then need to talk about how to deal with further feedback from TFs including Discovery
Mizushima: agree
… as Kaz mentioned, we need to clarify the whole process for Use Cases first
… then need to clarify how to deal with feedback from TFs
McCool: exactly
[adjourned]