Meeting minutes
housekeeping
minutes
<kaz> Apr-13
Lagally: review of April 13 call notes
… at-risk presentation, PR 902
… any objections to publishing?
… no objections, publish
task force leadership
Lagally: I have to step down as TF lead
Lagally: enjoyed it, but have been assigned new responsibilities
… Michael McCool has offered to take over for now
McCool: to clarify, I can start next week, and this is temporary until we find someone else
McCool: we will have to have a general discussion about TF leadership changes
Kaz: don't think we need detailed discussion on the procedure, but could start with asking the current TF participants about their interest
McCool: yes, I can send an email following up to Lagally's asking for nominations
… ideally, the new lead would be someone who's been involved so we have continuity
societal impact questionnaire
<kaz> PR 897 - Societal Impact Questionniare
Lagally: pull request from McCool
… this is for TAG review
McCool: note this is for the group as a whole, not just architecture
… so final approval will have to be in the main call
Lagally: understood. I think it would be useful to get additional reviewers, so I added a number to the PR
McCool: do think I want to merge a number of review inputs, set a deadline, and do a final pass.
Kaz: do think we should cover it again in the main call next week
McCool: also, is there an actual deadline?
Kaz: we can talk with Dan about that.
McCool: thinking of covering this in next main call, then do a call for resolution in two weeks
Test fest preparation
Lagally: so there were two PRs merged already, #906 and #907
<mlagally> PR 906 - Updated IR after addition of Intel-OCF results
<mlagally> PR 907 - Update IR with saywot and editdor results
Lagally: that updated the IR with new results from intel-ocf, saywot, and editdor
… and the result is we only have 3 assertions at risk now
McCool: actually, no results from editdor, they did new TDs only
… also, two of the remaining assertions are not priorities, so we only really have one to focus on
Lagally: for the record, I still think there needs to be a place for system-wide assertions
McCool: agree, but for now we should focus on finishing this charter's deliverables
McCool: note that ALL assertions in template.csv should be in manual.csv, so for testfest should copy it over again; last time was 5 months ago, but template.csv is showing changes from last week
Lagally: and do double-check, data is still in input_2022?
McCool: yes; when it started, not when it is done
Kaz: need to check current status of data including the results from both the group participants and the external developers.
McCool: as far as I know, we don't currently have external results in architecture
Kaz: should identify which assertions are the priority
McCool: we discussed, the hal-unsafe one is the priority, will document in testfest readme
Lagally: would also be good to check and update the instructions
McCool: will do
McCool: we do have more implementation descriptions than results submitted, but we have enough
Lagally: right, the goal is just to prove it is implementable, which we have done
McCool: anyway, I will do a final pass of cleanup today
PRs
<kaz> PR 856 - Additional terminology entry for Web Object
Lagally: there is a PR for "Web Object", #856
… from a while ago.
McCool: don't have a problem with the diagram, but the definition of Web Object is a bit too general, and only impacts Profiles, so we can defer
Kaz: tend to agree with McCool, we have other, overlapping definitions like "Web Thing" and "Servient".
McCool: a separate PR with just the diagram I would support
toumura: this diagram was meant to be an opener for Arch 2.0
McCool: so I would also be ok with deferring the entire PR to Arch 2.0
Lagally: ok, let's do that
Issue Review
Lagally: let's look through issues and see if there are any we can close
<kaz> Issue 888 - Evaluating At Risk Assertions
<kaz> Issue 869 - Use Case due diligence
Lagally: can close 888, 869: done
… also defer 899 to arch 2.0
<kaz> Issue 870 - Requirements assessment
Lagally: can consider 870 done as well
McCool: re 870, at least for this charter
… looking at requirements is going to be an ongoing process
… suggest changing title to say "for Arch 1.1" and consider it done
<kaz> Issue 571 - Identity and Identifier should be defined terminology
Lagally: issue 571, identifier as terminology
McCool: too late to include now, suggest defer
<kaz> Issue 850 - Contradiction with the WoT Profile spec on protocol bindings
Lagally: let's defer #850 to arch2.0: about profiles and hypermedia
McCool: generally the hypermedia issue needs work
<kaz> Issue 578 - Accessibility considerations of WoT architecture
Lagally: looks like APA re-opened #578, request for "Accessibility Considerations" section
McCool: since is wide review feedback, we should consider seriously
… leave open, let's look at it next week.
<kaz> [adjourned]