Nothing substantive in the OpenID track. The one item worth noting is openid/sharedsignals, which now has 1.1 draft documents copied from 1.0 with 1.0 retained; the other two commits are thin.
Updated 13 November at 06:50 UTC
What changed
Substantive change
OpenID4VCI's S2S work renames its identifiers and switches all JSON properties to snake_case.
Two commits landed on the default branch, both tagged [S2S]. One ratifies the identifier model, renaming session_id to wallet_id and credential_instance_id to credential_id (#762, #810). The other makes all JSON properties snake_case (#791, #809). Only commit titles are available, so the exact affected messages and any semantic change beyond renaming are not visible.
A wallet or issuer implementer building against the S2S draft needs to update field names such as session_id and credential_instance_id.
Anyone writing JSON schemas or test fixtures for the S2S messages must switch to snake_case property names.
Substantive change
Openid/dchp saw 23 commits of spec edits: a field rename, credential_types as an array, and mdoc and SD-JWT VC wording fixes.
Only the commit titles are available, and 8 of the 23 are not listed, so this is a partial picture. The titles show CredentialItem.format renamed to credential_format and the format annexes adapted to credential_types being an array. They also show the following. The wallet, not the mdoc, chooses issuer- or device-signed. A substitute data element may be returned where its definition allows. The mapping of support_no_cryptographic_binding to DocRequestInfo was dropped. SD-JWT VC path semantics were deferred to issue #52, and a KB-JWT suggestion was applied. The ISO 18013-5 Document type is no longer redefined as a byte string, the authority key identifier now uses the RFC 5280 name, and RFC 7515 was added as a normative reference. Several other commits are review fixes and housekeeping. Exact wire-format effects cannot be confirmed from titles alone.
A single commit, "clarify signature key name", landed on the default branch. The material gives only the commit title, with no diff, so what was renamed or clarified and whether wire behaviour changed cannot be determined.
Minor or unclear
Openid/federation-wallet merged PR #71 from branch tm1; the content is not shown.
One merge commit, "Merge pull request #71 from openid/tm1", appeared. The material has no PR body or diff, so the substance of the change is unknown. The repository shows 1 open PR and 4 merged in the last 30 days.
Minor or unclear
Openid/sharedsignals created 1.1 draft documents from the 1.0 ones, keeping 1.0 intact.
Commit #310, "Create 1.1 draft documents from 1.0, retaining 1.0", sets up a 1.1 line of the Shared Signals specification documents as copies of 1.0 while keeping the 1.0 documents. The material shows no diff, so it is unclear whether any normative text differs yet. The repository has 12 open PRs, which may be waiting on a 1.1 base.
A Shared Signals transmitter or receiver implementer can now track where 1.1 changes will be written, separate from the stable 1.0 text.
Minor or unclear
A merge of PR #800 (branch 718-age-over-nn) landed in OpenID4VP; the material has no diff, so the content is unknown.
One commit, 66f5ff931301, merged pull request #800 from the branch openid/718-age-over-nn into the default branch of openid/OpenID4VP. The branch name suggests a change related to age-over-NN claims, but the material contains only the merge commit title, with no diff or PR description, so the actual effect on the specification cannot be stated.
Minor or unclear
Openid/aauth trimmed its CONTRIBUTING file and changed how meeting notes are handled.
Two commits landed on the default branch. One trims CONTRIBUTING to essentials and describes meeting notes taken by an agent. The other drops the condition that OIDF approval is needed for meeting notes. Only commit titles are available, so details are unknown. No specification or protocol content is shown as changed.
Minor or unclear
The openid/aauth repo got working-group repo files and a meeting calendar, with no specification text.
Three commits add WG repo files and a meeting calendar, add a copy button for the calendar feed address, and change the README to link to the subscribe page. These are housekeeping changes only. No protocol content is visible in the commit titles.
Minor or unclear
Three PRs merged in claims-aggregation, covering a trust model, an RFC 9207 mix-up defense and general spec edits.
The commits are merges of PR #39 (spec-edits), #40 (claims-aggregation-trust-model) and #41 (rfc9207-mix-up-defense). Only branch names are available, with no diff or PR body, so the actual text changes are unknown. The branch names suggest a trust model section and use of RFC 9207 issuer identification against mix-up attacks.
Minor or unclear
Openid/claims-aggregation merged a contributor guide and made no spec change.
Two commits landed on the default branch since late June: a contribution guidance document (PR #42) and its merge commit. The commit messages show no change to protocol text.
Minor or unclear
Openid/authzen merged PR #801 (branch iana-rfc); the material doesn't show what it changed.
One merge commit (05dc553a8c44) landed on the default branch of openid/authzen: pull request #801 from the branch openid/iana-rfc. The material gives only the commit title, with no diff or PR body. The branch name hints at IANA registration or RFC-related work, but that is a guess, so the effect on the specification is unknown. The repository has 21 open PRs and 49 merged in the last 30 days.
Minor or unclear
A merge of PR #72 (branch openid/ralph) landed on openid/federation-wallet; the material doesn't say what it changed.
The only material is one commit message, a merge of pull request #72 from the branch openid/ralph. No diff, PR description or file list is included, so the effect on the specification cannot be determined. The repository metadata shows 2 open PRs and 3 PRs merged in the last 30 days.