Meeting minutes
Minutes 27 April
<kaz> Apr-27
McCool: have some suggestions for security...
Lagally: but let's not discuss on this call
Lagally: last meeting we resolved some issues and PRs
Lagally: 401 error issue we didn't really discuss...
McCool: we have discussed in discovery, can follow up there, create an issue in profiles if necessary
Lagally: did some updates on WebHook will talk about today...
McCool: any progress on explainer? even just general intro?
Lagally: not yet, but is a placeholder
Lagally: anything in the minutes to change? Can we approve?
… no objections, approve
Publication Blockers
<kaz> Issues labeled as "blocks publication"
Issue 128
<kaz> Issue 128 - Describe key use cases for Profiles
Lagally: can close "Describe Key Use Cases"
… should also look at "close" tag later...
Issue 110
<kaz> Issue 110 - Blocker for publication
Lagally: generic issue, "blocker for publication", Just an example, we can close now (#110)
Lagally: timestamps, Ben has a proposal
Issue 90
<kaz> Issue 90 - Provide example TD and declarative protocol binding illustration for Core Profile
Lagally: issue #90 is not really a blocker in my opinion, is an informative example
McCool: agree is useful, but because informative is not technically a blocker
Issue 17
<kaz> Issue 17 - Vocabulary not in TD context
Lagally: issue #17 - vocabulary
McCool: the issue is really that if there is new vocabulary, it should be in a context files
<kaz> i|can lose "D|subtopic: Issue 128|
<kaz> i|can lose "D|Issue 128 - Describe key use cases for Profiles|
McCool: one issue is that if we define new vocab, we should probably use a prefix
Lagally: have 24 blocks issues, and 18 marked as "close"
… will look at close issues myself
Issue 139
<kaz> Issue 139 - unique id
McCool: also issue #139, we have to avoid triggering a privacy review complaint, problem is the word "global"
… suggest we use uuidv4, also avoids collisions and privacy issues with metadata in ids
… and making use if uuidv4 solves a bunch of problems
Lagally: agree, better than developers doing something random
<mlagally> proposal: use uuidv4 for ids: https://
<mlagally> proposal: use uuidv4 for ids: https://
RESOLUTION: use uuidv4 for ids: https://
PRs
PR #195
<kaz> PR 195 - Example TDs for HTTP Baseline and HTTP SSE profiles
Lagally: example TD for HTTP baseline and HTTP SSE
McCool: issue with units, should probably use qudt, and I have an example in wot-testing
… it would also be nice to have an easy way to get the "renderable unit"
Lagally: will create an issue for that: issue #196
<kaz> Issue 196 - How to get a renderable unit string?
PR #194
<kaz> PR 194 - Adopting proposed language from https://github.com/w3c/wot-profile/issues/151
Lagally: adopting proposed language for 3xx errors, that we don't treat them in any special way; are HTTP protocol internal
… but adds assertions that Thing will not emit 3xx errors
McCool: suggest we merge, but raise issues if there is any reason we need to use 3xx
Lagally: also a lot of issues with id duplicates...
McCool: numbering of ids is also a pain. But please please don't change now, need to merge my PR first, then we can fix
Lagally: ok, will merge
Lagally: (merges PR #194)
PR #192
<kaz> PR 192 - Webhook HTTP profile
Lagally: this is for webhooks; not done, but a complete section now
… be aware there are some whitespace changes but can turn this off in the diff
McCool: typo, SEE should be SSE
McCool: should perhaps expand what is meant by "scalable", i.e. "can support devices that can disconnect between sending events"
Lagally: still work to do, mentioned in editor's notes
McCool: if we merge, I can fix up the assertion markup...
Lagally: ok to merge if we agree this is not the final version
McCool: I am personally fine with merging, ed notes make it clear it is not done
Sebastian: however another issue is the use of "notify", which we don't have in the TD
… would at the very least be at-risk, need implementations
McCool: markup has to be done for other issues
Lagally: I can also commit to an implementation
Sebastian: so we need one more
McCool: I know of devices I want to "describe" that do use webhooks, and that would give us a second "implementation"
Lagally: is a conflict
McCool: how about we agree you can merge after fixing the conflicts, and also the typo
<kaz> [adjourned]