Skip to content

Add discoverable chain pattern and cross-border trade use cases#80

Open
onthebreeze wants to merge 1 commit into
w3c:mainfrom
onthebreeze:un-use-cases
Open

Add discoverable chain pattern and cross-border trade use cases#80
onthebreeze wants to merge 1 commit into
w3c:mainfrom
onthebreeze:un-use-cases

Conversation

@onthebreeze
Copy link
Copy Markdown

Summary

  • Adds a "Recognition Patterns" subsection to the Introduction describing two patterns: the pre-configured list pattern and the discoverable chain pattern (where recognition credentials are discovered via DID service endpoints and verified by matching issuer/subject DIDs along a chain)
  • Adds two new use cases under "Discoverable Chain Use Cases":
    • Streamlined Border Clearance for Cross-Border Trade — customs authority verifies a commercial invoice by following the chain from exporter to national business register to UN GRID
    • Verifiable Product Conformity — buyer/regulator verifies a conformity certificate by following the chain from auditor to national accreditation authority to GACI
  • Adds sample JSON files in list-example/ illustrating both chains (recognized entity credentials and DID documents with service endpoints)
  • Updates "Commonalities and Differences" to acknowledge the discoverable chain pattern

Addresses #66

Test plan

  • Review rendered use-cases.html via PR preview
  • Verify JSON examples are valid and entity names are consistent across use case text and sample files
  • Verify DID subject/issuer linkage is correct across the chain examples

🤖 Generated with Claude Code

@iherman
Copy link
Copy Markdown
Member

iherman commented May 18, 2026

Regardless of whether this PR is acceptable or not, it looks like it is non-substantial, ie, it does not contain recommendation-track material. If that is indeed the case, I can release the IPR lock. Is that correct? Should I remove the lock?

@msporny ?

@msporny
Copy link
Copy Markdown
Member

msporny commented May 18, 2026

Regardless of whether this PR is acceptable or not, it looks like it is non-substantial, ie, it does not contain recommendation-track material. If that is indeed the case, I can release the IPR lock. Is that correct? Should I remove the lock?

My presumption is that @onthebreeze is going to make more contributions and we need to get his Github account fixed up, if not now, it'll need to happen in the next PR. Let's just get it sorted now (don't release the lock, @iherman)... shouldn't take more than a day or so to get it fixed up.

@onthebreeze
Copy link
Copy Markdown
Author

All good - I think I'm connected up now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants