Meeting minutes
minutes
minutes of 6-30
<kaz> June-30
Lagally: reviewed schedule, PRs, static HTML version, agreed to work on issue #766 offline (will check if was done)
Lagally: any objections to publish?
Lagally: no, publishing
contributions
PR #786
<kaz> PR 786 - Cleanup - archiving USE CASES and REQUIREMENTS
Lagally: cleanup of use cases and requirements in repo, move into archive
… moved these over to use cases repo a long time ago
PR 787
<kaz> PR 787 - Text improvements to Introduction and Terminology
Lagally: improvement to intro and terminlogy
McCool: ok in general, but "large" and "powerful" descriptions of classes may be off by an order of magnitude
Lagally: suggest we merge and then file an issue
McCool: one solution is to add an extra class at the end, shift the descriptions down one, and introduce a "medium" edge server.
Lagally: creates issue #801
<kaz> Issue 801 - Device Categories: Add Class 7, improve "typical application scenarios"
PR 788
<kaz> PR 788 - Editorial fixes for section 4 + 5
Lagally: editorial fixes to section 4 and 5
Lagally: using "scenario" rather than "use case" in some places
McCool: wonder about whether we need this much detail here given that we have a use case document
Lagally: is helpful for people reviewing to get the context
McCool: ok as long as we emphasize there is a much larger document, and this just a summary
seb: use case document has much more detail, this is more compact, which is useful
… people can get an impression of what domains are being addressed
Lagally: as for actual changes, referenced a particular class
McCool: we should be careful about making a 1:1 mapping between Things and devices, not the same. but ok
Lagally: also cloud-ready to cloud connected
Kaz: going back to use case discussion: for moment, can add some more links to use case document to section
McCool: for example, linking to particular sections in use case document
<Mizushima> +1 kaz
Lagally: also adding a single link at least from the introduction should be done
Lagally: creates issue 802
<kaz> Issue 802 - Add a link to use cases document to section 4
McCool: wonder if we should have a terminology definition? It depends on how much we use it.
Toumura: note that section title is deployment pattern, perhaps we should use that instead of "deployment scenario"?
… your pull request changes several terms from "use case" to "scenario", but perhaps "deployment pattern" would be more consistent?
Lagally: we could also delete "common"
McCool: common is meant to imply these are high-probability patterns, there might be others
Kaz: can toumura type in irc?
Lagally: or an issue, given audio issues?
Lagally: creates issue to "Consistently use deployment pattern" as issue #803
Lagally: can we merge?
McCool: ok with merging
Lagally: any other comments?
Lagally: no more comments, merging
PR #789
<kaz> PR 789 - Editorial fixes to chapter 6
Lagally: Editorial fixes to Ch 6
McCool: the use of "kinds" instead of "possibilities" is not quite right, but the other changes look ok
McCool: suggest merging, and then I can do a post-merge review and English fixup
Lagally: ok, merging
PR #790
Lagally: updates to chapter 7
McCool: suggest we review the editorial PRs offline, and deal with logisitics
Pr #793
Lagally: cleaning up editors and past editors, and cleaning up acks
McCool: thanks, also good that added Matthias and Kaz
TAG feedback
<kaz> Issue 797 - https://github.com/w3c/wot-architecture/issues/797 Issue 797 - Architecture (TAG) Review
Lagally: a lot of feedback, asking if we should split things up into multiple issues
McCool: agree to let them split it up
McCool: any show-stoppers?
Lagally: have not had a chance to read through it all
Lagally: don't have time to discuss now, let's revisit this next time
PR 780
<kaz> PR 780 - Generate static HTML file for WD publication (for CR candidate)
Lagally: regarding WD, do we include recent updates?
McCool: I think we should just push out the version we already had in flight
<mlagally> proposal: publish the version from https://
RESOLUTION: publish the version from https://
Kaz: just to make sure, let's check the HTML diff with the latest Editor's draft before publishing
[adjourned]