Meeting minutes
Minutes
https://
<kaz> Doodle for TPAC 2021 planning
Minutes approved
Geolocation
Joint session to be held at TPAC, Christine Perey will take care
McCool: Have geo-location semantics in TD and use it in the discovery
McCool: Will also need introduction mechanism
McCool: Currently lack of implementations
McCool: Spatial extension to DNS, etc.
<McCool> https://
<kaz> (Kaz notes that we still need to clarify the actual dates for the WoT meetings, which consist of OpenDay including liaison SDOs, Breakout discussion and WoT group discussion, during TPAC.)
Christine: Liaisons wrt/ geo-fencing using standards
<cperey> https://
Spatial web working group
Christine: New IEEE P2874 Spatial Web Protocol Working Group has quite mature ideas, so let's exchange with others having mature ideas
IEEE P2874
McCool: Add P2874 to liaisons list, also OGC
<kaz> (Kaz mentions some idea about possible OpenDay topics as follows:
<kaz> [[
<kaz> * Current status of IoT services
<kaz> ** Industrial gateways (Bosch, Siemens, Fujitsu)
<kaz> ** Automotive (Volkswagen, Audi, BMW, Daimler)
<kaz> * Existing standards and deployed ecosystems (based on our liaisons)
<kaz> ** Platform Industry 4.0
<kaz> ** OPC UA
<kaz> ** ECHONET
<kaz> ** ITU-T
<kaz> ** ECLASS
<kaz> ** ISO TC 184/SC4
<kaz> * Future need for for Web-based IoT
<kaz> ** Home automation scenarios
<kaz> ** Smart Cities
<kaz> ** Retail
<kaz> ** Healthcare
<kaz> ]]
McCool: Smart cities session ... discuss in main call
<kaz> kaz: +1
Issues and PRs
PR 217
PR 217 - Add Well-Known URI and Service Name in "IANA Considerations" section
Toumura: Just editorial change
McCool: Concern about potentially long URIs
McCool: "wot-thing-description" too long?
"wot-td" instead?
McCool: Fix typo and merge
PR 218
PR 218 - HTTP HEAD method to request the content length
McCool: Profiles aims to forbid head methods, but should directories follow a profiles?
Farshid: Does not add any feature to TDD.
McCool: Supports pagination of large TDs
McCool: SHOULD or MUST feature?
Farshid: Easy to implement.
McCool: Will be changed to MUST.
HEAD possible on all endpoints (listing, search, etc.)
Yet another possbility for constrained devices to handle large TDs, fragments, etc.
PR 219
PR 219 - HTTP HEAD method to request the content length (self-description)
Farshid: Similar feature for self-description
McCool: https challenging for constrained devices, so http (not https) a MUST
PR 218 and 219 merged
McCool: "only" 81 issues left
Issue 48
https://
McCool: IDs are not guaranteed to be unique
Farshid: In JSON-LD it IS unique
McCool: Please look through issues to be discussed next time
Adjourning