W3C

DTDL / VSSo

08 Mar 2021

Attendees

Present
Ted, Mario, Ash, Jeff, Mike, DanielA, Ron, Daniel, MagnusG, Benjamin, Jay, Gunnar, Joakim
Regrets
Chair
SV_MEETING_CHAIR
Scribe
Ted

Contents


Introductions, overview and goals

<scribe> scribenick: ted

Ted frames goals for call, gauge interest in VSSo2DTDL, initial feasibility and practically how to go forward

Daniel: VSSo use cases what is the current status, historic data, how to connect to service which goes more into direction of WoT
... we are discussing how to realize it. VSSo domain knowledge can be used in a number of ways
... I have looked into DTDL and how to use it, as a starting point want input on building ontologies RDF2DTDL something MS exploring?
... already have some favorible results. do we take VSSo and requirements from DTDL

Ted: has anyone from MS looked into this and formed opinion?

Jeff: I have looked into VSSo and lining up with DTDL, done VSS translation to DTDL
... after a meeting with GENIVI a couple weeks ago, contacted colleague in digital twin teams
... one wrote a quick translator to see how much work it would be, doable in a couple hours
... what it tells me it is fairly aligned syntax and semantics
... discussion has to be first on overarching goals/use cases
... what is their intent?
... DTDL intent is digital twins, that is both physical and logical layer
... we haven't seen anything on physical side, ability to overlay that with logical layer
... it is not just sum of signals but full overlay
... other thing about DTDL, it is designed to be broad all-encompassing across industries
... we are interested in VSSo as representation of transportation and how it can speak to other industries
... part of the other intent/goal, what does it take to make such an ecosystem
... how do we create that?
... there is a third element, when we start talking about ecosystems what does authorization look like as that is quite complex
... I think we might have some of the wrong people here, should have Christian, JB and Brian from MS
... they are really experts and specialists on DTDL

Ash: agree, need more of a follow up meeting
... interesting that RDF was raised earlier and how that relates to the whole scheme of things. I haven't looked at RDF2DTDL

Daniel: I looked at mapping you showed and possible generator, already getting started in technical discussion
... what I meant with domain ontology is ecosystem point. we can describe the vehicle but it becomes more powerful in an ecosystem
... fully agree we would benefit from defining vehicle and be able to include in your ecosystem

Ted: we recently released a refactored VSS, influenced by ontology work. we are discussing some design decisions and would be better to include MS early on to avoid issues later trying to align with DTDL

Jeff: so I can help queue up these things, we are talking on our end about the next steps and fully support the program
... Azure works on semesters - six month intervals. we are midway
... we are trying to figure out how to align this
... we should be able to be show a plan, ability to create a generator
... we can easily do a PoC, next level would require more funding
... this doesn't preclude us from having discussions in the meantime

Daniel: are you able to open start of your work up so I can compare to what I have done?

Jeff: that is a really great idea
... Christian did his own thing and not sure it represents the DT team, Ron can help

Ron: we can express information about what has been done in the meantime. DTC is kicking off open source, governance and structure
... some of the work being done here can be included there

Ted: we can get this started in a more limited scope

Next steps

Two weeks

Ron: next semester is where we can work on this, next couple months as early phase as described is useful

Ash: it might be early for us to join in on VSSo but please let us know when that meets

Mike: we have automotive domain experts present but also need our DT team involved
... we need to align with DTC which is Ron's area
... we need both our auto and DTDL people present, how to staff that will need to be understood

Ron: DTC is not a SDO but consortium and will need to figure out how that will work

Mike: do you think we can clear that up in the next couple weeks?

Ron: we have discussed with GENIVI about DTC, where we are with that and its vertical groups. there isn't one at present for automotive
... we can start with a liaison agreement and how to organize
... make sure IPR is in sync. there may be enough interest for an auto group within DTC as well

Ted: we can form liaison either formally or informally [describes ways]

Ron: we don't have to rush and have that in place before our next meeting

Daniel: we used WoT for M2M bridge and created a IoT PoC using VSSo

Ron: at this point, MS is not participating in WoT but keeping track of it. it looks like it might align with DTDL

Gunnar: primary thing with DTC is alignment with W3C on WoT
... WoT seems very useful in aligning multiple technologies, I am more interested in aligning on data model more than how to bridge disparaging

Ron: we have worked on language and licensing for covering three areas. DTC surveys what is out there and worth adopting or aligning with
... some of the partners are taking their DTDL conversions to open source
... in addition to code, vocabularies and ontologies to be published
... we imaging smart cities wanting to sync data with digital twins
... we have licensing around data management as well

Gunnar: is there anything preventing you from getting involved?

Mike: we are consumers of what our group produces, we are committed to VSS and VSSo at this point

(on connected vehicles at MS)

Mike: we will want to continue working with you

Ted: I will forward invite for tomorrow's call on VSSo should anyone be able to attend and reschedule a WebEx for two weeks from now for presentations on the two approaches to bridge VSSo and DTDL

Summary of Action Items

Summary of Resolutions

    [End of minutes]

    Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version 1.154 (CVS log)
    $Date: 2021/03/08 20:47:41 $