<kaz> scribenick: glomb
McCool: Chris Ambler is invited
<inserted> Feb-17 minutes
minutes feb 17 review: note on publication schedule done
previous minutes approved
McCool: would include michael kosters slides
Zoltan: different things: discovery in scripting api vs semantic discovery
repo reorg: wot discovery re-structured
background needs update
<inserted> Issue 3
issue #3
e.g. mdns
clarify core resource directory
proposal: two-phase-directory-based discovery
PR wanted for alternative ideas
clean up directory.md
readme for use-cases
use issues (problem) and PR (suggestion)
or add to already existing PRs
Zoltan: proposal as a whole (PR)
then split up
issues and PRs
<inserted> Issue 2
issue #2: relevant for security TF
<inserted> Issue 3
issue #3: McCool will elaborate
review of DID:
<McCool> https://github.com/w3c/wot-architecture/blob/master/proposals/2020-02-WoT-DID.pdf
w3c wg
e.g. with the help of blockchain
url scheme includes method + method specific id
resolves JSON document
kind of directory service (decentralized)
how to use in WoT: thing ids
dump TD info into DID document...
or point to TD directory
Andrea: point to discovery service (deal better with security)
McCool: or point to thing directly (.well-known/core)
authenticate before
similar approaches
lacking: more general concept
device may not host own TDs -> directory service
typed links
some other non-directory based way to retrieve TDs?
Andrea: blockchain could do
... upcoming paper - how to retrieve RDF from blockchain
DID will have multiple methods how to retrieve documents, no specification how it works behind the scene
not just Core RD in our proposal
to be elaborated
<zkis> https://w3c.github.io/wot-scripting-api/
discovery in scripting api
discover method defined in Scripting API
thing filter: search everything / directory / local / multicast
local: bluetooth, nfc, beacon, local hardware, ...
McCool: propose to make it more abstract
directories might be represented as a thing, then multicast might find it
discovery - two phase approach might meanigful
"multicast" might be re-phrased
DOMstring e.g. TD fragment
how to authorize - to be done before
application should figure out whether it is directory or thing
or: are just things returned?
location important - currently not included, maybe query property
infer location may be a problem - see issue #2
location of things as well as browser
definition in scripting api to be alligned with discovery TF work
in sensitive context disallow multicast
Zoltan: thing discovery object - enum
better way?
return TD and not URLs pointing to TDs
skip topic semantic discovery and move it to the next call on March 2
[adjourned]