diff --git a/transitions/2025/CR1/index.html b/transitions/2025/CR1/index.html index 8568042..71effde 100644 --- a/transitions/2025/CR1/index.html +++ b/transitions/2025/CR1/index.html @@ -42,11 +42,11 @@ .dfn-panel li{margin-left:1em} .dfn-panel.docked{position:fixed;left:.5em;top:unset;bottom:2em;margin:0 auto;max-width:calc(100vw - .75em * 2 - .5em - .2em * 2);max-height:30vh;overflow:auto} - + Controlled Identifiers (CIDs) v1.0 - - - + + + - - - - + + + + @@ -506,7 +506,7 @@

-

Controlled Identifiers (CIDs) v1.0

+

Controlled Identifiers (CIDs) v1.0

W3C Candidate Recommendation Snapshot

More details about this document @@ -519,21 +519,21 @@

Controlled Identifiers (CIDs) v1.0

Latest editor's draft:
https://w3c.github.io/cid/
History:
- Commit history + Publication history
- +
Implementation report:
https://w3c.github.io/cid/implementations/1.0/
- - - + + +
Editors:
Manu Sporny (Digital Bazaar)
Michael B. Jones (Invited Expert)
- +
Authors:
Dave Longley (Digital Bazaar)
@@ -553,7 +553,7 @@

Controlled Identifiers (CIDs) v1.0

new issue, open issues)
public-vc-wg@w3.org with subject line [cid-1.0] … message topic … (archives)
- +
Related Specifications
Decentralized Identifiers v1.0
@@ -565,13 +565,13 @@

Controlled Identifiers (CIDs) v1.0

- - + +

Controlled Identifiers (CIDs) v1.0

This document was published by the Verifiable Credentials Working Group as a Candidate Recommendation Snapshot using the - Recommendation track. + Recommendation track.

Publication as a Candidate Recommendation does not imply endorsement by W3C and its Members. A Candidate Recommendation Snapshot has received wide review, is intended to @@ -623,13 +623,13 @@

Controlled Identifiers (CIDs) v1.0

This Candidate Recommendation is not expected to advance to Proposed Recommendation any earlier than 28 February 2025.

- + This document was produced by a group operating under the W3C Patent Policy. - - + + W3C maintains a public list of any patent disclosures made in connection with the deliverables of @@ -639,14 +639,14 @@

Controlled Identifiers (CIDs) v1.0

Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy. - +

This document is governed by the 03 November 2023 W3C Process Document.

1. Introduction

This section is non-normative.

- +

Controlled identifier documents identify a subject and provide verification methods that express public cryptographic material, such as public keys, @@ -688,7 +688,7 @@

Controlled Identifiers (CIDs) v1.0

1.1 Use Cases

- +

The use cases below illustrate the need for this specification. While many other related use cases exist, such as those in Use Cases and Requirements for Decentralized Identifiers @@ -697,7 +697,7 @@

Controlled Identifiers (CIDs) v1.0

Globally Unique Identifiers

- +

Lemmy runs multiple enterprise portals that manage large amounts of sensitive @@ -709,7 +709,7 @@

Controlled Identifiers (CIDs) v1.0

Cryptographic Verification

- +

Lemmy would like to ensure that his customers prove control over their @@ -720,7 +720,7 @@

Controlled Identifiers (CIDs) v1.0

Cryptographic Purpose

- +

Stef, who operates a high security service, would like to ensure that certain @@ -731,7 +731,7 @@

Controlled Identifiers (CIDs) v1.0

Service Engagement

- +

Marge, a software developer, would like to publicly advertise ways in which @@ -741,7 +741,7 @@

Controlled Identifiers (CIDs) v1.0

Extensibility

- +

Cory, a systems architect, would like to extend the use cases described in this @@ -751,7 +751,7 @@

Controlled Identifiers (CIDs) v1.0

Issue and Present Claims

- +

Neru would like to issue digital credentials on behalf of her company that @@ -765,7 +765,7 @@

Controlled Identifiers (CIDs) v1.0

1.2 Requirements

- +

The following requirements are derived from the use cases described earlier in @@ -869,7 +869,7 @@

Controlled Identifiers (CIDs) v1.0

1.4 Terminology

- +

This section defines the terms used in this specification. A link to the relevant @@ -976,7 +976,7 @@

Controlled Identifiers (CIDs) v1.0

2. Data Model

- +

A controlled identifier document specifies one or more relationships between @@ -1041,7 +1041,7 @@

Controlled Identifiers (CIDs) v1.0

