<scribe> scribenick: kaz
McCool: (goes through the agenda above)
Virtual F2F minutes - Discovery session
Kaz: March 2 minutes had been already approved
McCool: let's review the minutes from
the virtual f2f then
... (goes through the virtual f2f minutes)
... need terms for Vorto
... one issue for discovery on Vorto to be created
... (creates an issue)
... align with Eclipse Vorto
... Kevin, do you use directory, etc?
Kevin: for Vorto, we use a virtual repository
McCool: Vorto repository stores and
manages models
... (adds comments on Vorto based on Kevin's clarification)
Kevin: TD template is conceptually similar to the Vorto model
McCool: partial TD may describe
classes
... we need some URL template to specify template
... we still need to discuss the detail
... also we need to see the relationship between TDs and Vorto
models
... my proposal is using links
... URLs point to models
... if we do that, Vorto repo and TD directory are
different
... Vorto repo stores and manages models
... TD directory stores and manages TDs describing device
instances
... need to look into existing IANA media-types that might work
here
... Vorto model is a JSON file?
Kevin: domain-specific language
McCool: content-type already registered?
Kevin: no
McCool: probably need registered IANA
MIME type for Vorto models
... this discussion should occur during the WoT Architecture
calls
Kevin: note that we don't use TD Template inside Vorto model
McCool: yeah
... what is the exact mapping between Vorto concepts and
built-in vocabulary in TDs?
... we need to do a mapping with the information model
and
... (goes through the information model from the TD spec)
TD spec - 5. TD Information Model
McCool: how to align Vorto with
TD?
... similar image to the TD Information model Figure 1
<McCool> https://github.com/w3c/wot-discovery/issues/7
McCool: would suggest you create a Pullrequest to put contents
Kevin: ok
fyi, pullrequests for wot-discovery repo
McCool: (quickly goes through the slides)
McCool: feedback from users, e.g.,
during TPAC 2020
... would like to add TD for devices supported by EdgeX
... EdgeX has its own application stack
... (core services section of the EdgeX platform archtiecture
include microservices intercommunicating with each other via
APIs)
... Proposed WoT/EdgeX Integration
... can do JSON matching or something
... have directory service and APIs
... would registere myself in the directory service
... to demonstrate 2-phase concept
... also node-wot inside EdgeX
... for WoT orchestration
... upload scripts and invoke them
... item 4 is optional and nodeRED orchestration is higher
priority
... still in planning phase
Christian: where node-wot would fit within the architecture?
McCool: all EdgeX is service-based
docker container
... orchestration inside EdgeX
... 2 issues
... how to build the container
... and instantiating it
... might have some examples
... retail examples could be resources for scripts
... but in general need to see how to build our own scripts
Christian: there are already some
endpoints existing
... upload script, start and stop it
... would be a good timing to extend the interface
McCool: any resources about that?
Christian: let me take an action about doc container
McCool: it is critical to integrate
EdgeX
... they currently use open APIs
... part of this effort, we define APIs for a directory
service
... my intention is making it public
... will work on it temporally at my private repo due to NDA
things, though
... (creates a new issue on the wot-discovery repo)
... define a concrete network API for a TD directory
service
Christian: thing-web repo is a bit outdated
McCool: yes
... we should see the current status existing implementation
for TD directory
... (adds a question about that for Victor)
Kaz: we should add some
description about our plan itself on the
wot-discovery/README.md
... how to do our PoC including EdgeX, node-wot, wot discovery,
etc.
McCool: yeah, maybe we could have a
specific directory for the PoC purposes
... maybe need to clean up the directory structure
... e.g., move prior.md to the prior-work directory
... and update the README.md
... let's create an issue
... create structure to organize PoCs
McCool: also reorganize prior work
toumura: question about the main
purpose of this PoC
... just for discovery?
... or maybe all the related building blocks?
... maybe better to put the PoC work under wot repo rather than
wot-discovery?
McCool: this PoC is specifically for
discovery
... but maybe would be better to go under wot repo
... let's discuss in the main call
... can be sensitive due to NDA things, etc.
... anyway we still need this issue 9 itself
McCool: questions?
Christian: rather a comment
... we already have TD
... the proposal doesn't really include how to generate
TD
... we should include some description about that
... also the mechanisms how existing protocols support
discovery
McCool: likewise "discovery" doesn't
mean "broadcast"
... the actual meaning of the current text is a bit
different
McCool: let's create an issue to
improve the text
... (create a new issue)
McCool: let's put concrete descriptions to the issue during the next call
[adjourned]