Meeting minutes
Guests and IE applications
McCool: still waiting for WG application from Luca, the WG has confirmed already
… there is another IE application from Mahmood Afshari
Kaz: we need some discussion in the chair call
McCool: we do need people as volunteers
… we also have a policy for IEs to review later in the agenda
minutes review from February 19th
<kaz> Feb-19
McCool: any changes or updates?
… minutes are approved
Quick Items
DST change
<kaz> MarComm announcement (Member-only)
McCool: Daylight Savings Time is happening next week
… W3C meetings are based on the US Eastern Time zone
… In Europe and Japan, the local time of the meetings will change
Notices
McCool: any notices?
Deno
McCool: would like to bring up the Deno runtime for node.js
… a web-compatible version of the nodejs platform
… lots of webby features and supports typescript out of the box
Daniel: Luca tried node-wot and it seems to work
McCool: the framework is also more mature now, at version 2
<kaz> Deno site
Ege: nodejs is adding features to keep up
<EgeKorkan> https://
Ege: at the WoT CG there are people looking for resources to help promote WoT
McCool: the explainer should have a list of benefits
Kaz: do we want the scripting API TF to evaluate Deno?
McCool: it's more of a thingweb issue
Kaz: the Scripting API TF are discussing the browser environment
Daniel: can create an issue for Scripting API about this
meetups
WoT CG
McCool: watched the CG video on JSON Schema and AI, it's worth watching
McCool: next CG presentation is about Mixed Reality
WoT JP CG
McCool: anything new in the WoT JP CG?
miz: nothing new
McCool: It may be better to combine calls and have a single call, possibly using real time translation
Smart City IG
<kaz> Smart City IG's GitHub repo
Kaz: created the github repository to collect resources
McCool: it is an IG and there is a need to officially join
… people should apply right away because of the delay
… is there a topic for the next meeting?
Kaz: organization and resource collection
Cloud-Edge-Client CG
McCool: working on organization
Liaisons
McCool: anything new for any of the liaisons?
McCool: ETSI CIM met on Monday the 3rd
… discussed alignment with WoT and need use cases
<kaz> liaison minutes.html Mar-3 minutes
McCool: we captured 4 use cases to start with
McCool: we have a weekly schedule but will have a break from end of March
<kaz> Meeting plan on the NGSI-LD liaison wiki
McCool: we will try to make progress on use cases in March
Schedule
<kaz> Holidays and Events
McCool: the cancellations are recorded on the agenda document
… there are no cancellations in March or April
Kaz: will not be available on March 19th and 20th
McCool: Then we will cancel the March 19th main call
McCool: Kaz ia also unavailable April 16th, so we will cancel the main call then also
… any objections?
<kaz> (none)
Policies
McCool: any updates?
Koster: no new updates but I think the IE policy is ready to merge
<kaz> PR 1224 - Create invited-expert.md
McCool: we need an update to the policy policy, will discuss at the chair call
McCool: anyone object to merging PR #1224?
… last call, any objections?
<McCool> proposal: Adopt new IE Policy at w3c/
RESOLUTION: Adopt new IE Policy at w3c/
McCool: as an ad-hoc resolution, we have a 2 week period to reconsider
McCool: merged
… any other policy discussion?
<kaz> remaining PRs
McCool: (moving some other unrelated PRs to UCR)
<kaz> Issue 1208 - [Policy Proposal] Managing moderator policy
<kaz> Issue 1166 - [Policy Proposal] Versioning Resources
McCool: we still have moderator and versioning policies to work on
Koster: is there anything to merge on Roles and Responsibilities?
McCool: should be added to the policy policy
… will discuss at the chairs call
TF reports
TD/Binding
<kaz> TD Issue 2054 - Reconsider id being optional
Ege: There is an issue on TD and Binding regarding the mandatory ID property
Ege: issue #2054
Ege: the consensus is that ID should be mandatory
… and should not be globally unique and permanent
Ege: we don't require a specific format but provide sensible guidance
McCool: 2 properties are uniqueness and permanance
… permanence is avoided because of the danger of tracking
… but uniqueness may be needed to avoid conflicts
Ege: for example, if the device moves and gets a new IP address, there should be a new ID
… before merging a PR, we would like to get another review from the privacy WG to avoid extra changes and confusion
McCool: any more comments?
Kaz: agree that we should start working with the privacy WG
McCool: RDF requires a unique ID, so we should keep the discussion on the permanence property
… any objections?
<McCool> proposal: TD TF may proceed with plan as discussed in w3c/
McCool: any objections to the resolution?
RESOLUTION: TD TF may proceed with plan as discussed in w3c/
McCool: resolved
AOB
McCool: any other discussion?
Kaz: there is no profile meeting this week since there is not an official moderator yet
McCool: anything else?
… adjourned