Meeting minutes
Minutes
deferred
New inputs
PR 563
PR 563 - Update Intel Web Speak with JSON Pointers for sec body
McCool: (adds comments)
McCool: would like to resolve the four prioritized features
(1) sec-body-name-json-pointer - Intel (1) sec-body-name-json-pointer-creatable - Intel (1) sec-body-name-json-pointer-array - Intel (1) sec-body-name-json-pointer-type - Intel
<McCool> w3c/
McCool: (skims the changes for PR 563)
McCool: looked into the API Keys, etc.
… (refers to the RFC 6901 (JSON Pointer) spec)
McCool: think I'm correct
… Ege, do you agree?
Ege: yeah
… I misunderstood something
McCool: fixed example would be helpful
… actual payload has two items in my case
… helpful to have some description
… wondering what the expected array usage is like
… a bit confusing
Ege: actual intention of two strings or one string?
McCool: I mean two elements
… need to define what the spec means
… anyway it's confusing
… Ege to fix the Playground
… and then I need to re-run the test tool
Kaz: please give clarification
… so the problem here is a bug within the Playground tool?
… no impact with the spec or the examples?
McCool: it's a bug of Playground tool
… no impact with the spec at all
Kaz: any impact for the test results?
McCool: Ege's results are wrong
Kaz: meaning all the results processed by Playground?
McCool: right
Kaz: need to regenerate all the results for TD, Architecture and Discovery?
McCool: for TD
… regarding this PR itself, OK to merge it?
Kaz: this PR itself is not for Playground but Intel's new test results
McCool: right
… would wait for the fix for Playground, though
Kaz: In that case, let's fix the bug first right away, then move ahead for another PR.
<Ege> thingweb/
Kaz: would suggest we once fix the Playground, then check the result for one PR, then try the next PR
McCool: however, running the test result generation would take long, so would like to merge PR 563 and PR 564 at once
Kaz: that's not ideal, but for today, I can live with that
(PR 563 merged)
PR 564
PR 564 - Update wot experimental TD for apikey in body #564
(also merged)
Kaz: just to make sure, Playground has been also fixed on another repository. right?
McCool: yes
… (then regenerate the test results)
… just to make sure, any other PRs updating TDs?
… found PR 562
PR 562
PR 562 - Updated TDs from latest master branch of WebThings Gateway
McCool: seems to be using wrong suffix
… would merge this PR once the data is fixed
… also the batchValidation script has not been updated
… I'll check that
(regenerating the result for TD without merging PR 562)
McCool: it takes 10 mins or so to get the results
… meanwhile, let's work on the other PRs
PR 559
PR 559 - Updated WoT Profile implementation report for WebThings Gateway
McCool: some problems with Consumers
Ege: we had discussion within the CG
… it could be a Consumer from my personal viewpoint
<cris_> +1 for it to be considered as consumer
McCool: Profile is not a critical path
Kaz: we used to use the term, "Servient", which includes both Consumer and Thing
… so a Gateway could be considered as a Consumer
ck k
McCool: (adds comments)
For the TD deliverable, we do not have many at-risk assertions left so it's not critical to push the definition of "Consumer". Profiles will be dealt with in the next charter so it is also no critical. So I think we can merge these TDs for now without the Consumer assertions.
(merged)
PR 560
PR 560 - Fix Size2 result for RIOT implementation
(merged)
PR 561
PR 561 - WoT Profile implementation report for Krellian Cloud
McCool: wondering about the comments
… but ok to merge it
(merged)
PR 562 (revisited)
PR 562 - Updated TDs from latest master branch of WebThings Gateway
McCool: need to wait until the data is fixed
Regenerated results for TD
Kaz: have we got the updated HTML?
McCool: still need to push the results to the wot-testing repo
… (pushing the results)
… (creates a new PR for wot-testing repo)
PR 565 - New Testing Results for TD
McCool: wondering about deletion around line 404
Files changes - oracle-wt.csv line 404
Ege: think moved to automatic
(PR 565 merged)
McCool: need to update the Implementation on wot-thing-description repo too
Implementation report for TD 1.1 to be updated
McCool: (sees the atrisk.csv at wot-thing-description/testing)
wot-thing-description/testing/atrisk.csv
McCool: all the four high-priority features for TD are addressed now
Next steps
Kaz: we're getting out of time
… how to proceed?
McCool: still need to update the results
… also will update the test result page
Kaz: how to deal with them by when?
McCool: we've extended the deadline as May 17
Kaz: do you mean you want to continue to work on the data update by May 17
… and see the updated results for all the 3 specs on May 17?
McCool: would like to work on the data until at least May 10
… and see the final results on May 17
Kaz: do you mean the goal for that purpose should be all the features at risk listed on the results page above?
McCool: yeah, at least all the priority features
Kaz: could you make an intermediate report around May 10?
… then think about how to proceed at that time
… then if needed, we can continue to work on the remaining features by May 17
… then see the final results on May 17
[adjourned]