Introduction of each plugfest demo

louay: discovery using UPnP

kajimoto: no demo this time

dsr: proxy for discovery

michael: doing REST-based proxy

dsr: the other thing to do is slides for tomorrow

johannes: same thing as the previous demo
... UI to interact with TD
... several things on servients
... how to model things
... how to handle the processes
... some lifecycle method
... and how to interlink things
... thinking about having resources
... would investigate patterns

michael: collection of patterns?

johannes: yes
... also collection of multiple, e.g., 64, LEDs

daniel: @@@

taki: no demo

victor: TD Repository:
... http://vs0.inf.ethz.ch:8080
... coap://vs0.inf.ethz.ch:5687

louay: shows FlowsAndBindings.md
... https://github.com/w3c/wot/blob/master/TF-DI/DiscoveryFlowsAndBindings.md
... several possible discovery flows
... discovery flow 1, 2, 3, 4, 5
... myself use flow 3
... flow 4 looks up endpoints
... flow 5 has TD generator
... there could be more patterns
... next how to bind concrete protocols
... the first is SSDP binding
... difine new SSDP device type
... Thing provider (server) advertises some specific SSDP message

s/message/messages when things appear/disappear

scribe: mDNS proposed by Dave

dsr: mDNS sends query using UDP
... binary data
... and links for early records
... "A" record for IPv4 address
... "AAAA" record for IPv6 address

johannes: do we have any starting points for documentation?

dsr: no, not yet

johannes: need to think about broadcasting?

dsr: mDNS is build on DNS

johannes: would be handy if we could document concrete examples
... the question is we need guidance for developers

louay: this .md file is the basis of the possible guideline
... https://github.com/fraunhoferfokus/wot-cli
... setup: install Node.js, clone the repository, install dependencies
... usage: wot [options] [command]
... wot discover
... wot advertise

sebastian: work for local network?

louay: yes
... and we'll discover all the things within the local network
... possible to use QUERY to search specific Things

daniel: @@d

louay: what you're asking is rather similar to the discovery flow 4
... advertise(Lookup-Endpoint)

daniel: would get same results regardless of the protocols

louay: would start with SSDP binding
... shows "TD.WOT.W3C.ORG: URL to Thing Description"

dsr: how about multicast?

sebstian: another question
... always announce Thing Description?
... how Bonjour and mDNS work

daniel: UPnP is gone, isn't it?

matthias: implementations for various OSs?

dsr: mDNS is quite simple

louay: s/SSDP/SSDP/

s|s/mDNS/SSDP/|there are libraries|

scribe: TVs use UPnP for discovery with DLNA

dsr: quick introduction for mDNS
... UDP and multicast
... IANA repository for service name
... shows Bonjour Browser
... can use a command line tool, dns-sd
... give service name using -R option
... shows /dev/cu.wchusbserial1420 log
... default network arrangement
... shows Transport.cpp
... log again
... easy to advertise endpoints

michael: diagram with 2 stages
... how about implementations?

dsr: there are many implementations

louay: registration is not part of work currently
... do we really need "RN:"?

dsr: need to specify which protocol(s) the endpoint can talk
... devices may sleep

daniel: also network traffic issue

sebastian: would see interaction with SSDP as well

(discussion on multiple protocols)

louay: important to specify USN (unique service name), e.g., advertisement UUID
... specify both service name and protocol
... wot search command has -p option to specify proptocols
... currently supports only ssdp and mdns, though

joerg: do we think it would be relevant for the next plugfest?
... who are interested?

louay: would make sense to have multiple gateways for different protocols

joerg: asking because we need to be clear what is expected for plugfest
... wondering how to deal with the categories
... we need to agree with what to do
... and decide who to do what

dsr: what kind of network to be used
... secure or not

johannes: for Nice meeting, eventually somebody brought a router and everybody used that

dsr: we can prepare what is needed
... July meeting will be held at some hotel?

johannes: if we can prepare beforehand, it would be better
... would be better to get prepared before we fly

louay: shows description.jsonld
... and scpd.xml
... and shows a demo which plays a video
... and show Node-RED diagram

johannes: relationship between Node-RED and TD?

louay: added thing as a node

johannes: how to translate UPnP to actions?

louay: if you want to use TD directly you can use URI and actions

johannes: you have same issues on actions vs properties

(Node-RED is useful to express the bindings between multiple protocols)

louay: we can start with concrete Thing Description which is tied to some device
... or we can start with "discover things"
... connect multiple things using Node-RED tool

kaz: here "thing" node is a wot servient as TD processor rather than concrete device. right

louay: right

[ adjourned ]