<kaz> scribenick: kaz
Lagally: (goes through the agenda for
today)
... logistics and roadmap
... use case document, prioritization, IG work,
requirements
Lagally: have I uploaded the slides?
Kaz: maybe not?
Lagally: available at the URL above
Kaz: will add it to the minutes then
Lagally: ok to approve the minutes with the addition?
(no objections)
Lagally: approved
Lagally: lifecycle and use cases
... the plan is finalizing the lifecycle discussion by the
virtual meeting
... also prioritizing the UC
Lagally: T2T workshop on June 8
... then PlugFest and F2F
(PlugFest on June 15-19; F2F on Jun 22-26)
scribe: update, lifecycle, discovery, PoCs, CHIP, ODM, IRTF WS
Matsukura: couldn't join the recent
lifecycle discussions
... what's the main point?
... lifecycle of what?
Lagally: device lifecycle
<mlagally_> https://github.com/w3c/wot-architecture/blob/master/proposals/unified%20device%20lifecycle.svg
<mlagally_> https://github.com/w3c/wot-architecture/blob/master/proposals/lifecycle-model-proposal-zolkis.md
Lagally: Zoltan should upload his updated diagram
<scribe> ACTION: zkis to upload his updated diagram to the GH repo
Kaz: in short, we've been
discussing the lifecycle of WoT-based service in general
... Elena gave a diagram from WoT security viewpoint
... Lagally gave a diagram from a bit different viewpoint
including device and data transfer
... Zoltan also gave a diagram from another viewpoint including
the 3-layer model of device, network and application
Elena's diagram (lifecycle diagram-WoT new lifecycle.svg)
Lagally's diagram (device lifecycle.svg)
Zoltan's diagram (Google account required)
Lagally: right
... (shows his own generated diagram)
Matsukura: which part is in the scope of
WoT?
... onboarding is already done by the other SDOs
Kaz: the application layer in Zoltan's diagram is the main target of WoT, I think
Lagally: we need to have clear
terminology definition as well
... (then updated the "F2F Topics" section)
F2F Topics section from the online f2f meeting wiki
Lagally: use case prioritization -
2h
... profiles - 2h
... requirements - 1h
... lifecycle - 2h
... so 7 hours for architecture topics
Lagally: this wiki page is getting
bigger
... not sure how to improve it, though
Kaz: we can create a separate
"previous" page
... might be better to have ones based on the year,
though
... e.g., "2019", "2018" and "2017"
Lagally: ok
Lagally: an issue for update from NHK
Lagally: need a pullrequest
Kaz: they would like to generate a pullrequest but not for the WG repo but an IG repo
Lagally: ok
Lagally: adding profile use case
... (goes through the description)
... TD is an extremely descriptive format
... but need common ground on how to understand it
... would like to present this proposal during the call 2
too
Kaz: as you already mentioned, the title of this proposal should be something descriptive rather thant "need for wot profile"
Lagally: right
... (and add a proposed title, e.g., "Out of the box
interoperability")
Lagally: update for retail with
security and privacy considerations
... OK with merging this proposal but would talk about this
during call 2 as well
Lagally: medical device use case from
Taki
... think this is a good use case
... note that there should be many existing standards for
medical purposes
... (Lagally gave comments like "adding references would b
useful")
... might want to think about some kind of semantic tags
... we already have units but don't have mechanism for this
kind of interaction for medical purposes
... my plan is merging this but would discuss this during the
call 2 again
Matsukura: agriculture use case
... there are 3 kinds of requirements
... device virtualization, state for things, units
... reference to Genivi's site suggested by somebody
Lagally: btw, maybe you should remove extra <br> tags from the MD file :)
Matsukura: ok
Lagally: initial use case document to
be generated
... the idea is making the use case discussion part of the
IG
... so that non-WG participants can join it easily
... by creating a separate wot-usecases repo, etc.
... technical contributions to the actual specs still remain at
the Architecture TF
Kaz: think the separation is
reasonable
... uc/req discussion can be done by the IG
... actual REC work to be done by the WG
Lagally: official resolution is still
to be done
... but we can move the "USE-CASES" resources to the new
repo
... (shows the initial UC/REQ Note)
Kaz: so we can make a preliminary resolution from this call 1, and make the final resolution during call 2
Lagally: (generates it)
<mlagally_> proposal: hand over contents of thre USE-CASE directory to the Use Case IG TF for inclusion into a Use Cases document
RESOLUTION: hand over contents of the USE-CASE directory to the Use Case IG TF for inclusion into a Use Cases document
Lagally: we have two additional co-Editors for this UC document, Matsukura-san and Mizushima-san
Kaz: great
Lagally: btw, Kaz has just created a
draft UC prioritization questionnaire
... which lists all the UCs so far classified by its
category
... that's it for today
... anything else?
(none)
Lagally: please join the Use Case TF call later today as well!
[Call 1 adjourned; UC call in 4 hours; Call 2 in 8 hours]
<scribe> scribenick: kaz
<mlagally__> fyi, https://www.iamexpat.de/education/primary-secondary-education/school-holiday-dates-germany
Lagally: (goes through the agenda)
Lagally: posted the slides
... to be added to the May-14 slides
<scribe> scribenick: zkis
Lagally: propose to accept with the small fix
[minutes accepted]
Lagally: There was a call earlier today
... editing wiki with F2F agenda proposal
McCool: in the future, we should avoid putting dates in the title, since it may change
Kaz: I could create another page and put a link to the old page (after this call)
Lagally: goes through the proposed F2F
agenda topics and figuring out the time needed
... a new section is needed for the lifecycle discussion
... shows the lifecycle proposals
Zoltan: the new section should be concise enough and we need to discuss content prioritization
Lagally: state names, transitions, security, etc
Zoltan: sounds good
Lagally: a small request: please create an SVG snapshot from the latest diagram and upload to the repo
<scribe> ACTION: ZK updates the SVG snapshot
McCool: let's note which Architecture calls we can have due to holidays
Lagally: records the call dates in the wiki
McCool: we will have similar issues
with the Use Case call
... therefore we should have it also with the plugfest
call
... will put placeholder agenda sections and mention what is
cancelled or not
... we should also have a summer break
Lagally: fine with that
McCool: will update the invites and will send updates to the members list
<scribe> ACTION: MM to update meeting invites
Lagally: there is the new Use Case IG
taskforce forked from the Architecture TF
... there is a new call
... all IG members could contribute use cases
... not only WG members
... there is a new Use Cases document
Lagally: will be a Note
... right now it's only a skeleton
... Requirements will be separated from Use Cases
... and should happen in the WG because of potential IPR
context
... co-editors are welcome to the Use Case doc
McCool: looks good, we could merge the PR
<inserted> Pullrequest 498
Lagally: #498
... adds the profiles use case
Koster: there could be something
specific about code generation
... the system should be able to do adaptation
McCool: profiles in general need some pre-work
Lagally: this is still good for
starting the profile discussion during the F2F
... automatic code generation could be a requirement
McCool: well, we should avoid
_automatic_ code generation, maybe in development time
... we should avoid too fancy stuff, rather define the context
better
Lagally: ok, let's merge this now
McCool: agreed
<inserted> Pullrequest 500
McCool: updates retail.md with security and privacy considerations
Lagally: good to merge
<inserted> Pullrequest 504
Lagally: adds medical devices use case
Lagally: it is under review still
McCool: needs more review and Taki is not here, so let's defer
Lagally: ok, let's keep it open for
now
... will add comments
<inserted> Pullrequest 505
Lagally: agriculture use cases
McCool: would separate greenhouse use case from generic agriculture use case category
Lagally: should we merge?
McCool: maybe review it more, as the author is not here
Lagally: ok, adding a comment
<inserted> Pullrequest 509
Lagally: adding smart building use case
McCool: discovery stuff should be
moved
... ok with merging it and will make a comment
Lagally: adding a comment with
summary
... merging
... ok, we finished the PRs
... AOB?
Lagally: working on the draft
questionnaire
... I would keep it open for 2 weeks
McCool: ok that's enough to process
and prepare for the PF and F2F
... note that discovery is not a category, but a horizontal
thing
... automotive is a vertical use case
Lagally: yes these will need to be broken down
McCool: ok it's good enough for
collecting information
... features are horizontal, use cases are vertical
... we could have a table/matrix with these
Lagally: I am more inclined to break
down the categories
... let's not overcomplicate, use this questionnaire and then
process the results
McCool: agreed to go ahead, the suggestion was for future work
Lagally: OK.
... well, that concludes. We will look into the Issues next
time.
Kaz: we need the final resolution of moving the use cases into the new use case repository?
Lagally: yes - we made a resolution in the Arch call 1
<kaz> Proposal: hand over contents of the USE-CASE directory to the Use Case IG TF for inclusion into a Use Cases document
Lagally: does everybody approve this?
McCool: we need to deal with IP
consequences
... since we move from WG repo to an IG repo
... this loosens the IP requirements
... so it's unlikely there will be complaints
Lagally: since one cannot patent a use case, there should not be much problem
McCool: but formally needs to be addressed since the WG -> IG move
Lagally: so, do we approve the
resolution?
... all IG members would access it
McCool: would we extend the rights to guests as well?
Lagally: yes
[accepted]
RESOLUTION: hand over contents of the USE-CASE directory to the Use Case IG TF for inclusion into a Use Cases document at the expected wot-usecases repo
Lagally: will make the move later
<kaz> ACTION: kaz to create a new repo of wot-usecases
Lagally: AOB?
[adjourned]
<kaz> (next call in 2 weeks)
