Meeting minutes
Guests
Kaz: Farshid is a guest for today
Agenda
McCool: Today's main topic is preparation for the TPAC meeting.
Farshid: can we look at some the PRs?
McCool: yes fine
… during the f2f right?
Farshid: I was asking for today
PR
PR 223
<kaz> Add object types to actions #223
McCool: seems fine, any objections?
Farshid: it is just about a TD, no ambiguity
McCool: 223 is an improvement, let's merge it
PR 225
<kaz> Add list of directory implementations #225
Farshid: it adds the 3 implementations
McCool: good news, now we
have two SPARQL implementations
… good enough to approve the spec
… any objections?
PR 226
<kaz> Add assertion list and extract script #226
Toumura: added assertion list script
McCool: seems good
… minor change not testable with Assertion Tester
to not automatically testable. Plus find which tests maybe
automatically tested
Farshid: wemight need to transform the script to a github action
Cristiano: +1
McCool: let's merge it as is and open an issue to keep track of this feature
<kaz> newly created issue - Automate assertion extraction #227
F2F slides
<kaz> F2F wiki
McCool: F2F is tomorrow
mc shows the current agenda for f2f
McCool: we need a list of
what is new
… review the state of implementation
… we need to label issues that needs to be closed
before CR
Farshid: I think mqtt should be post-pone
Andrea: geospatial queries are deferred?
McCool: yeah we have early
tests, but we lack alignments with other standards (i.e. OGC)
… we can add it as an experimental
extension.
… OGC is still a working progress
Andrea: maybe add just
a note about the possibility of doing geo-spatial queries
… if supported
McCool: about non-HTTP protocols CoAP is kind of special. .well-known might be supported out-of-box. But I am not sure to include it in this spec right now.
Christian: query live values?
McCool: we are not storing
TM
… to support live values we need
Timeseries
… is connected to Geospatial queries, cause
location is dynamic
… I agree it is a future problem
… same as Shadows/Proxies
Farshid: error
types?
… but maybe we can tackle them in this
charter
McCool: we are already aligned with a well-know error format.
mc goes on issues labelling which one should be discussed during F2F
<kaz> related issue - Reconsider @type ThingID #190
McCool: to be discussed in
the f2f
… event payload filtering deferred
<kaz> another related issue - Don't try to describe the Directory Service API in a Thing Description #172
McCool: propose closing issue 172
Remaining Issues
<kaz> Event payload filtering #176
<kaz> JSONPath and XPath response data models #156
McCool: we collected a good amount of issues to be discussed
<kaz> [adjourned]