Meeting minutes
New Members
McCool: HiveMQ has just joined W3C and WoT.
Ege: unfortunately, they can't joint the main call today, though.
Minutes
McCool: objection to minutes?
(no)
Quick updates
Ege: CG meeting on live coding on Nov 2
<Ege> https://
Scheduling
McCool: Next Wednesday is holiday
McCool: we have to figure out our press releases
McCool: on Nov 1st we want to have a resolution on our press release
McCool: Sebastian will be available offline
McCool: if we can get the RECs and resources done today, then we have 2 weeks
McCool: on nov 1st the meeting will be still hold, but some will not make it
Nov 23rd thanksgiving holidays
McCool: Thursday 26th Oct the use case call is planned
<kaz> daylightsaving
McCool: this weekend is the daylight saving in the US, watch calander for things moving around for next week
… anything else on schedule kaz?
Kaz: I put the URL of the daylight saving
McCool: we will wait until after daylight saving changes are complete
<kaz> (European summertime ends on Oct 29; US DST ends on Nov 5)
Ege: it seems that Thursday this exact slot seems to work with some other alternatives, but we will wait until the daylight savings
Kaz: As i responded by email, I was confused or I made you confused, but I have a W3C Team-internal call this time on Thursday. Probably it would be better to generate a Doodle to see people's availability for next week and after to avoid the confusion due to DST changes.
McCool: tomorrow we have a use case call, I hope to have a template for use cases that can be applied to other topics
… any other discussions on scheduling?
(none)
Planning
Policies
McCool: we are looking at a special meeting on Nov 8th for a policies meeting
… you have two weeks to look at the PRs and suggest changes
Project Management
McCool: we have been told that there are thoughts on project management, at some point we should discuss this
McCool: I hope to do this before Christmas
Kaz: project management includes many topics, my suggestion is that we start with our own policies.
McCool: yes I agree
… we do need to think about how we want to do this
IG Charter
McCool: I updated the charter to the new template and copied it over and adapted it
Kaz: we have discussion about IG charter in the second slot for today. right?
… maybe we can start with a brainstorming
<McCool> w3c/
Publications
Discovery spec
<kaz> REC Preparation v1
<kaz> REC Preparation v2
McCool: I have been working on Discovery REC preparation
<kaz> s/topic: Scheduling/topic: Meeting Schedule/
McCool: the PRs has links to different things resolved
… bunch of errors comming from external links
… broken URL fixed
… in the history section about a workshop, used to be a hyperlink which went away
… for each of the changes would like to have a resolution
… anybody feels that we should go through them in detail?
(none)
… kaz I am wondering about Pubrules, there is two formats for the date, and this doesn't apply to discovery rather Architecture, we have markup around the data
Kaz: it might be caused by the "Echidna ready" checkbox. Please uncheck it.
<kaz> (error is gone now)
<McCool> proposal: Proceed with REC transition for current version of WoT Discovery in wot-discovery/publication/6-rec/Overview.html (rendered at https://
RESOLUTION: Proceed with REC transition for current version of WoT Discovery in wot-discovery/publication/6-rec/Overview.html (rendered at https://
Architecture spec
<kaz> REC Preparation v1
<kaz> REC Preparation v2
<kaz> REC Preparation v3
McCool: we had again a set of broken links
<kaz> links of checkers' results
McCool: errata11 prefix to keep it consistent
… updated publication data
… used to say yearly workshop, removed the yearly
… some of the references, I updated the dates
… update on the scripting API version
Kaz: As a reminder on the wiki, there are two minor PRs for Architecture
As the reminder of what I have written I put on the main call wiki
<kaz> wot-architecture PR 937 - Replace to 'Custom devices' in Figure 31
<kaz> wot-architecture PR 932 - Typo fix
McCool: I'll add the PRs to the resolutions
McCool: what changed in the figure?
Kaz: the specific product name to be fixed as "custom device"
<kaz> s/As a reminder of what I have written on the wiki//
<McCool> proposal: Proceed with REC transition for current version of WoT Architecture 1.1 in wot-architecture/publication/ver11/5-rec/Overview.html (rendered at https://
McCool: any further discussions?
RESOLUTION: Proceed with REC transition for current version of WoT Architecture 1.1 in wot-architecture/publication/ver11/5-rec/Overview.html (rendered at https://
McCool: we have the resolutions done for the RECs
<McCool> w3c/
<McCool> w3c/
WoT resources
McCool: There are couple of PRs and an update to wot discovery 1.1 and then we are ready for resolution to publish them
… we need to ask the W3C web master
Kaz: did you have a chance to talk with the web master?
Kaz: yes, I did, but have not got a response yet.
Ege: small fix that removed extra quotes, synchronizing whats in the TD, not reflected in the index.html
… regarding the PR in the discovery, i think would be better to have same column names
Kaz: the existing PR themselves are fine, we should have some more discussions based on the merged results
McCool: the Publish WoT discovery v1 resource, it's nothing big just inconsistencies
McCool: there is the draft keyword in the Readme for the wot-resources
Ege: maybe I have removed this in the PR
McCool: I swapped the columns in https://
… for TD V1.0, the difference I noticed is that you use different titles, utf-8 thing
… i can change the titles in the discovery to keep things consistent
Ege: we are not sure what the web master needs, and would be good to get his opinion
McCool: lets wait for the web master and ask him what his preference is
… any objection to remove the word "Draft"
<McCool> proposal: Proceed with publication of the resources in wot-resources for discovery/v1, td/v1, and td/v1.1, subject to approval by the W3C webmaster.
Kaz: if the content is stable enough, maybe we can remove the word Draft itself, I have some concerns when discussing with the web master
<kaz> TD 1.1 resources
<kaz> TD 1.0 resources
Ege: there is a note on the bottom of the README
McCool: in general would say that it is a bad idea and would lead to inconsistent
McCool: the table should have new URLs added, and you shouldn't be revising the old URLs
McCool: the td V1 should have all the URLs for version 1.0
… a seperate issue is that we are sharing the files
Kaz: if we are okay with the new redirection setting, changing the redirection mechanism itself to /ns/wot approach would be nicer.
McCool: I also don't like the dates in the URL
… I think we should leave the draft and make a issue about it
Kaz: lets remove to the draft after getting the opinion from PLH and the webmaster
… the solid group use the /ns approach
McCool: having multiple URLs for multiple resources means that the resource is not unique, keeping both around won't be good
<McCool> w3c/
McCool: ege I made an issue, could you resolve it
… lets aim the resolution for next week
Press Release
McCool: we will be able to finalize the w3c/
McCool: testomonials have been merged
… editorial changes merged
<kaz> i|testi|wot PR 1148 - WiP: Mention examples of commercial adoption|
TPAC Minutes
McCool: TPAC minutes, we have to do this next week, in the meantime take a look
Meetup
McCool: WoT-JP CG is planning for security in December
TF Reports
McCool: any of the TF have any quick updates?
Ege: in marketing there was misalignment, and we aligned them in the Wiki, Regarding OPC-UA they are in the review stage
McCool: they are consumers of WoT TDs?
Ege: yes
<Ege> https://
cris: one thing coming from marketing, we found the feature of Tags in Github, for the coming weeks we will come up with a proposal
McCool: will it be a new policy?
cris: no, it will be used for tagging
McCool: Regarding Twitter, my understanding is that API is that it allows to get the latest post not the history
Ege: there are 3 things we are looking at Twitter, Mastadone,...
… w3c is considering to leave Twitter
Ege: Mastodon cannot be a replacement, the reach is less
… for Linkedin, W3C doesn't want a new account for groups
McCool: it sounds like there are some W3C changes that we should follow
Ege: If you want we can discuss them in the next marketting call
McCool: 10 minutes break, before we talk about the IG Charter
<kaz> [10-min break]
IG Charter
<kaz> Current WoT IG Charter
McCool: see PR in WoT, w3c/
… should move it to wot-charter-drafts
<kaz> wot-ig-2023-draft.html
McCool: Using new template
… content-wise it hasn't changed
… mission statement should be synced with WG
McCool: Note, links don't work until merged
… 2 years charter 1 Jan 2024 til 31 Dec 2025
… kept Kaz as the only team contact
… Motivation and Background section seems okay
… maybe update background information to be consistent with WG
… should also refer to new 1.1 documents
… Section 2 Scope
<kaz> (McCool generates Issues on wot-charter-drafts repo expecting we'll move the draft IG Charter to that repo later)
McCool: Not sure if we want to mention WG
… some parts relate to what CG does
… use-case deliverable is not listed
… we need some re-organization
Ege: I think we should really be specific, mentioning uses-cases
… is there a risk if we just have 2 items left
McCool: I think use-cases on its own would be useful
… we need to explain CG relationship
Ege: What if use-cases come from CG, would that be a a problem?
… CG contributing use-case to IG or WG ?
Cristiano: I don't think there is much difference ...
Kaz: We need to clarify current roles of IG, CG, WG
… if there are important aspects left for IG we need new charter
McCool: testing seems part of IG
Ege: implementation report should be done by the WG task forces
McCool: differentiate testing from PlugFest
… PlugFest: interop testing (WG) and experimentation (CG)
… does not belong to IG, I think
Ege: Marketing?
McCool: Yes, website is "owned" by IG
… not sure about social media
McCool: IG could be a place for *new* ideas
Ege: CG reports can propose new ideas
… I think there is a process for transferring the ownership
Kaz: let's list existing tasks first
McCool: In general I think we need an IG
… but we can narrow the scope
… let's follow up in Issue 122
… 2.1 PlugFest and Testing
… we need to re-organize this testing discussion
Kaz: supplementary work like implementation guidelines should be considered in charter
McCool: What about security and privacy guidelines document?
… not sure if this is an IG or WG thing
McCool: 2.2 Use Cases and Requirements
… needs updates
… last para needs to cleaned up also
… 2.3 Marketing and Outreach
… keep it for IG
… daily business happening in CG
… CG does outreach
… IG mediates between WG and CG
Kaz: basic diagram should be updated to reflect the changes
McCool: Correct
… 3. Deliverables
… some vagueness should be removed like "may be created"
Ege: FYI: Security& Privacy is WG informative deliverable
McCool: 4. Coordination
… we have old list
… is there any liaison we want to mention
… liaison in general is WG
<Ege> https://
<Ege> https://
Ege: Use-cases document. Link to latest published version is wrong
McCool: I think the main purpose of IG is use-cases
… 5. Participation, 6, and 7. should be consistent with WG
… we might need to update those sections
Ege: policy discussion for WG or IG ?
McCool: All WG discussions
… rest is "boilerplate"
… need to update charter history in section 10
McCool: Summary
… 2 things in scope
… use-cases document
… website content
… rest can be moved to CG or WG
Kaz: Good starting point
McCool: Should look at IG charter again in about 2 weeks
… will try to clean up the recorded issues
adjourned