BCR-2026-XXX: Peer Endorsement Predicates#156
Open
ChristopherA wants to merge 8 commits intomasterfrom
Open
Conversation
Contributor
Author
Updates (Feb 4, 2026)Per reviewer feedback:
|
Contributor
Author
|
Per Wolf's feedback: removed |
Contributor
Author
Updates (2026-02-04)Renumbering
Content Changes
RelatedThis PR is part of a coordinated suite of 8 BCRs for attribution, authority, and endorsement predicates. See PR #151 for the complete overview of the suite structure. |
Contributor
Author
Signature Pattern UpdateUpdated all 8 signature examples to use the signature-with-assertions pattern from BCR-2024-009 (documented in BCR-2026-004). Examples updated:
Pattern change: Also updated note text from "double-signing pattern" to "signature-with-assertions pattern" for consistency. |
Proposes Known Values for peer endorsements in web-of-trust systems. Includes patterns guide for Schema.org, Open Badges, VC reuse. Community range 1150-1173. Seeking rough consensus; willing to use 100000+ if community prefers. Signed-off-by: Christopher Allen <ChristopherA@LifeWithAlacrity.com>
Part of coordinated suite renumbering. BCR-2026-004 (Signing Event Attestations) was inserted, shifting all subsequent numbers. Updates: - All signature examples now use double-signing pattern with 'signer' predicate per BCR-2026-004 Codepoint range unchanged: 1150-1173 Signed-off-by: Christopher Allen <ChristopherA@LifeWithAlacrity.com>
Signed-off-by: Christopher Allen <ChristopherA@LifeWithAlacrity.com>
d2a3b78 to
6fde80a
Compare
Per Wolf's recommendation: use temporary letter designations. Actual BCR numbers will be assigned at merge time. Updated all internal cross-references to XXX format. Signed-off-by: Christopher Allen <ChristopherA@LifeWithAlacrity.com>
- Add distinction note: sig:endorsement describes countersignature intent, while our endorsement predicates describe peer trust relationships - Update example from xades:ClaimedRole to sig:signerRole - Update codepoints: signer 300→800, signedOnBehalfOf 301→801 - Reference Signature Qualifiers for role and commitment predicates Signed-off-by: Christopher Allen <ChristopherA@LifeWithAlacrity.com>
Contributor
Author
|
Updates for compatibility with the new Signature Qualifiers BCR:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposes Known Values for peer endorsements in Gordian Envelopes — signed attestations from one party about another that build webs of trust.
Predicates defined:
endorserParty— The entity making the endorsementendorsementBasis— How the endorser knows the subject (direct experience, reputation, etc.)endorsementScope— What specific capability or quality is endorsedendorsementContext— Circumstances under which the endorsement appliesendorsementAcceptance— Subject's acceptance of the endorsementPlus relationship context predicates for transparency.
Codepoints: Community range 1150-1173
Includes patterns guide for leveraging existing schemas (Schema.org, Open Badges, Verifiable Credentials) before defining new predicates.
Seeking rough consensus; willing to use 100000+ range if community prefers.