Meeting minutes
Minutes
McCool: we will review the minutes as usual
<kaz> (unfortunately, we didn't make the proposed policy for minutes a resolution, though)
<kaz> July-26
McCool: any changes you see?
McCool: any objections?
<kaz> (typo fixed)
McCool: minutes approved
Policies
<kaz> Proposed Policies
McCool: current PRs go into proposals directory
McCool: we would like to make them official
… would be good to do that before tpac
Kaz: OK with merging the initial proposals as a starting point for further discussion, but we should add draft on the title
… also it would be good to consolidate them into a single document to make the proposals inline with each other.
McCool: I would prefer to keep them separate
… but I am ok to add draft to titles
McCool: (adds "DRAFT" to the title of each proposed policy document)
… btw, what was the "IE included", which was discussed last week, about?
… related to the async decision policy?
Ege: yes I think so
Ege: We dont need to add draft if it is a proposal right?
McCool: sort of but we can do it later
Async Decision Policy
<kaz> wot PR 1108 - Asynchronous decision policy proposal
McCool: we should mention IEs
Sebastian: it is already done
Ege: I have already incorporated the feedback
McCool: we can table this since people had commented and reviews happened
McCool: any objections?
Dainel: style is different
McCool: I can change that quickly
McCool: we can merge and make them official in 3 weeks
Kaz: I am ok to merge this PR 1108 itself as a starting point and discuss later on before making them official
Kaz: also, IEs will have the same access rights as members so there should be a policy on how to choose IEs as well
… in addition, the execution of policies are very important. We should discuss these
Call for Resolutions
McCool: I will send an email about a call for resolution
… so that we can make these policies official
Meeting Schedule
McCool: there is holiday season approaching
McCool: which two weeks should we cancel?
… ege and sebastian has unavailabilities
Ege: we should understand when to reach resolutions on the REC track documents
Kaz: no group resolution needed for REC publication. The work is handled by the W3C Staff and also it is a W3C decision to proceed with REC publication
Sebastian: for td, we should check that the additional resources like ontologies are correct
… I am ok to cancel main call for 3 weeks, we should leave the TF meetings should be left to TF moderators
Kaz: Note that we were originally talking about summer vacation but now we're talking about publication schedule. If we really want to talk about the publication schedule, we should once wrap up the vacation discussion and then start to talk about publication schedule.
McCool: I propose to cancel the meetings weeks of august 21st and august 27th
New Charter
Kaz: I am talking with MarComm about the procedure
McCool: in this case, we will have a small gap between end of september and around 4th of October
Kaz: We've already got extension by the end of September. Also the actual AC Review should be able to get started by the end of this week or early next week at the latest.
Sebastian: why is the process getting delayed? I need to explain to my management
Kaz: due to process change, there are unclear parts, but as already mentioned, AC Review form and review request have been already generated, and actual review to start shortly.
McCool: we can talk offline
TPAC Planning
McCool: our slots are confirmed and written in Wiki
Ege: there are breaks announced by W3C
Ege: I think it would be better to start right after the break to allow others joining to catch up
McCool: we can do easy things in shorter sessions
Sebastian: TAG is also requesting a slot
McCool: we should have a slot about use cases not at the end
Ege: we should have use case and requirements process, not new use cases
McCool: we can arrange it
Ege: We will talk in the TD call to finalize the TD topics
… with Koster we spoke and decided to prioritize topics that benefit from a wider input\
Kaz: We should have a quick wrap-up for the final slot. On the other hand, the "New Use Cases" should be rather called "Industry Use Cases" or "Commercial Use Cases" to see further deployment of the WoT standards within the real business.
Ege: we should clarify what we mean by industry use cases but I think we agree on it, just a wording issue
Publications
McCool: we have 18 supporters for discovery now
Ege: Luca will have a look
Kaz: If you want, I can send a reminder to related AC Reps.
McCool: Yes, please.
McCool: anything on the notes?
Kaz: not yet. will work on them right after finalizing the Charter procedure.
Press Release
McCool: we have sent the review request to marcomm
<McCool> https://
Kaz: we should do review of press release narrative as the whole WoT WG.
McCool: we will do this over github
Kaz: We should have summary discussion during the main call as well.
McCool: can do that too.
Bug fix for TD
PR 1843
wot-thing-description PR 1843 - Fix well known operation types only
Ege: Luca found this error on the description
"operations types MUST be restricted"
Ege: there are no changes to the intention, we were testing like that already
McCool: you are increasing the level of assertion
McCool: we should have director approval to do this change
<McCool> proposal: WoT WG will ask the W3C Director for approval to make the changes labelled "Changes to PR HTML" to correct editorial issues (no implementation changes needed) in the WoT TD 1.1 Proposed Recommendation before going to REC.
RESOLUTION: WoT WG will ask the W3C Director for approval to make the changes labelled "Changes to PR HTML" to correct editorial issues (no implementation changes needed) in the WoT TD 1.1 Proposed Recommendation before going to REC.
Kaz: So we need to pick up PRs which have impact to TD spec's index.html from the PRs with "by REC publication" on wot-thing-description repository. Right?
PRs with "by REC publication" label
McCool: Right.
[adjourned]