Meeting minutes
Guests?
none
Minutes
(Sebastian goes through the minutes)
McCool: note there will be many restrictions for TPAC 2022
… should have more discussion later
Sebastian: ok
… minutes themselves look good
McCool: no issue to me either
(approved)
IEEE P2874
McCool: joined the meeting on June 1
Sebastian: (shows the slides)
McCool: we need to think about geospatial discovery
… and also how to deal with geospatial data
… another meeting proposed with OGC as well
… related to time series data
Ege: I'm also interested
OGC TC Meeting
McCool: invited by Linda and Christine from the Spatial Data on the Web WG
… will be held on June 15
… but the time is very early at my place
… another option is June 23 during their WG meeting instead
… McCool will present summary and propose a joint call during TPAC 2022
… for me June 23 would be much more convenient
… let's follow up with the email from Linda and Christine
Sebastian: ok
Cancellations
Cancellations and Schedule Updates
Sebastian: TD call today depends on the resolution for the WD publication
… next week, I myself will not be available
… but Ege can moderate it
Ege: yes
<Zakim> dape, you wanted to remove outdated cancellation entries
dp: suggest we remove the old entries
Sebastian: DTDL discussion on June 21
McCool: same time for the use cases/editors call
… will send an explicit calendar invite to make sure
TPAC
Sebastian: TPAC page is available now
McCool: last week Kaz mentioned the time zones varies much
… and difficult to find a good slot for all the remote participants from various time zones
… if the fee is per day, would make sense to have a meeting on a specific day
… physical meeting would be useful for collaboration
… also demos
… normally we have 15 hours for our (v)f2f meetings
… but difficult to find good times for Asia, Europe and Vancouver
… need to identify the slot carefully
… potentially, we could hold a follow-up vF2F meeting after TPAC
dp: keeping it one day is fine
… but the fee is per day?
McCool: seems it's per event...
(per person event fees)
McCool: joint meeting with Spatial group would make sense
Sebastian: OK with having only joint meetings within one day and having detailed group discussions during the following week
Ege: a bit confused
… can understand the time restriction, but do we need to have our meeting during the restricted time?
McCool: the question is the time difference with the various areas
… Vancouver, Europe and Asia
… Vancouver time is PDT
… so there are just limited choices
Ege: will we have official joint meetings between WoT-IG/WG and other groups?
… or each individual will visit their own interested groups?
McCool: people can't attend due to various reasons including their companies' policies
… the main point is it's not feasible to find good slots
dp: you can still have a whole-day meeting if the agenda is stable
… people can just choose their interested sessions
… even some of them are held at difficult times
Ege: we can pick a bit earlier slots, etc., if needed
McCool: need to see which slots are feasible
Kaz: agree with McCool
… so we should identify which discussion would need physical participation
… and which can be handled by remote discussion
Ege: think all the possible topics can be handled by remote discussion
… what is important is the "f2f feeling"
… Charter discussion for 1.1 period in Munich was complicated, though
Kaz: right
… so we should get a rough sketch of the agenda items
… and see which part to be handled how
Publications
Sebastian: any updates on wide reviews?
McCool: we need to add "need review" GitHub labels
… for example, TD issue 1497 has "privacy-needs-resolution" label
wot-thing-description Issue 1497 - Identifiers don't seem to rotate enough
Sebastian: anything to be added?
McCool: still waiting for responses
Sebastian: what about Discovery?
McCool: only issue is HTTP vs CoAP
… currently, the Explainer highlights HTTP only
McCool: CoAP would be nice for small devices
Ege: don't think we should add CoAP from now
McCool: that's my impression too
Sebastian: why don't we add a simple note to section 7.2 saying "CoAP can do similarly" or something like that
McCool: could do that but it's too late and may cause an additional error
Kaz: I'm OK with not adding CoAP at this stage
… but the Discovery Explainer doesn't have a link to the Discovery draft though it includes links for TD and Architecture
McCool: good catch
… will add a link
Kaz: tx
TD updated WD
Sebastian: would ask a resolution for publication
… got comments from Daniel about ReSpec errors
wot-thing-description Issue 1520 - ReSpec Error - Reference "[ACE-OAuth]" not found
Sebastian: also some more issues
wot-thing-description Issue 1523 - Missing RFC-2119 Keywords in Assertions
Sebastian: also i18n
wot-thing-description Issue 1516 - Limiting the length of strings
dp: related PR there
wot-thing-description PR 1526 - refactor: makes clear what the length of a string is based on
McCool: OK with following what JSONSchema does
Sebastian: let's merge PR 1526 then
(merged)
Kaz: this is a publication for an updated CR
… so let's move forward!
… let's make a resolution for that now :)
<dape> DP: w.r.t. string length, RFC8529 says "A string is a sequence of zero or more Unicode characters [UNICODE]."
<sebastian> proposal: the editors draft in the main branch on the TD repo will be published as new WD and will be seen as the TD 1.1 CR candidate.
RESOLUTION: the editors draft in the main branch on the TD repo will be published as new WD and will be seen as the TD 1.1 CR candidate.
McCool: Discovery also expected to make resolution next week
… might be delayed a bit
Charter
AC Review for the WoT WG Charter
Sebastian: please ask your AC Reps to support the Charter!
… still need 12 more supports to get 20 supports
Testing
McCool: latest test results have been checked in
… (shows the latest rendered results on his PC)
Kaz: if you could set up the github pages setting, maybe we could directly see the rendered HTML
McCool: let's talk about that offline
Ege: have created a new PR for instruction updates
wot-testing PR 331 - Add further testfest instructions
McCool: we need input data from implementers
… manual.csv is the template for your input
Kaz: just to make sure, not "template.csv" but "manual.csv"
… right?
McCool: yes
Sebastian: TDs and TMs are also welcome
Kaz: and we'll continue the testing discussion tomorrow and Friday
McCool: yes
… and I and Fady will also have some discussion right now
TD call
Kaz: just to make sure, there sill be no TD call given we've already make a resolution for publication. right?
McCool: right
… will send an updated calendar invite for cancellation
Kaz: tx
[adjourned]