2.1 Controlled Identifier Documents

- +

The following sections define the properties in a controlled identifier document, @@ -1168,7 +1168,7 @@

Controlled Identifiers (CIDs) v1.0

2.1.1 Subjects

- +

A subject is expressed using the id property in a controlled identifier document. The value of an id property is referred to as an identifier. @@ -1237,7 +1237,7 @@

Controlled Identifiers (CIDs) v1.0

2.1.2 Controllers

- +

A controller of a controlled identifier document is any entity capable of making changes to that @@ -1348,7 +1348,7 @@

Controlled Identifiers (CIDs) v1.0

2.1.3 Also Known As

- +

A subject can have multiple identifiers that are used for different purposes @@ -1415,7 +1415,7 @@

Controlled Identifiers (CIDs) v1.0

2.1.4 Services

- +

Services are used in controlled identifier documents to express ways of @@ -1510,7 +1510,7 @@

Controlled Identifiers (CIDs) v1.0

2.2 Verification Methods

- +

A controlled identifier document can express verification methods, such as cryptographic public keys, which can be used to verify proofs, @@ -1659,7 +1659,7 @@

Controlled Identifiers (CIDs) v1.0

2.2.1 Verification Material

- +

Verification material is any information that is used by a process that applies @@ -1733,7 +1733,7 @@

Controlled Identifiers (CIDs) v1.0

2.2.2 Multikey

- +

The Multikey data model is a specific type of verification method that encodes key types into a single binary stream that is then encoded as a @@ -1927,7 +1927,7 @@

Controlled Identifiers (CIDs) v1.0

2.2.3 JsonWebKey

- +

The JSON Web Key (JWK) data model is a specific type of verification method that uses the JWK specification [RFC7517] to encode key types into a @@ -2053,7 +2053,7 @@

Controlled Identifiers (CIDs) v1.0

2.2.4 Referring to Verification Methods

- +

Verification methods can be embedded in or referenced from properties associated with various verification relationships as described in @@ -2096,7 +2096,7 @@

Controlled Identifiers (CIDs) v1.0

2.3 Verification Relationships

- +

A verification relationship is an expression that one or more @@ -2133,7 +2133,7 @@

Controlled Identifiers (CIDs) v1.0

2.3.1 Authentication

- +

The authentication verification relationship is used to specify how the @@ -2206,7 +2206,7 @@

Controlled Identifiers (CIDs) v1.0

2.3.2 Assertion

- +

The assertionMethod verification relationship is used to @@ -2257,7 +2257,7 @@

Controlled Identifiers (CIDs) v1.0

2.3.3 Key Agreement

- +

The keyAgreement verification relationship is used to @@ -2319,7 +2319,7 @@

Controlled Identifiers (CIDs) v1.0

2.3.4 Capability Invocation

- +

The capabilityInvocation verification relationship is used @@ -2385,7 +2385,7 @@

Controlled Identifiers (CIDs) v1.0

2.3.5 Capability Delegation

- +

The capabilityDelegation verification relationship is used to specify a @@ -2456,7 +2456,7 @@

Controlled Identifiers (CIDs) v1.0

2.4 Multibase

- +

A Multibase value encodes a binary value as a @@ -2519,7 +2519,7 @@

Controlled Identifiers (CIDs) v1.0

2.5 Multihash

- +

A Multihash value starts with a binary header, which includes 1) an identifier @@ -2596,11 +2596,11 @@

Controlled Identifiers (CIDs) v1.0

3. Algorithms

- +

This section defines algorithms used by this specification including -instructions on the following: how to base-encode and base-decode values; +instructions on the following: how to base-encode and base-decode values; how to safely retrieve verification methods; how to retrieve document fragments; and how to produce descriptions of processing errors over HTTP channels. Alternatives to the algorithms provided in this section MAY be @@ -2608,7 +2608,7 @@

Controlled Identifiers (CIDs) v1.0

3.1 Base Encode

- +

The following algorithm specifies how to encode an array of bytes, where each @@ -2754,7 +2754,7 @@

Controlled Identifiers (CIDs) v1.0

3.2 Base Decode

- +

The following algorithm specifies how to decode an array of bytes, where each @@ -2910,7 +2910,7 @@

Controlled Identifiers (CIDs) v1.0

3.3 Retrieve Verification Method

- +

The following algorithm specifies how to safely retrieve a verification method, @@ -3059,7 +3059,7 @@

Controlled Identifiers (CIDs) v1.0

3.4 Fragment Resolution

- +

