Meeting minutes
new members
Sebastian: Elodie Thieblin has joined as a Siemens participant; is semantic web expert
Sebastian: regarding invited experts, none, but we may be inviting a guest from Cologne interested in BACnet testing to TD call
Kaz: inviting people to public calls is ok, but make sure they can commit to patent policies, etc.
minutes
<kaz> Nov-23
Sebastian: review minutes from 23 Nov 2022
Sebastian: any objections to publishing?
… hearing none, will be approved and published
quick updates
IIWoT Workshop
Sebastian: we had proposed a keynote, but they required in-person attendance, which we cannot do
… resources, travel restrictions
… McCool has offered a remote presentation; no response yet
cancellations and schedule changes
Sebastian: testfest will be in two weeks; is a tentative schedule
McCool: we should have a resolution to finalize these times
proposal: fix testfest schedule (Eastern timezone): 8am M/T; 9am W; 10am T on Dec 12-15
RESOLUTION: fix testfest schedule (Eastern timezone): 8am Mon/Tue; 9am Wed; 10am Thu on Dec 12-15
McCool: let's update the general cancellation policy to include Jan 9; only have to mention exceptions to that
Sebastian: also there is a use case call scheduled for Dec 6
Lagally: would also be good to go over gaps for charter input; let's have the call, and I will chair
McCool: for now let's use the "canceled" Editor call logistics/calendar entry for this; I will try to clean up
Kaz: note that the current "Editors call" with the "canceled" label starts at 8am Eastern which is the expected time (=one hour later than the Marketing call)
McCool: also note that a lot of the calendar entries expire end of Jan; we will have to update at some point
Kaz: also for Marketing call need to update webex coordinate so Ege can be host; will be updating calendar
Schedule Changes
<kaz> wot repo - PR 1045
Sebastian: schedule changes
… see wot PR 1045
McCool: in summary, schedule changes to deal with delays in CR transition and to allow time for new WG charter
Kaz: generally ok with these changes, but please remember that we need to think about two schedules in parallel, one on this kind of spec generation during this Charter period and another on the WG Charter generation for the next period.
McCool: probably need a resolution as well to request a 3mo extension
proposal: request a 3m extension to our current WG charter in order to complete CR/PR transitions and to merge PR #1045 under the assumption of such an extension
<Github> https://
proposal: request from W3M a 3m extension to our current WG charter in order to complete CR/PR transitions and to merge PR #1045 under the assumption of such an extension
<Github> https://
proposal: merge PR #1045 under the assumption of a 3mo extension
<Github> https://
Lagally: these changes do have implications for members; some members may need to check with AC reps, etc.
McCool: definitely consider this notification; can send an email emphasizing it
Sebastian: ok with postponing the resolution to ask for an extension
McCool: suggest we ask for the extension in Dec once we see the CR transition is done
Kaz: W3C charter says that extensions less than 6mo can be at discretion of W3M
McCool: suggest we definitely discuss this in the main call after the testfest, which will be the last one this year
proposal: merge PR #1045 under the assumption of a 3mo extension
<Github> https://
RESOLUTION: merge PR #1045 under the assumption of a 3mo extension
<Github> https://
publications
general situation
Sebastian: have talked already about CR transition status
… situation is generally that we have three deliverables ready for CR transition but we are still waiting
… although the request for Architecture as a little bit later than TD and Discovery
… we did have a meeting on Monday to clear up some i18n issues in Discovery
McCool: TD i18n discussion on Monday was only an implementation clarification
Profile
Sebastian: for profiles we are aiming for a candidate for use in the testfest
Lagally: mostly were discussing Arch in today's call, will be discussing Profile in tomorrow's call
… but we also need implementations that are candidates for being profile compliant; for the most part this should be easy, just adding the profile qualifier
… can discuss further in testing call
… also there are several PRs on the table for Profiles that need review
McCool: does doing a WD on Dec 8 still makes sense?
Lagally: I think after the testfest makes sense
McCool: also think we want to freeze the spec for the testfest after tomorrow's call
Lagally: how hard is it to publish a WD?
Kaz: should not be hard, since it's not FPWD, as long as it passes the testing tools
Lagally: ok, I do suggest we publish the WD this year if we can
… let's discuss in tomorrow's call
Sebastian: for testfest at a minimum we need a freeze for testing
Kaz: regarding IANA, still some fixup to do
McCool: also DID, but neither is a blocker
Sebastian: regarding Societal Impact Q...
McCool: will probably only get to it in Jan, right now at-risk gaps are my priority
Next WG Charter
Sebastian: proposing a call series Jan 16-20, cancel other meetings, have 4h of meetings to develop new WG charter
… we tried to reuse existing slots that are also in the sweet spot to allow people from all timezones
… hearing no objections, let's go ahead with this plan
TF review
Sebastian: anything to share
Discovery
McCool: small change to Discovery that updated CR candidate: UTF-8 -> Unicode code point order
Scripting API
Daniel: end of Jan want to publish updated Scripting API better aligned with Discovery
Architecture and Profile
Lagally: already mentioned Arch and Profile
… but want to clarify manual.csv