Meeting minutes
minutes
https://
<McCool> https://
<MM shows the minutes>
Kaz: just updated the speaker names
McCool: how we handle big pdf files? github has a file size limit
… we need another place
Kaz: you can send it to the w3c-archive or simply send it to me so that I can install it on the W3C server.
McCool: there is also a limit
Kaz: I can upload to W3C
<Ege> regarding large file storage, please have a look at https://
McCool: propose to publish. Any objections?
Ege: about the file size I shared 2 links about Git Large Files
Sebastian: W3C wiki also allows file upload
McCool: any objections to publish the minutes?
no
McCool: let's publish
Quick updates
Use Case call
McCool: Use case will be held every Tuesday
… there was problem with meeting details
… next meeting will be next week Tuesday
Lagally: Any inputs for the requirements are welcome, also from non-members
<McCool> acvk k
Kaz: we should document the process and policy about handling use cases and requirements.
Lagally: agree
Meeting with PLH
McCool: PLH is ok to do fixes on Arch 1.1 and Discovery without a new CR
… also discussed on OPC UA.
… there will be a seperate exchange with Sebastian
Kaz: PLH's clarification is basically inline with what I've been mentioning. However, there is still the need to get enough implementations.
McCool: yes, however, there are features where no libs exists so far. We need to check how to handle this.
Cancellations
McCool: Discovery is cancelled on Feb 6
McCool: there will be a Arch call tomorrow. However, the W3C Calender system needs to be updated.
Publication plan
https://
McCool: I will update the entries for Discovery (no new CR is needed)
Lagally: I think it is realistic to have wide review within 2 months.
McCool: however we will have problems to work on the feedbacks on time if it comes too late
Kaz: please add clarification about important milestones within the schedule, e.g., wide review and implementation experience. Please note that Testfest is not required from the W3C Process viewpoint, but we still need to clarify how to get the implementation experience.
Lagally: if you have a profile compliant implementation you are welcome to provide TDs anytime
WG Charter
Charter extension
McCool: charter is extended, right?
Kaz: yes
thanks Kaz
<kaz> current WG charter (extended till July 31)
Charter meeting minutes
<MM review the minuts from Charter meetings>
McCool: any objections?
no
McCool: any objections?
no
McCool: any objections?
no
McCool: any objections?
no
McCool: all minutes will be published
Next steps
McCool: we need to clearify how to proceed. We have some PRs waiting. I expect to have another 4h for discussion.
… we should find best time for doing charter discussions
… there is a doodle poll provided
Doodle for the 2nd Charter meeting
McCool: please provide your options
McCool: Idea is to have a temprorary repo to always see the latest rendered charter version
… if finalized repo will be deleted
Kaz: I can setup repo today
<McCool> w3c/
<MM shows some PRs which are waiting to be merged>
https://
McCool: PRs will be moved to the new repo. The easy one will be merged.
Ege: The binding template part has too much details. Should it merge first and then reduced the content afterwards?
McCool: Prefer merging first as is as good starting point, but the Charter itself should include the summary.
Kaz: Ege and all, please summurize your discussions. Details should be provided somewhere else.
<MM shows the current Scope section of the WoT2.0 charter>
Ege: Maybe this already too much, so we should just list the deliverables
Kaz: If you have details description already, please just move to a different place
Sebastian: is there a link in the charter to detail description place then?
Kaz: there is no need for doing so. Details can be provided on wiki or GitHub as the starting point of our spec work for the next Charter period.
Lagally: It should be marked where we already have a group consensus
Liaisons
McCool: Sebastian will meet PLH to discuss the OPC UA liaison
TF Reports
McCool: any news to share?
… seems not the case
AOB
<Ege> https://
Ege: wondering if it's possible to create a calendar entry for a tentative call
... just tried to that as above
... note the title has been changed to "CANCELLED WoT Marketing"
<kaz> [adjourned]