Meeting minutes
minutes
<kaz> March-1
no objections. Publishing minutes.
discussions points
Kaz: some discussion related to pagination in the scripting API today
Cristiano: streaming of TDs instead of paginating
McCool: incremental loading of TDs, need to match the underlying networking protocol
Kaz: small devices may need to extract TD fragments/elements one by one, but the Scripting TF wanted to know about the detailed use case scenario before thinking about the details. that was today's discussion.
McCool: scripting API can use JSONPath to select parts of the TD
McCool: maybe JSONPath should be added as an optional feature for self-describing devices
McCool: There is PR to distinguish fragment from element
Farshid: if self-describing device cannot perform the filtering, it should reject to avoid surprise on the client side (unexpected model, size)
Cristiano: the filtering could be on a dedicated endpoint, similar to the TDD
plugfest outcome
<kaz> wot-testing issue 122 - Create Outcomes Presentation for 2021.03 Plugfest
<kaz> mm: wonders if the next plugfest is in October during TPAC
<kaz> kaz: if we don't schedule any additional meetings, yes
<kaz> ... probably we need to hold testfests to check the implementation status, though
Farshid: need to focus on closing critical issues, before implementing more
<cris> +1
McCool: we could remove less important features
McCool: pagination could be removed.
Andrea: adding pagination to ontology is not appropriate. We can try to remove them pagination from ontology and move the headers
Andrea: commented on https://
<McCool> https://
McCool: Linked Data Platform Paging is a note, not a standard
Cristiano: this means we need to rely on the protocol for pagination
Cristiano: other protocols may have their own pagination mechanism
Andrea: this is an http solution, we don't need to worry about other hypothetical protocols
McCool: need to also check if we can paginate within a TD
McCool: we have to make a decision on this, latest by March 29th
Farshid: the header-based proposal was similar. Since we need to rely on HTTP headers and spec and return a plain array, there is not much to decide.
Christian: can we support several mechanisms? Not just one?
Cristiano: shouldn't other endpoints also support pagination?
McCool: pagination annotation in TD may be useful
cancellations
McCool: no calls in the next two weeks, due to conflicts with F2F
McCool: we need to continue working on the issues and create PRs in the meantime
<McCool> https://
F2F slides
upload to https://
McCool: discovery meeting is on Mar 17th (next Wednesday)
JSONPath
McCool: need to change the reference in the draft
<McCool> update JSONpath ref to point at draft-ietf-jsonpath-jsonpath/
PR Updated ontology source code, diagrams, and spec text
https://
Andrea: Removed the id from RegistrationInfo, because if there is an id there, it would be the RegistrationInfo's ID, not the TD
McCool: the context URL need to change in future to use the w3.org domain
Kaz: the current URL is fine for the editor's draft, but what concrete URL do we want to use for the "update"?
no objections to merging
PR updates to geolocation proposal
PR Specify additional responses
https://
merged
<kaz> [adjourned]