W3C

– DRAFT –
WoT and NGSI-LD

13 January 2025

Attendees

Present
Charith_Perera, Dave_Raggett, Frederic_LE, Kaz_Ashimura, Ken_Zangelin, Martin_Bauer, Michael_Koster, Michael_McCool, Rigo_Wenning
Regrets
-
Chair
McCool
Scribe
mjk

Meeting minutes

Minutes review

<kaz> Dec-9

McCool: any objections to approving the minutes?
… no objections, approved

Agenda

<kaz> Agenda for today

McCool: we are having meetings weekly to get started
… asking people to add documents to the github repository
… would like to clean up the repo as part of the agenda
… we can gather resources
… there is a PR to merge the liaison charter document into the reop

Martin: we need to decide how to proceed and develop some simple and concrete initial examples

McCool: I think it will be helpful
… we could work toward a use case

Kaz: agree with mccool, thank you Martin
… maybe we could use the W3C WoT's use case template

Rigo: discussing use cases would be a really nice idea
… how does the application layer of WoT relate to NGSI-LD?

<rigo> especially for robotics, the StandICT landscape analysis for digital twins just came out: https://www.standict.eu/landscape-analysis-report/landscape-robotics-standards

McCool: can we add Martin's initial presentation to the repo?

Martin: will go look for it

McCool: if you think of something to add, please make a PR to add it

Liaison document

McCool: the only update is changing language from binding specific to a more general "document"

Martin: we could add the NGSI-LD spec but it's large

<kaz> wot-ngsi-ld PR 1 - Create liaison.md

McCool: merged PR #1

<Charith> I guess, this project used NGSI https://cordis.europa.eu/project/id/732240/reporting (perhaps as a associated project or usecase, if helpful)

<Charith> https://oascities.org/wp-content/uploads/2022/08/SynchroniCity_D2.10.pdf

Examples of use cases

McCool: makes sense logistically to put them in the repo
… creates "examples" directory in the repo

McCool: we can also link to external documents

McCool: it would be useful to brainstorm some topics
… functional clustering of resources?

Rigo: it describes how to cluster things in a complex system
… for WoT there is a consistent interface, then how do you cluster for example hundreds of sensors
… it's a simplification of workflows

McCool: in a WoT TD, there can be multiple devices and separate functions
… TDs are linked data

McCool: are there any other thoughts on categories of examples

Martin: let's check the use case in the primer for a starting place

McCool: this could become a to-do action item

Kaz: agree, we could start with a brainstorm around use cases possibly including smart city use cases rather than strict description according to the WoT template

McCool: at a previous meeting, we discussed using WoT to model digital twins

McCool: another use case is using TD to onboard devices
… another case is describing a northbound interface for digital twins

Rigo: there is a landscape analyzer as a negative example, it is only a list of specifications and doesn't explain how the standards relate to another

Martin: agree, we don't want a list and would rather keep things small and compact

McCool: what are the subcategories of digital twin, i.e. location, device shadow, etc

Rigo: we should clearly define our boundaries
… from a legal perspective
… there is no upper bound on what can be done

McCool: safety and privacy are not unique to smart cities
… not a data model problem in general
… not sure also what WoT brings to the table

Kaz: part of the brainstorming is noting which topics fall under WoT/NGSI-LD

Rigo: an example is a sensor that has built-in security logic that can interoperate with a smart data management system
… for example, a block in the TD containing this metadata can allow smarter data management by pushing it down to a lower level

Martin: what is the functional part of this interface?

McCool: it reminds me of functional items for safety we discussed in WoT some time back

McCool: there are policies and rules that have metadata support

Rigo: this is precisely what I am talking about

Koster: another item is what is the scope of things that can be modeled using TD that may not have digital interfaces

McCool: OK, I will commit this now, please create separate .md files for things that are added

McCool: that is all I had for the agenda
… next meeting is January 20th

McCool: are there any other items for the agenda today?
… ideally we will have some PRs to review next week
… is there any other discussion or business for today?
… OK, let's adjourn for today

<kaz> [adjourned]

Minutes manually created (not a transcript), formatted by scribe.perl version 242 (Fri Dec 20 18:32:17 2024 UTC).