Meeting minutes
Main Call Topics
Guests, New Members, IEs
Koster: we have an invited expert request
Kaz: I will contact this person and ask about his interest in the CG, but if contribution for WG is required we need to discuss this in the main call
… think we also should clarify this as a policy explicitly.
Koster: we need a policy of their contributions
Ege: somebody has also approached me for an IE request
Ege: I think there should be a policy document about it
<Ege> dtex/
Kaz: there is some basic plicy about IE in general, the WoT working group have been clarifying their additional policy
Kaz: we require the invited expert to make a presentation
McCool: we need to create an issue for this
Ege: will do this
Minutes
<kaz> Jan-17
Koster: minutes published with no objection
Notices
Koster: are there any notices?
Lagally: : I was asked to write a blog article about the publication REC document, if somebody would be interested to review the draft feel free to let me know
Meeting Schedule Changes
Koster: we have a policy updates today after the main call
… next week a meeting to discuss IG charter
Cancellation
Koster: we have some in February but nothing new, the calender has been updated
Rescheduling
Koster: security and discovery are currently susspended but will take place again soon
Kaz: we should add publication schedule as in item to the schedule
Lagally: on the publication of the documents can we also add the profile document
… we should work on a plan to get this work completed, in Nov there was a conversation about finding a TF for this, there is interest to complete this document
… Luca indicated interest to take TF leadership
… I would be able to attend the call and help Luca with the transition
Kaz: we still need to talk about the working group planning and clarify which specifications to be worked on
<mlagally> proposal: Resume the profile task force work under new TF chair Luca Barbato on Feb 19th.
Publications
Koster: anything on publications?
(none)
Resources
Koster: For TD there are still some outstanding items for resources
Kaz: we have joint discussion in the call tomorrow, we can hear from the discussions later next week
Meetups
WoT CG
Koster: no new update
Cristiano: Ege and I will have a talk on Global summit and we will have a talk on node-wot
Liaisons
(no specific updated)
TF Reports
Scripting TF
Cristiano: we are active and we are working on issues and figure out what we will do, we are finding more user stories and assessing bi-weekly meetings
Daniel: we also look into improving our support for discovery, but ongoing work
Security
Kaz: this TF is currently susspended
… also discovery
Marketing
(none)
Use Cases
Tomoaki: this week i updated the document based on last discussions, and we discussed use case definitions, requirement analysis and gap analysos.
Koster: any other discussion on the use cases?
(none)
Plugfest/Testing
Kaz: maybe in the wiki we can add suspend in the TF that are currently not active
… architecture is also not active
TD
Koster: we talked about the use cases, we split the meeting into two sessions
<kaz> [10-min break]
WG Planning
Sebastian: opening the session on WG planning
… Topics are policies, project management, Berlin event, TF sustaining
… any other topics?
Sebastian: topic: policies
… review of github issues
<sebastian> https://
Sebastian: summarizes process for policies
… starting with a proposal for a policy and a github issue to motivate and track
issue #1171
<kaz> Issue 1171 - [Policy Proposal] Invite Expert Selection Procedure
Kaz: earlier today we discussed the IE policy and this issue captures the points from that discussion
Kaz: will write up more as a PR
Issue #1168 - policy on assertion IDs
<kaz> Issue 1168 - WoT-wide general policy on assertion ids
Sebastian: this makes sense to have a well known encoding of IDs
Sebastian: we could align with an RDF namespace
… are there any comments on this?
Kaz: we can start with the current practices
… from Architecture, Discovery, and TD
Sebastian: is there a document?
Kaz: no, we need to clarify what we have been doing, McCool and Ege could help
McCool: what we have been doing is random
McCool: we should get the IDs cleaned up before we start another round
Sebastian: discovered an issue with the links and name conflicts
McCool: also issue with terms not matching descriptions in ontologies
Kaz: so we should start with the current scheme and improve from there
Daniel: There is a respec issue we could fix by patching the HTML to resolve the link issue
Ege: IDs aren't random per se, they are assigned by the spec editors
… alignment with RDF namespaces can be done but there are other issues
Sebastian: we didn't mean random IDs but rather not well managed
Sebastian: can we get a proposal?
Ege: I can make some suggestions
Kaz: starting with the current TD approach and refined from there
Issue # 1166 - Versioning Resources
<kaz> Issue 1166 - [Policy Proposal] Versioning Resources
McCool: we need to figure out a version scheme for recources
… we plan to discuss it in the TD meeting tomorrow (Thursday)
Daniel: We have an issue that it's not easy to point to a specific version of all resources and artifacts
… and use semantic versioning
<kaz> acm m
Mahda: all resources and documents need to be versioned
Issue #1117 - Roles and Responsibilities
<kaz> Issue 1117 - [Policy Proposal] Roles and responsibilities within the WG/IG
Sebastian: we should put roles and responsibilities in one place
… started to create a document collecting these
… any comments or questions?
Kaz: will we consolidate the policies into a single document?
Sebastian: some of these roles are already defines by W3C
Kaz: it will be good to have this all consolidated
Sebastian: any other policy items?
Project Management
Sebastian: there is a proposal from Ege
… categories are proposed to sort issues
… the proposal is to assign issues and track progress
… it's a standard process for software development
… personally like this approach, and we are already doing some of this process
… this would make it more formal
Ege: proposal is to align with the use case pipeline
Kaz: there should be 2 layers of process management, there is a higher level of use case management to lower level of concrete tasks
<kaz> Mizushima's high-level process proposal
Kaz: the higher level is from the use case discussion and documented in the process.md document
Sebastian: the high level includes gap analysis, etc.
… this goes hand in hand with the development process
Sebastian: what is the next step? Is there a new policy?
Kaz: The use case TF and TD TF should continue to work on both levels until February and work toward convergence
… not necessarily a new policy
<MIzushima_> +1
Sebastian: The project management proposals are already merged
Issue # 1170
<kaz> Issue 1170 - Liaison and Collaboration for WoT 2.0 Charter
Kaz: this is a reminder that we need to continue to work on how to describe liaisons and collaboration
… Kaz can generate a basic template if it's OK with the chairs
Sebastian: yes, please
ACTION: kaz to generate an initial template for liaison/collab
Kaz: assign to me (Kaz)
Issue # 1167
Ege: there is overlap between the Use Case document and the Architecture document
… Similar high level content
… we need to align this in some way
… we need to make it clear to outside readers
Sebastian: there are some other questions about the Architecture document we also need to clarify
… Also agree we need to consolidate the content
Kaz: agree, and what is more important is the Use Case TF reviews all of the use cases, including the ones in the Architecture document, so we don't miss any important use cases
Ege: we need to agree on the purpose of the Architecture and Use Case documents and eliminate the overlap
Tomoaki: the use cases in the Architecture document are different and we need to include both
Sebastian: The architecture document is a snapshot of use cases
Kaz: we should discuss this in the Architecture meeting and see if there is anything needed to contribute to use cases
… we need a collaborative discussion including both TFs
Ege: Architecture content can be included in the UCR document as a generic introduction
<McCool_> time check - 2m left
Ege: The architecture document can focus on architecture
McCool: we should decide priorities of task forces and spin up the high priority ones
Sebastian: suggest that we continue this discussion in the main call next week
Kaz: next week is IG charter and can resume this discussion in 2 weeks
Sebastian: adjourn the main call
<kaz> [adjourned]
Ege: start TD at 5 past