Meeting minutes
previous minutes
<kaz> Dec-22
McCool: about use cases document we'll review today
Lagally: it should be ready to be published
McCool: no issues with the minutes, minor format problems
… any other issues?
… ok no objections, minutes approved
Quick updates
Editors call update
McCool: editor meeting we'll be rescheduled to
… there was discussion about Architecture document
… in particular about labelling PR
Lagally: yes we tried to identify which changes were critical
McCool: we need also a way to summarize the changes, PR labelling will help in that direction.
Architecture call new slot
Lagally: wot arch meeting will be split in two: Profile and Arch
… then we can fit Profile after main call
… about arch we discussed to use the current second hour of arch slot
… for the editor call we'll move it three hours later
<McCool> proposal: profiles at 7am ET on Wed (one hour before main call) (chairs call will be moved an hour earlier), architecture will use only the second hour of the current slot, so will be at 6am ET on Thursday.
RESOLUTION: profiles at 7am ET on Wed (one hour before main call) (chairs call will be moved an hour earlier), architecture will use only the second hour of the current slot, so will be at 6am ET on Thursday.
ACTION: kaz to generate another doodle for the Editors call including 6ET
WoT Japanes CG updates
Mizushima: The second kick-off meeting will be held on Jan 28th, and initial discussion on potential outreach events, for example for publishing industory has started
McCool: we should record this to the Events page
Smart cities updates
Kaz: not many updates, but I'll work with the Smart Cities Steering Committee to get smart city stakeholders from Japan, China and Korea as the starting point.
WoT Articles
<kaz> Introduction to the Web of Things
McCool: Sebastian found a new article about wot, we should keep track of it
Lagally: we also wrote a paper CCNC Workshop
… I gave a presentation yesterday
McCool: is there any link to the article
Lagally: not yet
<McCool> https://
IG recharting
McCool: we need more support and the AC review is ongoing
WG Charter Extesion
Kaz: will ping PLH about the process. probably we need to ask W3M for 3mo extension as well to finalize the procedure.
Lagally: probably we should also review the plan for the extension
… updating with the lastest discussion
McCool: we are already in the wide review process
… not sure if we can
Kaz: we should think about extension and publication schedule separatly
McCool: probably is better to move some topics to the next charter
Lagally: we are requesting one year extension but the plan covers only 6 months
McCool: I agree I think the current plan can be improved
Publications
Wide reviews
McCool: I looked in the process of wide review
TD
McCool: in December Ben provided a deep review of the TD doc
… today we'll discuss it in the TD
Sebastian: we did not have a resolution
Use Cases
Kaz: call for resolution about Use Cases document
<McCool> proposal: publish the current editor's draft of the Use Cases and Requirements document as an updated IG Note, but also including small editorial changes resolving issues marked as "editorial" in the repo
RESOLUTION: publish the current editor's draft of the Use Cases and Requirements document as an updated IG Note, but also including small editorial changes resolving issues marked as "editorial" in the repo
McCool: when will the Call for Resolution for TD will happen?
Sebastian: today
… we are going to discuss also backward compatibility
Lagally: many thanks to all contributors, co-editors, W3C team contact for the good collaboration on the UC WG note
TD (revisitd)
McCool: TD will discuss remaining issues and make the TF resolution today, then WG resolution during the main call next Wednesday. Is that OK?
sk: fine
Wide review process
McCool: we have to fill a questionaire and reques a review via Github about accessibility
… I'll do it
… we need to do this for each deliverable
<kaz> Wide review guide
McCool: one note we have to identifying substantive changes
… each document needs to have a privacy and security section updated
… more discussion is needed for the core documents
… every task force should start this process asap
Sebastian: we should start the wide review ASAP, it would take time to get the real review
… in the meantime we can continue working on the documents
McCool: we can figure out estimates about review
… our homework is to define a list of changes and do the questionaire
Ege: regarding the schedule when is the feature freeze / deadlines?
Lagally: can you define feature?
McCool: assertions are good examples of features. They should be frozen
… before review
… or only adding new assertions if they are really essential
Kaz: editors please look at the extension plan document and update the schedule again
Lagally: arch spec is not ready to be frozen
<kaz> extension plan
Kaz: as I mentioned already, we should think about the WG Charter extension procedure and the publication schedule separately, and discuss the updated publication schedule during the "Publications" topic later. WG Charter extension is already submitted to W3M and we're asking for 12mo extension. So we should think about our updated publication schedule within that period based on the current status.
McCool: testing need feature freeze but we could test only discovery and TD
… profile can have a dedicated a test fest
Lagally: is the TD feature frozen?
McCool: there are few PR that changes assertions
Sebastian: we need more discussion about PR first
Testing
McCool: no testing call
Liaisons
McCool: ITU-T webinar, I'll send a calendar invite
… IEEE is hosting an event too
… something is happing OPC UA
Sebastian: I'm finalizing the discussion
… they have a multi organization agreement
… this is something that the legal department need to fill in
… the liaison message should go to the W3C Liaison Team (at team-liaisons@w3.org)
McCool: possible next charter topics about geospatial
AOB
Cristiano: UNIBO also presented at the IEEE workshop.
Lagally: please invite your colleagues to the next Use Cases call on Jan 25.
Lagally: will do.
<cris> https://
[adjourned]