Ben: Change request for mahmoud, but similar change. This narrows scope of schema to fit specific example, not reduce optionality. This is JSON replacing a specific form, having closer values to what would expect ✪
Jim M: So if we get into cross-border movement, these specific terms would be required in-schema? ✪
Nis Jespersen : Commercial invoice like any other. Til recently we pieced together cred schemas from full set of RDS building blocks. What schemas reflect now is extremely big systems. These are recent changes, to narrow it down. Ben selected specific attrs to narrow it down to commercial invoice ✪
Jim M: so truly commercial invoice between buyer and seller ✪
Chris Abernethy: Since last week [?] has had a chance to weigh in on this, think these are worth reviewing ✪
<orie> MUST and SHOULD / MAY.
Chris Abernethy: Not possible for requester to guarantee they are providing IDs unique to requester ✪
Orie Steele: You both might be talking abt diff endpts ✪
Chris Abernethy: On board, believe you suggested in update endpt, someone who calls could provide identification in credential, but might not be able to look up [?] ✪
Orie Steele: Not guaranteed uniqueness. Depends on issuer, if assigned identifier & using consistently get but with addnl constraints ✪
Chris Abernethy: Agree, esp with increased complexity you pointed out ✪
Chris Abernethy: Not currently reflected in trace API schema, will do ✪
Orie Steele: Should treat respec doc as source of true; openapi, tests, others as secondary sources of truth ✪
Chris Abernethy: Think specifying process for generating IDs not worth getting into. Issuer that generates, needs to be able to use that later ✪
Orie Steele: Inference in there, assuming [?]. Issuer could just do url example.123 for every cred, would conform with norm. Unless want not legal, we do need to describe what needs to be ✪
Nis Jespersen : What you're talking way into, issuing server decides on ID, VC ID, consequences? ✪
<orie> you could say it MUST be unique and it SHOULD be a urn:uuid:v4.
Chris Abernethy: I agree with both. Responding to Orie, yes agree need specify instructions for that ID, misunderstood you. Yes specify needs unique. ✪
Nis Jespersen : Sounds more like Manu's suggestion, we put it in options? ✪
Orie Steele: Accomplishing same thing, moving client provided paramn from one object to another ✪
Chris Abernethy: But it's there in VC, I think issue here is how it gets there ✪
Orie Steele: K was thinking more abt update endpt. If know it's there can use ID in update endpt. In creation, can throw 400 error in value or assign one, or override what client does - don't think we should do that ✪
Chris Abernethy: But then issue, a) removing option to do something need to do, b) injecting data into cred ✪
Paul: Customer said "just want a black box", as soon as delivered just achieve fail, message that even for simple that verification message really useful ✪
Chris Abernethy: Examples don't agree with spec rn ✪
Nis Jespersen : Would be enum of verification types right? ✪