Meeting minutes
Minutes
approved
Logistics
McCool: let's quickly look at the schedule
… there will be a conflict with the Nordic Chapter CG again on Dec 18
Kaz: we (WoT Chairs and myself) can join the meeting as guests again
McCool: wondering about the future collaboration
Kaz: need to clarify our policy for that
… would suggest we talk with their Chair by email
McCool: yeah
… need to revisit that next year anyway
Publications and Resources
How to generate HTML for ontology
wot-resources Issue 15 - Clean up Discovery Resources
Kaz: for the REC publication tomorrow, we can install a placeholder HTML with one line saying "See this Turtle file..."
McCool: yeah, that's possible
Kaz: we can update the content with nicer description and style like the ones for TD later :)
McCool: ok
… can generate something saying "Please refer to the ttl file..."
… will work on that later
… any other updates on the publication in general?
Kaz: as sent by email as the Publication Request CCing you, everything is ready for publication tomorrow
PR 13
Kaz: btw, the PR 13 was already overridden, so can be closed
wot-resources PR 13 - Update URLs
McCool: yeah
… we can handle this PR this time at the last stage
… but this would be a good approach for the next version
Kaz: right
(closed)
Issue 15
<McCool> wot-resources Issue 15 - Clean up Discovery Resources
(also closed based on today's discussion)
PR 529
<McCool> PR 529 - Update IR
McCool: updating the Implementation Report using my generated tool
… did the same thing for Architecture and TD
… TD had a change with assertion 148 (based on PLH's comment)
(merged)
Planning
Use Cases and Requirements
McCool: we need to start actual work on Use Cases and Requirements
Kaz: let's start to get volunteers for the Use Cases work
McCool: yeah
… another question is we need some more volunteers for Architecture, Profile and Security/Privacy as well
… probably we should ask people for new TF moderators
Kaz: yeah
… let's bring this to the main call
Discovery Use Cases
wot-usecases PR 242 - Associate Discovery Requirement with Use Cases
McCool: let's take a look...
diff - 4.3 Requirements for individual WoT Building Blocks
McCool: would be better to add some additional description, e.g., as an Editor's Note
… (adds an Editor's Note saying "It's under review..." using the ednote style)
<ktoumura> https://
McCool: btw, how can we contact all the Use Case submitters?
Kaz: let's see who were the submitters first
(PR 242 itself has been merged)
Review request
McCool: (creates an Issue to ask people for use case links)
Kaz: we can mention people's GitHub account on an Issue to ask them for review
… but if we want Use Case submitters for review, we should look into the Use Cases document itself and see who were involved in which use case(s)
McCool: yeah
… would try several approaches
[adjourned]