The following algorithm specifies how to retrieve the portion of a document that @@ -3102,7 +3102,7 @@

Controlled Identifiers (CIDs) v1.0

3.5 Processing Errors

- +

The algorithms described in this specification throw specific types of errors. @@ -3165,7 +3165,7 @@

Controlled Identifiers (CIDs) v1.0

4. Contexts and Vocabularies

- +
Issue 3: (AT RISK) Hash values might change during Candidate Recommendation

This section lists cryptographic hash values that might change during the @@ -3174,7 +3174,7 @@

Controlled Identifiers (CIDs) v1.0

4.1 Vocabulary

- +

The terms defined in this specification are also part of the RDF vocabulary namespace [RDF-CONCEPTS] @@ -3241,7 +3241,7 @@

Controlled Identifiers (CIDs) v1.0

4.2 JSON-LD context

- +

Implementations that perform JSON-LD processing MUST treat the following JSON-LD context URL as already resolved, where the resolved document matches @@ -3283,7 +3283,7 @@

Controlled Identifiers (CIDs) v1.0

4.2.1 Context Injection

- +

The @context property is used to ensure that implementations are using the same semantics when terms in this specification are processed. For example, this @@ -3336,14 +3336,14 @@

Controlled Identifiers (CIDs) v1.0

4.3 Datatypes

- +

This section defines datatypes that are used by this specification.

4.3.1 The multibase Datatype

- +

Multibase-encoded strings are used to encode binary @@ -3392,7 +3392,7 @@

Controlled Identifiers (CIDs) v1.0

5. Security Considerations

This section is non-normative.

- +

This section contains a variety of security considerations that people using @@ -3405,7 +3405,7 @@

Controlled Identifiers (CIDs) v1.0

5.1 Proving Control and Binding

- +

Binding an entity in the digital world or the physical world to an identifier, to @@ -3417,7 +3417,7 @@

Controlled Identifiers (CIDs) v1.0

5.1.1 Proving Control of an Identifier and/or Controlled Identifier Document

- +

Proving control over an identifier and/or a controlled identifier document is useful @@ -3432,7 +3432,7 @@

Controlled Identifiers (CIDs) v1.0

5.1.2 Binding to Physical Identity

- +

An identifier or controlled identifier document do not inherently carry any @@ -3461,7 +3461,7 @@

Controlled Identifiers (CIDs) v1.0

5.2 Identifier Ambiguity

- +

Even in cases where the subject referred to by an identifier proves control, the interpretation of the subject remains contextual and @@ -3549,7 +3549,7 @@

Controlled Identifiers (CIDs) v1.0

5.3 Key and Signature Expiration

- +

In a decentralized architecture, there might not be centralized authorities to @@ -3573,7 +3573,7 @@

Controlled Identifiers (CIDs) v1.0

5.4 Verification Method Rotation

- +

Rotation is a management process that enables the secret cryptographic material @@ -3641,7 +3641,7 @@

Controlled Identifiers (CIDs) v1.0

5.5 Verification Method Revocation

- +

Revocation is a management process that enables the secret cryptographic @@ -3725,7 +3725,7 @@

Controlled Identifiers (CIDs) v1.0

5.5.1 Revocation Semantics

- +

Although verifiers might choose not to accept proofs or signatures from a @@ -3763,7 +3763,7 @@

Controlled Identifiers (CIDs) v1.0

5.6 Choosing a Multiformat

- +

Multiformats enable self-describing @@ -3795,7 +3795,7 @@

Controlled Identifiers (CIDs) v1.0

5.7 Encrypted Data in Controlled Identifier Documents

- +

Encryption algorithms have been known to fail due to advances in cryptography and computing power. Implementers are advised to assume that any encrypted data @@ -3821,7 +3821,7 @@

Controlled Identifiers (CIDs) v1.0

5.8 Content Integrity Protection

- +

Controlled identifier documents that include links to external machine-readable content such as images, web pages, or schemas are vulnerable to tampering. It is @@ -3842,7 +3842,7 @@

Controlled Identifiers (CIDs) v1.0

5.9 Integrity Protection of Controllers

- +

As described in Section 2.1.2 Controllers, this specification includes a @@ -3873,7 +3873,7 @@

Controlled Identifiers (CIDs) v1.0

5.10 Level of Assurance

- +

Additional information about the security context of authentication events is @@ -3912,7 +3912,7 @@

Controlled Identifiers (CIDs) v1.0

5.11 Service Endpoints for Authentication and Authorization

- +

If a controlled identifier document publishes a service intended for authentication @@ -3926,7 +3926,7 @@

