Meeting minutes
Agenda
<kaz> agenda for today, April-20
<MMC informs about agenda re-structuring>
Minutes
McCool: Any change requests?
… typos have been fixed before the call
… no objections -> minutes approved
Review Ongoing Action Items
https://
McCool: w.r.t. Use case coverage and due diligence
… ask everyone to provide information
… MLagally still on vacation
Quick updates
Cancellations
McCool: Updated cancellations
… ie. scripting call next week
… https://
… e.g., today Profile has been cancelled
… next Monday.. security takes place
IEC CDD Liaison
Kaz: I talked with new IEC SC 3D chair
… were wondering how to proceed liaison
… prefer working first with Japanese CG
WoT Japanese CG updates
Mizushima: April 22, Agenda has been decided
… use-case: smart building in Japan
McCool: New announcements can be added to wiki
Mizushima: Okay, thanks
Publications
McCool: We have TD request for TD
… https://
… should answer a question in the issue in TD call
Ege: Makes sense
McCool: Internationalization has been done
McCool: Discovery still in the work
… behind schedule is also accessibility
McCool: PING is separated?
… what causes security review?
Kaz: should use dedicated labels
McCool: good to know. should take care of that
McCool: Explainer is a lot of work
… Lagally started work ... not much content
… discovery and profile has not been started yet
<kaz> wide review guide
<kaz>Security
<kaz> Write a "Security Considerations" section for your document, taking into account
the Self-Review Questionnaire: Security and Privacy, then request a review via GitHub
<kaz> Show useful links
<kaz> groups
<kaz> None
<kaz> links
<kaz> Self-Review Questionnaire: Security and Privacy, published by the TAG and PING
<kaz> security-request repo
<kaz> Mitigating Browser Fingerprinting in Web Specifications
<kaz> Guidelines for Writing RFC Text on Security Considerations (RFC3552), particularly
Section 5
McCool: Let's review schedule
McCool: https://
… https://
McCool: w.r.t. schedule
… May 6, CR candidate for TD1.1
… 2 weeks away
… should finalize things next week
… CR transition mid May for TD1.1
Toumura: created PR for sorting entries based on date
McCool: CR and PR transition for TD1.1 mid May?
Ege: Yes, not sure.. Toumura-san mentioned this also
McCool: I think we forgot to move PR transition
Ege: think so to
McCool: Okay, let's look at it again in TD call
Testing
McCool: wait for updates before updating TD results
… for discovery we are making progress
Ege: have an internal implementation
… with special logic
Cristiano: WebThings gateway has client implementation
McCool: Hitachi updated discovery results recently
… need to re-run report generator
Daniel: I don't think node-wot will support discovery in near future
McCool: we have a template how to provide manual / automatic test results
… got PR from logilab also
McCool: thoughts about testing procedures?
… let's discuss this in testing call
Review Sections
McCool: created new sections
Charter
McCool: Charter Extensions and Renewal
… Review Liaisons
… Review Collaborations
Review Liaisons
McCool: Matter, I am getting access to specs
… will take a closer lookl
Review Collaborations
McCool: Any new announcements
Ege: working on charter with CA
… very much out-dated
McCool: discuss that in marketing call?
Kaz: BTW, there is new template for CG charter
<Ege> we were going to use https://
<kaz> https://
Kaz: Yes, seem correct link
Daniel: seems *old* repo
<kaz> latest Charter template may have an entry for CG as well
Kaz: good point
TF Reports
Scripting
Daniel: next meeting May 2
Security
McCool: Reviewed architecture
… in Arch document - security split by deliverable
… plan to flatten the structure
… will discuss this on Security call on Monday
… another PR w.r.t. testing plan
Marketing
Ege: we went through issues
… closed *old* issues
McCool: agree with closing *old* issues
… TD and discovery we should use "propose closing"
Ege: for TD call this is on the agenda
Kaz: Agree. Should rather close obsolete issues
… like 1 year ago
… btw, we should talk about policy for requests for presentations
… suggest to discuss this first in main call
McCool: asked to talk Sustainability
… will join next marketing call to discuss the topic
Kaz: Simple suggestion - quickly mention it in main call first
… assign peoples afterwards
McCool: wiki and GH are both public
… e.g., Standict needs W3C feedback
… not sure about policy though
Kaz: Presentation request in general - information in main call first
… details separately
McCool: Okay, let's do that
… main call first... discuss it
… in time critical matters... sending email is okay too
Ege: w.r.t. presentation
… we have now policy.. should we do anything with what we did already
McCool: if confirmed ... not much to do
Ege: Standict is a bit like a press release
Kaz/McCool: Yes, talking to Coralie first makes sense then
McCool: w.r.t. AC meeting and sustainability
Kaz: April 26
… member-only meeting
McCool: Yes, not critical
[testing in 5 minutes]