Instruction file imported from w3c-fedid/digital-credentials (
.github/instructions/html.instructions.md). Copyright stays with the author.
Review Instructions for the Digital Credentials API Specification
You are reviewing pull requests to a W3C specification. Follow the rules in the sections below. Flag issues, uncertainties, and inconsistencies, and make concrete suggestions.
- ReSpec linking is correct and consistent (no raw
<a>for internal links). - Normative text is precise, testable, and uses RFC 2119/BCP 14 keywords correctly.
- Algorithms are deterministic, fully defined, and implementable.
- WebIDL is valid and matches algorithm behavior.
- Security, privacy, a11y, and i18n concerns are not obviously violated.
- Commit messages follow the project’s conventions. If you are unable to perform a comprehensive review of a PR, prioritize checking these key areas.
- [[CREDENTIAL-MANAGEMENT]] — Credential Management Level 1
- [[DOM]] — DOM Standard
- [[HTML]] — HTML Standard
- [[INFRA]] — Infra Standard
- [[PERMISSIONS]] — Permissions API
- [[PERMISSIONS-POLICY]] — Permissions Policy
- [[RFC2119]]
- [[RFC8174]]
- [[VC-DATA-MODEL]] — Verifiable Credentials Data Model v2.0
- [[WEBIDL]] — Web IDL Standard
Normative changes: Commit messages for normative changes normally have no prefix.
Breaking normative changes:
For normative changes that are breaking (i.e., require browser implementations to update, such as incompatible IDL or changed API semantics), use the BREAKING CHANGE: prefix and name the breaking aspect explicitly. See below.
Examples that can be improved:
fix stuffupdate specshould work nowedit: tweaks