Controlled Identifiers (CIDs) v1.0

6. Privacy Considerations

This section is non-normative.

- +

Since controlled identifier documents are designed to be administered directly by @@ -3942,7 +3942,7 @@

Controlled Identifiers (CIDs) v1.0

6.1 Keep Personal Data Private

- +

If a controlled identifier document is about a specific individual and is @@ -3959,7 +3959,7 @@

Controlled Identifiers (CIDs) v1.0

6.2 Relationship to the Same-Origin Policy

- +

The @@ -3987,7 +3987,7 @@

Controlled Identifiers (CIDs) v1.0

- +

Identifiers can be used for unwanted correlation. Controllers can @@ -4002,7 +4002,7 @@

Controlled Identifiers (CIDs) v1.0

6.4 Controlled Identifier Document Correlation Risks

- +

The anti-correlation protections of pairwise identifiers are easily defeated @@ -4016,7 +4016,7 @@

Controlled Identifiers (CIDs) v1.0

6.5 Subject Classification

- +

It is dangerous to add properties to the controlled identifier document that can be used to indicate, explicitly or through inference, what type or nature @@ -4046,7 +4046,7 @@

Controlled Identifiers (CIDs) v1.0

6.6 Service Privacy

- +

The ability for a controller to optionally express at least one service in the controlled identifier document increases their control and agency. Each additional endpoint in the controlled identifier document adds privacy risk either @@ -4076,7 +4076,7 @@

Controlled Identifiers (CIDs) v1.0

7. Accessibility Considerations

- +

The following section describes accessibility considerations that developers implementing this specification are urged to consider in order to ensure that @@ -4089,7 +4089,7 @@

Controlled Identifiers (CIDs) v1.0

7.1 Presenting Time Values

- +

This specification enables the expression of dates and times related to the validity period of proofs. This information might be indirectly @@ -4116,10 +4116,10 @@

Controlled Identifiers (CIDs) v1.0

- +

A. IANA Considerations

This section is non-normative.

- +

This section will be submitted to the Internet Engineering Steering Group @@ -4127,7 +4127,7 @@

Controlled Identifiers (CIDs) v1.0

A.1 application/cid

- +

This specification registers the application/cid media type specifically for identifying documents conforming to the controlled identifier document @@ -4181,14 +4181,14 @@

Controlled Identifiers (CIDs) v1.0

B. Examples

This section is non-normative.

- +

This section contains more detailed examples of the concepts introduced in the specification.

B.1 Multikey Examples

This section is non-normative.

- +

This section contains various Multikey examples that might be useful for @@ -4293,7 +4293,7 @@

Controlled Identifiers (CIDs) v1.0

B.2 JsonWebKey Examples

This section is non-normative.

- +

This section contains various JsonWebKey examples that might be useful for @@ -4417,10 +4417,10 @@

Controlled Identifiers (CIDs) v1.0

- +

C. Revision History

This section is non-normative.

- +

This section contains the substantive changes that have been made to this @@ -4456,7 +4456,7 @@

Controlled Identifiers (CIDs) v1.0

D. Acknowledgements

This section is non-normative.

- +

The specification authors would like to thank the contributors to the @@ -4574,10 +4574,10 @@

Controlled Identifiers (CIDs) v1.0

- +

E. References

E.1 Normative references

- +
[DID-EXTENSIONS-PROPERTIES]
DID Document Property Extensions. Manu Sporny; Markus Sabadello. W3C. 19 November 2024. W3C Working Group Note. URL: https://www.w3.org/TR/did-extensions-properties/
[INFRA]
@@ -4614,7 +4614,7 @@

Controlled Identifiers (CIDs) v1.0

W3C XML Schema Definition Language (XSD) 1.1 Part 2: Datatypes. David Peterson; Sandy Gao; Ashok Malhotra; Michael Sperberg-McQueen; Henry Thompson; Paul V. Biron et al. W3C. 5 April 2012. W3C Recommendation. URL: https://www.w3.org/TR/xmlschema11-2/

E.2 Informative references

- +
[CID]
Controlled Identifier Document v1.0. Manu Sporny; Dave Longley; Markus Sabadello; Drummond Reed; Orie Steele; Christopher Allen; Michael B. Jones. W3C Verifiable Credentials Working Group. W3C Candidate Recommendation. URL: https://www.w3.org/TR/cid/
[DID-CORE]
@@ -4648,99 +4648,99 @@

Controlled Identifiers (CIDs) v1.0

Permalink - +

Referenced in: