Meeting minutes
Minutes
<kaz> Nov-29
Minutes from last meeting: approved
Logistics
Dec 27th, Jan 3rd cancelled: last (optional to close PRs, if not present please comment beforehand until Dec 17th) meeting this year on Dec 20th
PRs and Issues
PR 241
https://
-> terminology will only be defined in the architecture document to avoid duplicates
Merged
PR 243
https://
Some formatting and wording still to be fixed.
PR 244
https://
Challenge: How to recommend one search API if only one is specified?
"at least one" -> "a"
Kaz: it would be better to use "SHOULD" instead of "RECOMMENDED" because we usually use "SHOULD"
McCool: right. Farshid, can you fix that?
Farshid: in that case would be better to use "MAY" instead of "OPTIONAL".
McCool: yeah
XPath -> XPath 3.1
SPARQL -> SPARQL 1.1
McCool: SPARQL expression -> (URL) encoded SPARQL expression
Farshid: similar for JSONpath and Xpath
SPARQL update queries out of scope
-> SPARQL update queries have to be disallowed
Farshid: SPARQL update queries MUST NOT be supported
Check for correct http response code: 403 (forbidden)?
Will be own issue, not part of this PR
PR merged
Issues
Issue 216
<kaz> Issue 216: Define role of "Discoverer/Registerer"
<kaz> WoT Architecture 1.1 draft: 3. Terminology
<FarshidT> Discoverer: An entity that generates and registers a TD with an exploration service on behalf of a Thing which may not be able to do it for itself.
Christian: just checked with Apache Jena and update on the /query endpoint results in http 400 (bad request)
See comments in issue
Farshid: definitions do not sound straightforward
McCool: maybe "generator" which produces and stores TD
<McCool_> https://
<kaz> [adjourned]