The W3C Credentials Community Group

Meeting Transcriptions and Audio Recordings (2014-today)

Go Back


Verifiable Traceability Task Force

Transcript for 2023-06-06

russell_hofvendahl_(mesur.io) is scribing.
Our Robot Overlords are scribing.
Nis Jespersen : Greetings, welcome to trace call, don't forget to sign contributor agreement
Mahmoud Alkhraishi: Confused. Why monetary? Different PR?
Orie Steele: Don't know why there, but that's OpenAPI yaml, auto built from folders
Nis Jespersen : Bit of delay before gets to openapi, why it got in here
Mahmoud Alkhraishi: K, CI error but didn't break
Orie Steele: Not CI, artifact of how we construct CI from folder of docs regularly merged
Mahmoud Alkhraishi: Happy to merge
Nis Jespersen : Next, also Orie, 795
Orie Steele: Just removes name, description fields, updates text
Orie Steele: Nis, if yours does it for everything, let's merge yours before mine
Nis Jespersen : Might want to do 798 first
Mahmoud Alkhraishi: Anyone on mesur side using name descr?
Russell Hofvendahl: Unsure, would need to look into
Orie Steele: Wouldn't impact gs1
Chris Abernethy: Deferring to Russell
Mahmoud Alkhraishi: Happy to merge after if this works for mesur
Nis Jespersen : So close 795
Orie Steele: To be clear, issuerName
Nis Jespersen : Objections?
Orie Steele: Same comment, if you care about issuerName prop being allowed, may want to engage with VC group, have added name/descr to cred, not to issuer
Nis Jespersen : K, still want to merge, merging
Orie Steele: In general bundle api, so can download all schemas, this PR attempts to do something regarding workflows?
Chris Abernethy: Seems like new files containing paths just moved, hiding workflows
Orie Steele: Agree, helpful refactoring would love to merge if doesn't break, but if breaks then fire mode
Chris Abernethy: Yeah, separate into two PRs
Benjamin Collins: Sync with adam before merging
Orie Steele: Other side, any PRs on top of, drift? Just indexing?
Nis Jespersen : I'll check out after meeting, engage with Adam
Benjamin Collins: Getting in nis/I as authors before we freeze everything
Orie Steele: Removed Brian Muntz
Mahmoud Alkhraishi: This PR adds to authors, not Editors, correct
Nis Jespersen : Great, merging, please keep coming so all represented
Mahmoud Alkhraishi: I can. interop, 553, Orie?
Orie Steele: Yes, on last call when we did issue processing assigned me several issues related to selective disclosure, this PR closes those issues
Mahmoud Alkhraishi: Bunch of approvals no objections, merging
Orie Steele: Several scenarios, trying to get ready for vc v2, getting stuck on rev list 2020 holds us back. Also VC JSON schema work, also want to get alignment
Mahmoud Alkhraishi: Orie, articulate what you said in comment?
Orie Steele: Have, merge PR work on tests for what want in v2, get off tests for thing not mentioned in spec anymore
Orie Steele: Already have issue, so make search for and add
Mahmoud Alkhraishi: Update sections for normative vs non-normative language, parts say informative some normative
<orie> Lots of suggestions need to be applied
Nis Jespersen : Address some changes discussed last time, from Mike last time, so re-wrote workflow section
<russell_hofvendahl_(mesur.io)> Mahmou: Also Orie
Orie Steele: Avoid statements inside advisement blocks
Mahmoud Alkhraishi: Yes. Any objections?
Benjamin Collins: Also conflicts
Mahmoud Alkhraishi: Ted?
Ted Thibodeau: Adding myself to block
<orie> sry i need to drop
Mahmoud Alkhraishi: That's all PRs today
Nis Jespersen : Yes
Nis Jespersen : +1 On too generic
Mahmoud Alkhraishi: Moving on
Nis Jespersen : Yeah
Nis Jespersen : +1
Mahmoud Alkhraishi: Instinct, we do not need this. Everyone else?
Benjamin Collins: Pending close probably
<chris_abernethy> Apologies - I need to drop as well.
Mahmoud Alkhraishi: Fair.
<chris_abernethy> I'm happy to publish today, please slack if needed.
Benjamin Collins: Thoughts on this
Mahmoud Alkhraishi: Agree, but important thing issue 385 at top. I believe only one is events linking to products.
Benjamin Collins: Example at top, seems separate from commisionevent with hash
Mahmoud Alkhraishi: If only using hashlink for events, if following different model then makes this convo moot
Benjamin Collins: Close in favor of keeping 385 open?
Mahmoud Alkhraishi: Might be best we can do, reality that cant add semantics to every edge
Benjamin Collins: Reality this is expected hashes at this point in time, don't see any way around that
Mahmoud Alkhraishi: Don't see workaround
Benjamin Collins: Nis?
Nis Jespersen : If you don't have better term, invented under trace, more recently switched to @vocab
Mahmoud Alkhraishi: Thing, orie's comments on thread say, we should upadate this line so doesn't point to hashlink, but some semantic meaning like product we have. Issue is, always receive hashlink, not product
Benjamin Collins: But context, @id points to context
Mahmoud Alkhraishi: Point is that every term within that, rn every array of type string, should be array of type url
Nis Jespersen : Still feels like misusing @id here. Repeating what you said, it's primitive type it's not semantic type
Mahmoud Alkhraishi: K, look at line 47, is that misusing type id
<nis> 1+
Nis Jespersen : Great yes
Mahmoud Alkhraishi: Need a second to write comment
Nis Jespersen : Yes, only thing is trace product, should not be necessary for us to invent
Mahmoud Alkhraishi: Already have I think
Benjamin Collins: Now explicitly says what expects to be there
<russell_hofvendahl_(mesur.io)> Mahmou: Great. Only question is idk fi url, #url works?
Benjamin Collins: Think formatUrl can have hashtag at end
Nis Jespersen : I believe we mostly use URI, would use that
Mahmoud Alkhraishi: Assigning to me
Benjamin Collins: Even if spent time on, at least if closed out then success
Mahmoud Alkhraishi: 561, Big one, EPCIS modelling of events. All the event schemas we have,
Mahmoud Alkhraishi: K, call it a day