– DRAFT –
WoT Architecture

minutes

<kaz> May-12

approved

schedule

ml: next week this date is father's day in germany

mm: so why don't we use the use case call slot?

ml: works for me

ml: two hours?

ml: will send out a doodle

kaz: starting at use case starting slot, then going for two hours?

mm: how about this time we just do one hour, then see if we can extend if people can clear their schedules

kaz: too many two-hour calls is tiring
… but in the short term, given the schedule, maybe

contributions

ml: we'll look at the schedule later

PR 737

<kaz> PR 737 - Align binding related information

ml: binding info - need Ege

PR 754

<kaz> PR 754 - terminology for orchestration

ml: definition of orchestration
… using some language suggested by mm

ml: can we merge?

mm: sure

ml: merging

PR 760

<kaz> PR 760 - changing section level for MediaTypes

ml: section levels for media types; resolves an issue, 675
… move it to a higher level so it is not buried

ml: does not change content, just moves a section close tag, moves media type one level up
… editorial

mm: concur can be merged

ml: merged

kaz: as I mentioned the other day, I still think it's a bit odd to have "Media Types" as a separate subsection within the section 6 which describes the concept of the WoT Architcture.

mm: would suggest we create a new issue for that point.

kaz: ok

PR 761

PR 761 - replacing placeholder for virtual thing with content

ml: description of virtual things in Ch 6
… should replace an ednote
… although I see the ed note is still there... hmm. let me quickly delete it
… done

mm: let's review the text

mm: suggest we mention "service" to align with the current definition

ml: ok

ml: can be merge?

mm: fine with me

ml: merging

PR 762

<kaz> PR 762 - changing table style

ml: table style for device categories
… using "def" table style, consistent with others

mm: ok

ml: merging

Issues

ml: have been tagging things I think we can close, and propose close
… close means I don't think we need a long discussion
… I also closed some that had clearly been addressed

issue 736

<kaz> Issue 736 - What does form context mean?

ml: ege asked what "form context" is; we don't define that

ml: is clearly defined in CoRAL, which is cited

mm: I think the only real issue is that the text is not 100% clear that the defn comes from CoRAL

ml: ok, let's change that then

mm: suggest adding "In CoRAL" to the start of the list

ml: done; then we can close the issue

Issue 715

<kaz> Issue 715 - Verify note on TD Fragment

ml: verify note on TD fragment

mm: would be ok with just deleting the note, the defn itself is ok

ml: ok, let's do that

ml: (deletes note after TD fragment)

Issue 681

<kaz> Issue 681 - Review architecture document consistency

ml: document consistency checked

ege: not ready to close

mm: depends on other issues, we should list them all, then close this issue when they are resolved

ml: ok, let's collect the issues that this one depends on

<kaz> Issue 634 - arch-thing-bundling : Things MAY be bundled together with a Consumer to enable Thing-to-Thing interaction.

<kaz> Issue 635 - arch-id-correlation : An identifier in the WoT Thing Description MUST allow for the correlation of multiple TDs representing the same original Thing or ultimately unique physical entity.

ege: issue 634, 635

<kaz> Issue 625 - Assertion review

ege: there is also issue 625, which is an assertion review, some are not dealt with yet

<kaz> Issue 646 - [Index] Section structure, assertions, and issues

ege: also a closed issue 646, just reopened

mm: 625 mentions two assertions that we have separate issues for, so is redundant now, let's close

<kaz> PR 737 - Align binding related information

ege: also PR 737

ml: and issue 646

kaz: we could have a master issue list, or we could use labels (or both)

ml: will make a checkbox list for now

mm: regarding 625, I think we should just remove that assertion, it conflicts with privacy, use of uuidv4 in profiles, and there is no mechanism supporting it in TD

ml: ok, will assign you then

ml: ok, regarding "things MAY be bundled" -> has been resolved already

PR 734 (revisited)

<kaz> PR 737 - Align binding related information

ege: won't have time to update

mm: if we leave it out, will it cause a big problem?

ege: no, and I can also make a simple PR to deal with the things that were deleted

WD

mm: don't necessarily need to call it a CR candidate, but we should publish a WD update at least

proposal: resolution to publish a WD update based on the current editor's draft

proposal: resolution to publish a WD update based on the current editor's draft using branch architecture-1.1-pre-cr-wd

<mlagally_> https://github.com/w3c/wot-architecture/tree/architecture-1.1-pre-cr-wd

proposal: publish a WD update based on the current editor's draft using branch architecture-1.1-pre-cr-wd one week from today

RESOLUTION: publish a WD update based on the current editor's draft using branch architecture-1.1-pre-cr-wd one week from today

AOB?

<Ege> https://github.com/w3c/wot-architecture/pull/767

ege: 767 replaces 737, just deletes assertions

<kaz> [adjourned]