Meeting minutes
Preliminary
McCool: no new guests
… or no logistics updates
PRs
PR 176
McCool: wondering if it's OK to include extra space within the contentType string
Kaz: don't think it's correct
Koster: don't think so either
McCool: merge the PR itself
(merged)
any additional PRs?
McCool: anybody still planning to provide new PRs?
… TDs will be stored at the Directory automatically
… would like to merge any valid PRs
… tomorrow, we need to use the time to check the status and wrap it up
Kaz: what about our remaining PR 165?
McCool: would visit issues first
Issues
McCool: add label of "plugfest202109"
PRs - revisited
PR 165
McCool: possible virtual device for geolocation
… manual geolocation data this time
… don't have actual ontology yet
… need to do that at some point
goes through the check points on the Issue 165
McCool: interesting validation issues
… for multi language support
… duplicated English title within the titles entry
… also about explicit readproperty op in geolocator
Ege: one of your form has writeproperty?
McCool: yeah
… the default setting may be confusing
… getting warning is useful
McCool: (briefly shows some of the files changed)
… would merge the PR
… any objections?
(merged)
McCool: (shows TDs under TD/TDs/Intel/)
McCool: what about a dynamic device?
… (shows TD for a camera)
McCool: (and then geolocator)
McCool: not actually reading the property data itself
… kind of awkward too
… don't want to give actual URI
(discussion on how to deal with the URI)
currently, the camera TD has [[ "href": "https://
McCool: guess we need a different pointing mechanism
Koster: also something to tell the format
McCool: idea here is having an ontology for geolocation information
… that's not a problem
Kaz: some kind of alias mechanism?
McCool: pointer mechanism
… to deal with how many hops to go
McCool: let's think about a vehicle moving
… devices are self-describing
Kaz: can understand the need for use cases but adding that capability to TD itself would be overkill
… that's rather a capability for handling mobile network mesh
… and IoT discovery itself
… we can create an Issue for that, though
Ege: similar issue with robot use case as well
… so this is a bigger issue
Kaz: you can create an Issue with a label of "finding", etc.
McCool: yeah
(Ege leaves)
McCool: (add comments to Issue 167)
Koster: OneDM uses fragment identifier
McCool: ok
… would like to create some more fake devices
… to handle geolocation queries
Project (2021-09 Plugfest): Geolocation #167
McCool: (shows intel-speak.td.jsonld)
McCool: what does the "accuracy" mean?
… basically the radius of 5m here
Kaz: you're thinking about 2D positioning here given just using langitude and latitude
… but possibly we could care about 3D positioning
McCool: yeah
… looked at the API within mobiles
… should talk about the geospatial guys
Kaz: also the DAS WG guys, e.g., Anssi
McCool: yeah
… maybe we might want to create a dedicated repo for this direction, e.g., wot-geo, like we did for wot-ejs
Koster: can assume GPS system?
… or various possible mechanisms too?
McCool: yeah
Kaz: if we assume the geolocation api, we can't tell the method beforehand
… the device will decide which method to get the best result
… and we can tell that based on the response from the device
… so we should think about the response from the device as well because it could include some important information about the method
McCool: right
… note here (after "position") is "altitude" which specify the 3D position
… anyway would like to continue discussion with geo guys
<McCool> https://
McCool: my idea is making that MD a separate Note
McCool: heading would be a simple version of orientation
Kaz: btw, we just have 10 more minutes
… so let's talk about projects to be checked tomorrow
McCool: right
Projects to be checked
Interop Testing (2021-09) #174
Toumura: checked the connectivity with the NHK devices
McCool: (adds that to the Issue as a comment)
… any other things expected by tomorrow?
… wondering about Philipp's RIoT OS device
Jan: some issue with network connection
… Philipp has created some tutorial, though
Kaz: thought Philipp was interested in using mobile network instead
… so we can ask him about that direction as well
Jan: can ask him about that
McCool: maybe somebody could help them set up the configuration
… e.g., TUM or Unibo?
… would be good test of tutorial instructions too
… issue noted with node-wot
… old CoAP library can't handle TD...
… if use "td+jsonld" as the MIME type
… works only with "json"
Jan: that issue has been fixed in the dev version of node-wot on my side
… only remaining issue with node-wot fetch
Tomorrow
McCool: we'll wrap up the Plugfest tomorrow
… there is a diagram of devices/apps by Toumura-san
network diagram by Toumura-san (at the bottom)
[adjourned]