Meeting minutes
<benfrancis> mlagally: We can hear each other but not you
Michael L, we can hear you and each other
Agenda
McCool: suggest put review of TPAC agenda under other business
minutes review 08-01
<mlagally_> https://
Lagally: mentioned some slides uploaded last time for profile next steps
Lagally: we discussed various options for moving forward
Lagally: any corrections to the minutes?
Lagally: ege's pref for option A is missing, should be added
Kaz: recorded elsewhere
Lagally: ok, let's leave the minutes alone, then. Approved?
Lagally: ... hearing no objections, approved
schedule for combined call Arch/Profile
<kaz> doodle results
Lagally: looks like the current time is still the best option, so we will stick with it
contributions
Lagally: there are 10 PRs, will work from oldest to most recent
PR 251
<kaz> PR 251 - Remove cloud events as message format for WebHooks, update README.md (#248)
Lagally: removing cloud events, had IPR issues due to charter update
Lagally: some issues with Base profile vs. core
McCool: should use "HTTP Baseline Profile" as already agreed
Lagally: this PR also removed the JSON object format
Ben: this PR was supposed to be about removing cloud events
… it seems there are some other unrelated changes... would suggest removing unrelated renaming commits
… deal with that separately
Lagally: agree, revert changes in this PR for README, then merge
PR 256
<kaz> PR 256 - Add titles to action input examples - closes #216
Lagally: closes 216
… I reviewed, looks good, suggest merging.
… (no objections)
PR 257
<kaz> PR 257 - Assert that the profiling mechanism depends on TD v1.1 - closes #217
Lagally: was reviewed, has been around for a while, ege has approved
Ben: so there were a number of force-pushes here to resolve conflicts
… but it looks like there are still conflicts
Lagally: looks like a conflict in an example... white space issues?
Ben: will try to resolve conflicts offline
Lagally: has been approved, will trust ben to fix it; let's agree to merge after he fixes issues
Lagally: (no objections)
PR 260
<kaz> PR 260 - Re-structure profiles sections - closes #214 and closes #248
Lagally: closes 214 and 248
Lagally: diff is not helpful
Ben: this is tiding up after splitting up the profile; there were some bits that were common to all three; moved to common constraints
… moved default language and security constraints to the top of this new section
… moved information model section and http section to common constraints
… also two security sections, merged
… moved security and privacy considerations to top-level sections as required for review
… and then a bunch of renaming of ids
Ben: sounds like a big change and a lot of shuffling
McCool: suggest creating an issue to remove reference to Security Best Practices; merging with Guidelines document
McCool: probably also need to review the considerations sections; for now are minimal; can review in security TF
Lagally: so this refactoring is useful, suggest merging
Lagally: any objections? none -> merging
Pr 262
<kaz> PR 262 - Refine assertions around 3xx redirect responses - closes #246
Lagally: refine assertions about 3xx status codes
… but some cases where 3xx codes are used, e.g. OAuth
… but excluded some cases, e.g. Multiple Choices
Ben: there is on ambiguous redirection, 300, which suggest disallowing
Lagally: suggest merging
Ben: but last PR has created merge conflicts
Lagally: assuming merge conflicts are fixed, will merge later
PR 263
<kaz> PR 263 - Add missing form for observeallproperties and unobserveallproperties #263
Lagally: missing form for observeallproperties and unobserveallproperties
… in protocol binding section
Ben: is in example TD
… is adding unobserveproperties to top-level form
… and this is only for sse
Lagally: any objections to merging?
… hearing none, merging
PR #264
<kaz> PR 264 - Add geolocation semantic annotation recommendation - closes #137
Lagally: adds geolocation semantic annotation recommendation
Ben: this may need rebasing to make sense
Lagally: numbers without units
Lagally: but schema.org does say if no unit given is m, perhaps we insist on that
McCool: in general, think geolocation should be in its own profile, even if it is small
… since there are many other ways to do it, and baking this one way into common constraints seems premature
… but for now I am ok with merging as long as we add an issue to discuss it later
Lagally: add issues 264
Lagally: back to unit of measurement, allows unit of measurement to be specified
McCool: agree with insisting on m and not allowing other units, if only because specifying units is complicated
Ben: this is what we do in webthings, use only SI, then translating into other units as localization
McCool: I think we just add an informative note that "Since this is a number only, the units are assumed to be m."
Kaz: Agree to add that kind of note. Please remember we also have been talking a lot with SDW about how to do. So we need to think about how to deal with geolocation information in near future, though citing schema.org if a good starting point.
McCool: really don't feel comfortable putting it under common constraints for now
Ben: feel we are pulling on the thread of a much bigger issue with this geolocation information
<kaz> [adjourned]