Meeting Link / Recording

Video recording will be here
Transcript will be here

Attendees

This is a future meeting

Agenda Items and Notes (including all relevant links)

Time	Agenda Item	Lead	Notes
5 min	Start recording Welcome & antitrust notice Introduction of new members Agenda review	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: Current work Spec repo to be donated to ToIP if WG/TF is approved https://github.com/dhh1128/did-method-webs https://dhh1128.github.io/did-method-webs/index.html Previous reference impl was started here https://github.com/WebOfTrust/did-keri-resolver
5 mins	Review of action items from previous meeting	Chairs	Consider pros/cons and strategy for where reference implementations live Lance Byrd will start an ACDC PR to the spec that describes signing Lance Byrd will provide an outline of how to use a TEL to verify the signature document Daniel Hardman will donate his dh1128 repo if ToIP will allow.... all commits are signed
5 mins	Announcements	TF Leads	News or events of interest to members: This is a provisional WG/TF and we hope to be officially under ToIP in September 2023 Change meeting time to better accomodate west coast (times after 10am ET)? https://doodle.com/meeting/participate/id/bY5AJgnb Thoughts on amending the charter https://wiki.trustoverip.org/display/HOME/ZZ+-+Proposal+-+DID%3AWebS+Task+Force regarding where the code lives. For instance, under IPR, ACDC has the following clause “The ACDC TF is not expected to produce source code.” There is no such clause in the did:webs charter. Possibly in WoT repos Possibly start here as a neutral repo Ideal spot in terms of coaliton/PR? As public as possible. Possibly DIF, where the universal resolver lives At least provide some universal resolver contributions Possibly OWF Contributions in support of wallets IIW October 2023 Do we want to define milestones, like IIW, for the spec and reference impl? Arrive with a coherent draft, already registered in DID registry Also arrive with reference impl in DIF Universal Resolver DIF identifiers discovery In next Monday's DIF ID WG meeting, we will talk about "lifecycle of did:web identifiers" which also seems related to this topic: https://github.com/decentralized-identity/identifiers-discovery/blob/main/agenda.md#meeting---28-aug-2023---1400-et did:plc discussion https://github.com/decentralized-identity/identifiers-discovery/blob/main/agenda.md#meeting---25-sep-2023---1400-et
5 mins	Reports	Open	Upcoming milestones IIW Fall 2023 There are several potential opportunities, Daniel Hardman will report soon.
25 mins	Discussion	Open	Daniel Hardman suggested last week that we explore the 'notion that did:web can borrow the view of did:webs" during our discussion about using JWS vs. ACDC. https://github.com/dhh1128/did-method-webs/issues Activity this past week Stephen Curran reviewed the newly added did doc section information alsoKnownAs vs equivalentId whois weighted threshold multi-sig SSL/TLS common name https://github.com/dhh1128/did-method-webs/pulls Activity this past week Signed Files Whois VCs + JWS vs. Service Endpoint
5 mins	Any other business	Open
5 mins	Review decisions/action items Planning for next meeting	Chairs

2023-08-31 Provisional websWG Meeting Notes

[data-colorid=h986qdsa56]{color:#1f1f1f} html[data-color-mode=dark] [data-colorid=h986qdsa56]{color:#e0e0e0}Meeting Link / Recording

Attendees

Agenda Items and Notes (including all relevant links)

Meeting Link / Recording