Skip to content

Update local bibliography refs#681

Open
kezike wants to merge 3 commits into
w3c:mainfrom
kezike:654-update-local-biblio-refs
Open

Update local bibliography refs#681
kezike wants to merge 3 commits into
w3c:mainfrom
kezike:654-update-local-biblio-refs

Conversation

@kezike

@kezike kezike commented Jul 20, 2026

Copy link
Copy Markdown
Collaborator

This PR addresses Issue #654 by updating the Recognized Entities reference and cleaning up the local bibliography.


💥 Error: 500 Internal Server Error 💥

PR Preview failed to build. (Last tried on Jul 20, 2026, 9:20 AM UTC).

More

PR Preview relies on a number of web services to run. There seems to be an issue with the following one:

🚨 Spec Generator - Spec Generator is the web service used to build bikeshed/ReSpec specs

🔗 Related URL

Error output:

EISDIR: illegal operation on a directory, open 'uploads/8oeN34/'

This seems to be an issue with the Spec Generator service. PR Preview doesn't manage this service and so has no control over it. If you've identified an issue with it, you can report the issue to the maintainers of Spec Generator directly. Please be courteous. Thank you!

If you don't have enough information above to solve the error by yourself or if the issue doesn't seem related to Spec Generator, you can file an issue with PR Preview.

Comment thread threat_model/index.html
Comment on lines -54 to -83
"ISO18004": {
title: "ISO18004:2024: QR Code Bar Code Symbology Specification",
href: "https://www.iso.org/standard/83389.html",
status: "Published",
publisher: "ISO"
},
"DCAPI": {
title: "Digital Credential API",
href: "https://www.w3.org/TR/digital-credentials/",
status: "WD",
publisher: "W3C"
},
"OID4VCI": {
title: "OpenID for Verifiable Credential Issuance v1.0",
href: "https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0.html",
status: "WD",
publisher: "OpenID Foundation"
},
"OID4VP": {
title: "OpenID for Verifiable Presentations v1.0",
href: "https://openid.net/specs/openid-4-verifiable-presentations-1_0.html",
status: "WD",
publisher: "OpenID Foundation"
},
"VC-RECOG-ENT": {
title: "Recognized Entities v1.0",
href: "https://www.w3.org/TR/vc-recognized-entities/",
status: "WD",
publisher: "W3C"
}

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems we aren't using these references in the threat model, so I have decided to remove it. FYI @jandrieu @eric-schuh

Comment thread index.html
of the workflow the exchange is based on, and the options provided by the
coordinator when the exchange was created.
potentially be executable with any of the [[OPENID4VCI]], [[OPENID4VP]],
[[DIDCOMM]], and exchange protocols. The protocols supported depend on the

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should I make DIDCOMM an informative reference here?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It may make sense for these to be [[[ ... ]]] [[ ... ]] pairings, which render as the document's title with href of the document itself, followed by the document's specref ID with href of the citation in the Citations section of the document, a la —

Suggested change
[[DIDCOMM]], and exchange protocols. The protocols supported depend on the
potentially be executable with any of the [[[OPENID4VCI]]] [[OPENID4VCI]],
[[[OPENID4VP]]] [[OPENID4VP]], [[[DIDCOMM]]] [[DIDCOMM]], and/or exchange
protocols. The protocols supported depend on the

Comment thread index.html
focuses on how an exchange client uses this API to interact with the exchange; see
<span class="issue">Appendix TBD</span> to see how to combine exchanges
with other protocols such as OID4VCI, OID4VP, and DIDComm.
with other protocols such as [[OPENID4VCI]], [[OPENID4VP]], and [[DIDCOMM]].

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should I make DIDCOMM an informative reference here?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As above. I leave the production of the [[[ ... ]]] [[ ... ]] pairings as an exercise for the reader.

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.

2 participants