Prev minutes

May-14

approved

May-28

approved

July-9

approved

(with the fix for "ca" to "Cristiano")

July-23

approved

ITU-T liaison

Lagally: Ilyoung is not around yet, but I've been looking at their documents

https://www.itu.int/ITU-T/recommendations/rec.aspx?rec=11699

https://www.itu.int/ITU-T/recommendations/rec.aspx?rec=12647

https://www.itu.int/ITU-T/recommendations/rec.aspx?rec=13027

https://www.itu.int/ITU-T/recommendations/rec.aspx?rec=13637

Lagally: (goes through those documents)

McCool: we should ask Gyu Myoung about how they update their documents
... for example, terminology should be aligned with our work

Lagally: yeah, would have further collaboration as well

McCool: also what "Web interface" means in their documents
... human interface?
... or including M2M interface?
... also "agent" and "broker", etc.

Y-4400 - T-REC-Y.2063-201207-I

McCool: we should look at what Mozilla does as well
... there should be some common pattern

(discussion on "Figure 8-1 – Conceptual model of the web of things" on p6)

McCool: wondering what the "agents" expose, e.g., HTTP
... also is there any entity who does registration?
... also service discovery mechanism
... may be human registers information manually

Kaz: regarding the Figure 8-1, maybe the "Web of things broker" layer is similar to our "Binding Templates"
... so we could think about that kind of similarity
... but I believe we should start with concrete use cases and requirements which are underlying

Lagally: yeah

McCool: a deep dive into Mozilla architecture might be also useful as well
... maybe we could ask Ben as well to review this document
... also (as already mentioned) wondering about the discovery mechanism

Lagally: would everybody to take a look
... also (as Kaz mentioned) use cases and requirements are very important too

McCool: Appendix I has description on "Use cases and scenarios of the web of things"
... about "Home control services using WoT"
... smart home environment
... robot thing is also interesting
... commanding for remote access
... wondering if there are other use cases in other documents

Issues and PRs

Pullrequests

PR 33

Lagally: would like to convert new proposals into HTML

McCool: wondering when to convert the new ones into HTML

Lagally: also how to deal with cross reference between vertical ones and horizontal ones

Issue 39

McCool: might want to have a dashboard for cross referencing

https://github.com/w3c/wot-usecases/pull/38

McCool: would like to have input from Jennifer

Jennifer: don't want to make the use case too narrow

McCool: we're concerned about visualization as well
... related to WebGL, etc.

Lagally: do you want to have some more offline discussion about this use case?

McCool: would have some more one-on-one discussion with Jennifer

Lagally: ok

McCool: we can add a sentence for the moment saying visualization is out of scope

PR 33

McCool: horizontal discovery use case
... discovery itself is not a vertical use case but horizontal technology

Lagally: ok
... do we need further review for this?

Jennifer: let's quickly see this

Lagally: (goes through the proposal)

changes

Jennifer: everything to be sent to a specific network?

McCool: depending on the requirements
... possibly a distributed mechanism with multiple networks
... single network is appropriate for smarthome use cases, though

Jennifer: ok
... fine with having a generic description for this

McCool: ok
... the point here is having generic distributed mechanism as well
... maybe we can add a comment on discovery service

Lagally: people may think the "service" is hosted by some device server

McCool: "discovery service" here is more abstract one
... maybe would be clearer to say "discover mechanism" here
... which possibly includes several components

Lagally: (creates a new issue for wot-architecture)
... incorporate the discovery terminology into terminology section

<mlagally> https://github.com/w3c/wot-architecture/issues/530

Lagally: what about "Variants" here?

McCool: let's not merge this yet but think about the terminology a bit more

Jennifer: thought this proposal is almost ok from my viewpoint

McCool: will go through the proposal again

Lagally: btw, we should add Jennifer to the "Reviewer(s)" section

McCool: ok

AOB?

Lagally: will remind our ITU-T colleagues of the joint discussion.

[adjourned]