Meeting minutes
Minutes
approved
Profile
PR 287
PR 287 - Consolidate date-time references to RFC 3339 - closes #276
ml: would merge this
(merged)
rrsaget, draft minutes
PR 315
PR 315 - Improve link assertions
ml: need to discuss Issue 255 as well before merging this
Issue 255 - Remove or re-work section 6.1.2 Links
PR 317
PR 317 - Fix respec reference error
ml: just an editorial fix
(merged)
PR 318
PR 318 - Converting from ednote to note
diff - 7.2.1.4 writemultipleproperties
ml: want to discuss this next time
PR 319
PR 319 - Describe how Webhooks are used in the WoT context
kaz: Webhooks itself is not really popular within the WoT context even though it's quite popular for Web developers in general
… so we should have some more description about Webhooks and who handles the Webhooks mechanism within the WoT context as a component of the WoT-based system in addition to mentioning that the Consumer should be an HTTP server
ml: that's true
… (creates a new Issue on that point)
<mlagally> Issue 322 - Brief section to explain Webhook-based Consumers
Section 6
kaz: the current title is "6. Common Constraints" but I think it describes basic requirements for the HTTP Basic Profile
… so would be better to say "6. Requirements"
… also listing Accessibility, Units, Date Format, Security, etc., at the same level is a bit odd
… so would be better to have two bigger categories, one for wider viewpoints like Accessibility and Security; another for smaller points like Units
PR 321
PR 321 - Removing mention of plugfest experience
kaz: we need Ege for this PR
… but we can remember what we meant by the sentence about the Plugfests
… many of the features for WoT Profile are defined by the other normative WoT specs
… so have been tested during the Plugfests and Testfests
… that's what we meant
… let's explain that point again
[adjourned]