Meeting minutes
Apologies
McCool: apology regarding the confusion around the Teams meeting for the WoT Week session
Kaz: the last topic 9 was a quick summary by McCool
Self intro
Kaz: first meeting for Frederic
Frederic: from AFNeT working with Martin and Franck
McCool: note that we use the W3C Calendar to manage the Zoom calls
Agenda
McCool: (goes through the agenda)
McCool: Jan 6 would the first meeting for 2025
… any topics to be added?
(none)
Minutes
McCool: would think about rotating the scribe role :)
… starting with the meeting in January
… (adds a list of the scribe to the agenda wiki)
… (then goes through the previous minutes)
… regarding the minutes themselves, any changes or fixes needed?
(none)
McCool: Kaz, you basically distribute the draft minutes beforehand. right?
Kaz: yeah, every time (basically)
McCool: please review the draft minutes beforehand also
WoT Week minutes
McCool: (quickly goes through the minutes)
… (specifically the section 9, ETSI ISG CIM for NGSI-LD)
… Erich from Microsoft, the F2F host there, presented several tools
… interesting materials for testing, etc.
… I think we should look into that
… the other things brought up was NGSI-LD server talking with devices
… onboarding for devices
… there are two kinds of usages: north-bound and south-bound
… another point was discussion about possible binding
… we have WoT Profile also
… can think about sub-profile also
… (shows the OPC UA liaison section also)
McCool: have to ask Erich about the detail
… that's the minutes from the WoT F2F in Munich
Juanjo: need to look into what you mentioned, but not sure about their approach
McCool: agree
… let's raise an issue for further discussion
Juanjo: not pretty sure about their approach
… would hear from Martin, etc.
… but FIWARE handles things based on NGSI-LD
… WoT Thing Model is agnostic with the protocol
… how things could be considered as instances of the model
… which could be accessed from NGSI-LD
… there could be a Thing Model which can be accessed from NGSI-LD
… then we can on one side from NGSI-LD by FIWARE/ETSI and WoT side describing the entity classes
… NGSI-LD can be used to interoperate with the things
McCool: there are two things here
Juanjo: the definition of "Things" focused on not necessarily "devices"
… maybe physical ones or might be virtual ones
McCool: that's a fair point
… we have linked data, and there are different kind of "Things"
… my personal opinion is that you can do it from the scratch
Juanjo: remember how this discussion started
… standard API for digital twins
… physical or digital devices
… common understanding with the WoT Thing Model for the ingredients for the entities
… then NGSI-LD interact with the digital twins
McCool: we do have model for Thing Description
… real question is mapping ontology, etc.
<McCool> ege: https://
Ege: presentation by a company about a use case from eclipse ditto
Ege: the person was at the Plugfest
… this is already possible for TD, I think
McCool: even though there is no blocker, would see what can be done easier
… need to dig it up
… would talk with Erich about the detail a bit more
Juanjo: know about the work by Microsoft
… there is an initiative about smart datamodel
<McCool> https://
Juanjo: for a given model for digital twins
… (Juanjo gives some description about the Smart Data Models)
… don't know which actual model to be picked up...
… corresponding similar digital twin mechanism
McCool: (shows "dataModel.Building")
Juanjo: there is not description language for dataModel.Building. right?
… if WoT Thing Description could be assigned to that, we might be able to use that
Kaz: let's not dive int the detail about that
… but let's talk about the logistics and planning doc for today
McCool: yeah
Logistics
McCool: Kaz, you can make the meeting on Jan 6. right?
Kaz: yes
McCool: so the next meeting after this meeting will be Jan 6
Martin: public holiday in Germany
McCool: we can shift the meeting by one week
Kaz: note that this is a bi-weekly meeting
McCool: may impact the WoT CG meetings then
Ege: don't worry
McCool: next meeting on Jan 13 and every two weeks after that
Martin: might be better to have the meeting every week for a while
McCool: ok
… Jan 13 and then every week until mid-Feb after that
Charter
McCool: would like to update the Charter (=planning doc)
PR 1209 - Activate Liaison for ETSI ISG CIM for NGSI-LD
McCool: this PR is putting the proposal to the actual area, but it's too early
… so would close this PR itself without merging
… and then create a new PR for further updates
(new PR) PR 1222 - Update ngsi-ld.md
McCool: (goes through the changes)
… need some more detail here
… we can mention some more concrete documents like possible bindings
… or we can define concrete deliverables externally
Juanjo: we didn't have time so far, but would make some requests
Martin: not sure about how to work on that
<McCool> w3c/
Kaz: probably we should use the dedicated wot-ngsi-ld repo for further discussion
… to let ETSI guys give direct contributions easier
Kaz: can add you all from ETSI to the collaborators for the repo (like we did for the W3C server)
… sorry but we need to do that for GitHub again since it's a different system from the genuine W3C server
McCool: (shows how to make contributions to the GitHub resources via Pullrequests (PRs))
… you can also create a dedicated branch for your edit
<McCool> w3c/
McCool: (creates an initial PR as above)
… (also adds some more topics like the Smart Data Models)
Kaz: please let me know about your GitHub account so that I can add you all to the GitHub collaborator Team for the wot-ngsi-ld repo
… also for Frederic, please let me know about your email address, and I can help you create a W3C account also
[adjourned]