Meeting minutes
<McCool_> https://
Previous Minutes
<McCool going over minutes>
McCool: any objections?
-> none -> minutes approved
Quick updates
IEEE P2874 Updates
McCool: invited to give a talk
… 1 June 2022 at 1:00pm Eastern Time
… will prepare draft
Cancellations and updates
McCool: Arch Call moved to Editor call slot
… forgot to update W3C calendar
… will do that next time
… will setup dedicated DTDL call invite to avoid confusion
Lagally: Use use-case call dial-in?
McCool: not possible, conflicts with editor call
… cleaner to have a dedicated invite
Kaz: WebEx for editor/use-case has been changed, so we can use that
<kaz> wot-tuesday-8am-boston (Member-only)
McCool: Suggest new invite to avoid confusion
McCool: Hannover fair?
Sebastian: Next week, Monday to Thursday
… Ege will most likely not be available also
McCool: Please update cancellation section
JP Member meeting
Kaz: had meeting on Wed last week
… talked about several updates
McCool: Follow-up items?
Kaz: resources are in Japanese
… got good impression on WoT as well :)
Publications
Wide Review
McCool: Issues are in flight
… TDs has completed all necessary changes
… in draft, for discovery
… Explainer is pretty much done
… ready for review next week
… we need to publish WD, e.g. Architecture
… we have Explainer draft for Profiles
… needs some more work
Sebastian: One issue open for TD w.r.t. internationalization
… we hope to solve it today
McCool: The extension plan is slightly out of sync
… https://
… BTW, TPAC 2022 has been confirmed
Calls for WD Updates
McCool: 2 week review time... normally
… I suggest 1 week review period
… TD is in flight ...candidate branch today?
… any objection for 1 week review
… 2 weeks will impact schedule
Lagally: WD update closed when?
McCool: It takes about 1 week to go through process
… after creating branch we can work on WD
Lagally: Next week is a problem. Vacation period in Europe
McCool: Not a CR candidate
Lagally: wondering about cut-off date for MergeRequests
McCool: Branch today
… rest goes to next draft
Sebastian: I think we talk about CR, not WD
McCool: For CR, we need 2 weeks
Sebastian: Correct, we are heading to CR
<kaz> Guide on how to edit the draft for publication
Kaz: editors, please look at guideline and check documents
… the faster we can resolve issues the faster we can publish the drafts
… please generate a static version HTML in addition to tagging a branch for the document check
McCool: w.r.t. Architecture, we have a stable version for a week already
Lagally: Suggest not to rush
McCool: Okay, let's give architecture 1 more week
… for TD, we should allow for 2 weeks from now
Sebastian: CR version, right
McCool: Yes, but let's decide later
Sebastian: Okay, we will merge the pending PRs today.
… freeze the document, review for 2 weeks
… in 2 weeks we decide on CR or WD depending on (number of) comments
Review other Ongoing Action Items
Liaisons
McCool: Sebastian will setup OPC UA meeting
McCool: ITU-T SG20, they are working on smart-city
… Next SG20 mtg is 19-28 July 2022; need further followup before then
Kaz: ECHONET likes to start further collaboration with the WoT-JP CG first
McCool: I see, will be input to next charter discussions
Kaz: IEC CDD (Common Data Dictionary)
Kaz: will talk about the next steps with them on June 13 again.
AC review
Kaz: AC review announcement was send out yesterday
… please ask your AC rep
… we need 20 supports in total
TF Reports
Architecture
Lagally: Architecture document is stable, please review
Profile
Lagally: talked about real out-of-the box interoperability
… please provide comments
… we talked about proposals/platforms
<McCool_> https://
Discovery
McCool: Talked about security bootstrapping
… like HTTP negotiation
… I hope all concerns are addressed
Marketing
<McCool_> https://
McCool: would like to focus on "Should the CG manage (some of) the WoT web pages?"
… Clarification to limit scope of CG
… like : Developers, Documentation, and Videos
… purely about content
… not design et cetera
… pages are about informative documentation and training materials
Ege: we don't want CG to be another group
… we would like to have specs better visible
… don't plan to have separate page for CG
Ege: moreover, marketing task force is currently a website taskforce
… outreach should become a CG task
McCool: Important question. Is CG responsible for the afore mentioned pages
Kaz: Agree with McCools comments on issue
… all WoT groups should clarify what they do
… the W3C Team provides auto-generated pages
… We WoT-IG/WG should think about what to be added to our own generated pages in addition to the /groups/wg/wot and /groups/ig/wot, and the CG also should think about what to be added to the CG page in addition to /groups/cg
… for example, Japanese group drives outreach event information and deployment guideline information on their own generated pages
<kaz> Auto-generated group page
<kaz> WoT-JP CG page as an example
Lagally: Confusion comes because we do not have clear definitions
… marketing taskforce responsible for outreach
… CG more for meetings, testings
… CG should not do official communication
Ege: Who does do official communication?
Lagally: the main website should stay within WG/IG
McCool: I suggest to use same page, but sub-pages might be handled by CG
Ege: not sure if this is what we want
McCool: Tools list for me can be a CG task
… new feature should be an IG activity
… suggest to separate content CG vs IG/WG
Sebastian: activity in marketing / website can be seen as CG results
… should consider having a different webpage
… not hosted by W3C, like json-ld.org
Daniel: I fear splitting sites creates confusion
<sebastian_> I need to go.
Cristiano: Issue is clear. Can CG publish content on those 3 pages.
… we can ask for a vote?
… suggest to have a single website
Kaz: Different opinions from different people
… need more discussions
… it sounded to me that some would like the CG to maintain the consolidated WoT page at www.w3.org/WoT
… but CG is different from W3C process viewpoint
McCool: Please provide comments in issue 321
… please focus on question: CG to manage content on 3 pages
<McCool_> https://
<kaz> [adjourned]