- From: CCG Minutes Bot <minutes@w3c-ccg.org>
- Date: Tue, 16 Jan 2024 19:32:19 +0000
Thanks to Our Robot Overlords and Nis Jespersen and Our Robot Overlords and Nis Jespersen for scribing this week! The transcript for the call is now available here: https://w3c-ccg.github.io/meetings/2024-01-09-traceability/ Full text of the discussion follows for W3C archival purposes. Audio of the meeting is available at the following location: https://w3c-ccg.github.io/meetings/2024-01-09-traceability/audio.ogg A video recording is also available at: https://meet.w3c-ccg.org/archives/w3c-ccg-weekly-2024-01-09.mp4 ---------------------------------------------------------------- Verifiable Traceability Task Force Transcript for 2024-01-09 Agenda: https://www.w3.org/Search/Mail/Public/advanced_search?hdr-1-name=subject&hdr-1-query=%5BAGENDA&period_month=Jan&period_year=2024&index-grp=Public__FULL&index-type=t&type-index=public-credentials&resultsperpage=20&sortby=date Organizer: Orie Steele, Mike Prorock, Mahmoud Alkhraishi Scribe: Our Robot Overlords and Nis Jespersen and Our Robot Overlords and Nis Jespersen Present: Mahmoud Alkhraishi, Nis Jespersen , Chris Abernethy, Russell H (mesur.io), TallTed // Ted Thibodeau (he/him) (OpenLinkSw.com), Ted Thibodeau, Patrick St-Louis, Benjamin Collins Our Robot Overlords are scribing. Mahmoud Alkhraishi: My Edinburgh there you go welcome to the first race call of the Year let me turn off the Scribe. Mahmoud Alkhraishi: Welcome to the first trace call of the year [scribe assist by Nis Jespersen ] Mahmoud Alkhraishi: After normal procedures, we will go through all issues in prep for cutting v1 [scribe assist by Nis Jespersen ] Mahmoud Alkhraishi: https://github.com/w3c-ccg/traceability-vocab/pulls <nis> Both specs, by end of the month Mahmoud Alkhraishi: https://github.com/w3c-ccg/traceability-vocab/pull/919 <nis> scripe+ Nis Jespersen is scribing. Two approvals, merging Mahmoud Alkhraishi: https://github.com/w3c-ccg/traceability-vocab/pull/920 Next, udpated nomination More agnostic to both gas and oil pipelines Merging Next: purge EIP Mahmoud Alkhraishi: https://github.com/w3c-ccg/traceability-vocab/pull/921/files Nis Jespersen : This was based on BTI report, but not used Nis Jespersen : These workflows predate our workflow data model, removing them Mahmoud Alkhraishi: https://github.com/w3c-ccg/traceability-interop/pulls Mahmoud Alkhraishi: https://github.com/w3c-ccg/traceability-interop/pull/595 Nis Jespersen : Long time coming, several iterations with GS1, should be good to merge now. Mahmoud Alkhraishi: https://github.com/w3c-ccg/traceability-interop/pull/611/files Mahmoud Alkhraishi: We don't use VC JWT, seems good to remove Merging https://github.com/w3c-ccg/traceability-interop/pull/612 Mahmoud Alkhraishi: Should only matter if your processor it case specific Chris Abernethy: Let's see if we start failing Mahmoud Alkhraishi: Interop has 21 issue, vocab 60 Let's go through them from the top Tag the ones required for v1. Chris Abernethy: Is that the same as the VC2 tagging? Mahmoud Alkhraishi: https://github.com/w3c-ccg/traceability-interop/issues Mahmoud Alkhraishi: https://github.com/w3c-ccg/traceability-interop/issues/614 Chris Abernethy: Assign to me, I will see why we're doing this Mahmoud Alkhraishi: Might not be a v1 issue Mahmoud Alkhraishi: https://github.com/w3c-ccg/traceability-interop/issues/613 Mahmoud Alkhraishi: For the record, any objections to moving the meeting time back to the original time? (No objections) Chris Abernethy: The jsonld looks right to me Mahmoud Alkhraishi: If the service does not have a context, that needs fixing Chris Abernethy: It should be in the DID context "Service" needs to be defined Mahmoud Alkhraishi: There's missing context on some terms. This seems like a vocab issue Mahmoud Alkhraishi: Are we going to do this for v1? Chris Abernethy: I can take a stab Label is v1.0 Mahmoud Alkhraishi: https://github.com/w3c-ccg/traceability-interop/issues/604 Mahmoud Alkhraishi: https://github.com/w3c-ccg/traceability-interop/issues/602 <tallted> started at top of hour? calendar still shows start at half-past... Mahmoud Alkhraishi: Remove DID Auth 602 Mahmoud Alkhraishi: Not possible to move the schedule. Our Robot Overlords are scribing. Nis Jespersen is scribing. Next week we WILL start at this time, half past the hour Ambition: to cut a v1 Mahmoud Alkhraishi: https://github.com/w3c-ccg/traceability-interop/issues/602 Nis Jespersen : 602 Is DID Auth, we can close Mahmoud Alkhraishi: 604 Has the resolution Closing Mahmoud Alkhraishi: https://github.com/w3c-ccg/traceability-interop/issues/589 Patrick St-Louis: The VC API workflows are used to start an exchange OIDC or DIDComm Path based on the kind of workflow Pretty different from the presentation exchange on trace interop VC API is for shorter exchanges Mahmoud Alkhraishi: These are two fundamentally different concepts Nis Jespersen : When Manu joined a month ago it sounded like we were much more aligned Mahmoud Alkhraishi: Could be VC API can also be used long term Our workflows are month-long Patrick St-Louis: Across multiple presentation? Mahmoud Alkhraishi: Yes Nis Jespersen : To connect multiple presentations Mahmoud Alkhraishi: Used by the holder On the VC playground, when you have an issuer with OIDC, you get a workflow exchange id You get an exchange for the workflow ^ Patrick Mahmoud Alkhraishi: Patrick, please bring this up on the VC API group About their understanding Mahmoud Alkhraishi: https://github.com/w3c-ccg/traceability-interop/issues/582 Mahmoud Alkhraishi: This is nice to have Nis Jespersen : Chris: +1 Nis Jespersen : Nis +1 Mahmoud Alkhraishi: https://github.com/w3c-ccg/traceability-interop/issues/574 Chris Abernethy: We closed PR 606 because it was a negative test Nis Jespersen : This should be done Mahmoud Alkhraishi: Closing Mahmoud Alkhraishi: https://github.com/w3c-ccg/traceability-interop/issues/544 Mahmoud Alkhraishi: We have oauth mentioned several places We don't need more Nis Jespersen : Nis +1 Mahmoud Alkhraishi: We need normative section on who initiates the interaction Chris Abernethy: The paragraph in the intro seems to be describing DIDAuth Patrick St-Louis: Back to workflows, who uses workflow ids? Mahmoud Alkhraishi: Both holders and verifiers Mahmoud Alkhraishi: Removing the paragraph is in 572. Closing Mahmoud Alkhraishi: https://github.com/w3c-ccg/traceability-interop/issues/543 Patrick St-Louis: Who would be the party creating the workflow id? Nis Jespersen : Always the holder Mahmoud Alkhraishi: https://github.com/w3c-ccg/traceability-interop/issues/534 When you make a presentation, you are a holder Mahmoud Alkhraishi: https://github.com/w3c-ccg/traceability-interop/issues/533 Chris Abernethy: A few have been done Mahmoud Alkhraishi: I will review Mahmoud Alkhraishi: https://github.com/w3c-ccg/traceability-interop/issues/532 Mahmoud Alkhraishi: Important for v1 Mahmoud Alkhraishi: https://github.com/w3c-ccg/traceability-interop/issues/531 Mahmoud Alkhraishi: https://github.com/w3c-ccg/traceability-interop/issues/530 Mahmoud Alkhraishi: We removed the workflows today Nis Jespersen : Confirmed, we merged that today Mahmoud Alkhraishi: https://github.com/w3c-ccg/traceability-interop/issues/529 Mahmoud Alkhraishi: Do we still want to make this sectino on relation to VC API? Patrick St-Louis: It's just the credentials issue and verify you are using Mahmoud Alkhraishi: Yes, that relation Patrick St-Louis: The options when issuing. In trace you do make use of the options, VC API has preconfigurations Mahmoud Alkhraishi: That is a good comment Mahmoud Alkhraishi: Do we still need the section? Patrick St-Louis: Just say this was inspired by VC API Makes sense since VC API is also used in other test suites Mahmoud Alkhraishi: Can we stick around for the last 7 issues Mahmoud Alkhraishi: https://github.com/w3c-ccg/traceability-interop/issues/528 Mahmoud Alkhraishi: Abstract update. Straight forward Mahmoud Alkhraishi: https://github.com/w3c-ccg/traceability-interop/issues/506 Nis Jespersen : We are not making a dependency between VC2.2 for Trace v1 Mahmoud Alkhraishi: No Mahmoud Alkhraishi: We should make cryptography list Pinging Orie Chris Abernethy: VC2.0 was supposed to halt the issue discussion until upgrade Mahmoud Alkhraishi: Yes, but considering from a Trace v1 perspective Mahmoud Alkhraishi: https://github.com/w3c-ccg/traceability-interop/issues/496 Chris Abernethy: Will review Mahmoud Alkhraishi: https://github.com/w3c-ccg/traceability-interop/issues/482 Mahmoud Alkhraishi: Revoc2020 is deprecated, do we want to switch references to SL 2021? Patrick St-Louis: Sounds like it could go. The flow is the same I just implemented both, 2021 only would streamline things Mahmoud Alkhraishi: https://github.com/w3c-ccg/traceability-interop/issues/453 Chris Abernethy: JWT request body Nis Jespersen : We just removed the VC JWT collection Mahmoud Alkhraishi: This is JOSE/COSE Mahmoud Alkhraishi: https://github.com/w3c-ccg/traceability-interop/issues/405 Mahmoud Alkhraishi: https://github.com/w3c-ccg/traceability-interop/issues/359 Mahmoud Alkhraishi: I want to say no to supporting SD_JWT on Trace v1 Nis Jespersen : Nis +1 Too ambitious Patrick St-Louis: How do I test that revocation actually work? Patrick St-Louis: Only negative testing Mahmoud Alkhraishi: Please review Vocab issues before next week So we can go through the 60 issues quickly Mahmoud Alkhraishi: Next week reverting to the original time Mahmoud Alkhraishi: https://github.com/w3c-ccg/traceability-vocab/blob/main/docs/openapi/components/schemas/common/TradeLineItem.yml Mahmoud Alkhraishi: https://github.com/w3c-ccg/traceability-vocab/blob/main/docs/openapi/components/schemas/common/TraceabilityAPI.yml Mahmoud Alkhraishi: https://github.com/w3c-ccg/traceability-vocab/pull/919
Received on Tuesday, 16 January 2024 19:32:19 UTC