<scribe> scribenick: kaz
Lagally: conversation during/after the
vF2F
... got resolution for the FPWD publication
(no objections)
Lagally: approved
transition request for WoT Architecture 1.1
Lagally: approved and no blocking issue for FPWD
Kaz: right
<mlagally_> https://github.com/w3c/wot-architecture/releases
<mlagally_> https://github.com/w3c/wot-architecture/releases/tag/FPWD-1.1
Lagally: created release tag as above
Kaz: ok
... will check the document with checkers for publication
Lagally: btw, you mentioned a comment within the transition request?
Kaz: yes
transition request for WoT Profile
Kaz: no comment from Philippe but
just approved :)
... but I myself added a note that it would have been better to
use "Web of Things (WoT) Profile" as the title of the
document
Lagally: let's go for it :)
... (creates a PR)
Kaz: ah, I thought I had already created a PR :)
Lagally: let's merge that then
... (and merged it)
Lagally: (visits the wot-usecases
repo)
... during the Use Cases call today, we talked about two new
use cases
Lagally: one of the two is about VR/AR use cases
<inserted> Irrigation in outdoor environment use case
<inserted> ml: and another is on agriculture
Lagally: (explains the use case)
... we need to indicate a way for accuracy
Sebastian: we have to clarify the
data
... metadata on the interaction level
Lagally: get temperature and return results
Kaz: btw, I misunderstood this
proposal was generated by Lionel from Lyon U because he made
the Pullrequest
... but it seems the original proposers are not Lionel
himself
... so this proposal is related to the discussion we started
yesterday about how to deal with proposals/contributions from
non-Members
... I'll check with Lionel as well
Lagally: ok
... need further discussion during the main call too
... (goes into the detailed description)
Lagally: this is about VR/AR use
cases
... expected devices include VR goggle and 3D camera
... how to deal with the streaming data is important
... can use the VR headset to browse the resources
... how should we move forward with accuracy and reliability of
the data?
Sebastian: we should create an issue and have discussion during the TD calls
Lagally: ok
... should discuss additional metadata, etc.?
Sebastian: yeah, introducing new terms
would not be harmful
... on the other hand, we should be careful about how to deal
with the requirements
... need elaborate what is really needed
Lagally: ok
... some of the new use cases would explain the validity of new
features
... will create an issue for the disscusion
wot-architecture repo - REQUIREMENTS area
Lagally: we have several requirements
descriptions
... agriculture, discovery, geolocation, ...
... link relation types
... requirements from the new WG Charter
... Thing Model
Sebastian: we've introduced a new concept for Thing Model
Lagally: yeah
Sebastian: what is the meaning behind the "link" here?
Lagally: we had some discussion
yesterday (during the TD call)
... link relation types to be archived at IANA
... included related standards here
[[
Web Linking: https://tools.ietf.org/html/rfc8288
Link Relation Types for Web Services: https://tools.ietf.org/html/rfc8631
Additional Link Relation Types: https://tools.ietf.org/html/rfc6903
https://tools.ietf.org/html/rfc5988
Link Relation Types - IANA registry: https://www.iana.org/assignments/link-relations/link-relations.xhtml
]]
Sebastian: there are 2 examples here. right?
wot-thing-description Issue 999
Lagally: example of Oracle's device model above (Issue 999)
Sebastian: what is the relationship?
Lagally: (goes through the example codes)
Sebastian: how to handle the device components?
Lagally: think the recommended way should be embedding the models into the Thing Description
Sebastian: ok
... would like to continue the discussion on Thing Model during
the TD call next Wednesday
Lagally: any other business for today?
(none)
[adjourned]