Zoom Meeting Link / Recording
Attendees
@Philip Feairheller @Sam Smith @Alan Davies @Henk van Cann @Daniel Hardman @Kent Bull
Agenda Items and Notes (including all relevant links)
Time | Agenda Item | Lead | Notes |
5 min | | Chairs | Antitrust Policy Notice: Attendees are reminded to adhere to the meeting agenda and not participate in activities prohibited under antitrust and competition laws. Only members of ToIP who have signed the necessary agreements are permitted to participate in this activity beyond an observer role. New Members: None NOTE: There is still some confusion as to which Zoom meeting link is the correct one for this meeting. The KERI dev call should be canceled on the thirds Tuesday to reduce this confusion. A subset of this group ended up meeting in the KERI dev Zoom meeting today.
|
5 mins | Review of action items from the previous meeting | Chairs | (spec update) Kent to check for any definitions referencing the whois section. (spec update) Kent to remove the whois.md from the spec and to put it in a different folder in the repo. (code update) Kent to finish the delegation implementation and default alsoKnownAs DIDs (spec update) Move excessively informative language from the body of the spec into an annex.
|
5 mins | Announcements | TF Leads | News or events of interest to members: |
5 mins | Reports | Open | |
25 mins | Discussion | Open | Action Items from last time: alsoKnownAs default did:web DID This DID should only be present in the alsoKnownAs section when the controller of an AID places the did:web DID in a designated aliases ACDC. If I don’t put the did:web DID in the designated aliases ACDC then they can’t trust the did:web DID any more than they can trust their zone files. Placing a did:web DID in the designated aliases ACDC ensures that the controller actually committed to that DID.
The spec should be changed to say the did:web DID should be in the DID doc ONLY WHEN the DID is found in a designated aliases ACDC.
Daniel Hardman to do Dossier spec first, did:webs half of the meeting second Important Open Spec Issues The next DID community-oriented tasks to tackle should be
|
5 mins | Any other business | Open | |
5 mins | | Chairs | (spec lint) Kent to review all of the definitions in the document with Henk to see what we can reference from the KERI Suite Glossary instead of explicitly restating them. (spec update) Use the grey highlighting to indicate informative vs. normative language. (spec and impl update) remove the default did:web from alsoKnownAs and make so that the spec is clear in that did:web is only expected when it is found in an ACDC. (spec update) Move excessively informative language from the body of the spec into an annex.
|
Notes from the Dossier portion of the meeting:
The Evidence Advantage: Building Trust for a New Era in Telecom
preponderance of evidence
the preponderance of evidence indicates that such is likely to be the case. bulk, majority, greater quantity, larger part, best/better part, main part, most, almost all, more than half, mass, weight, (main) body, lion's share, predominance, generality.