From 9984cd97027f56abc6c9cf6dea5746d73718da43 Mon Sep 17 00:00:00 2001 From: Manu Sporny Date: Sun, 8 Dec 2024 12:46:51 -0500 Subject: [PATCH] Fix link to PSD2 in CR1 draft. --- transitions/2025/CR1/index.html | 85 ++++++++++++++++++++++++++++----- 1 file changed, 73 insertions(+), 12 deletions(-) diff --git a/transitions/2025/CR1/index.html b/transitions/2025/CR1/index.html index 55164e1..c523c1f 100644 --- a/transitions/2025/CR1/index.html +++ b/transitions/2025/CR1/index.html @@ -248,7 +248,7 @@ "editors": [ { "name": "Manu Sporny", - "url": "https://digitalbazaar.com/", + "url": "https://www.linkedin.com/in/manusporny/", "company": "Digital Bazaar", "companyURL": "http://digitalbazaar.com/", "w3cid": 41758 @@ -501,7 +501,7 @@

Controllable Identifier Document 1.0

Editors:
- Manu Sporny (Digital Bazaar) + Manu Sporny (Digital Bazaar)
Michael B. Jones (Invited Expert)
@@ -601,7 +601,7 @@

Controllable Identifier Document 1.0

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

+

1. Introduction

This section is non-normative.

@@ -3699,7 +3699,7 @@

Controllable Identifier Document 1.0

- + Payment services (PSD 2) and eIDAS introduce such requirements to the security context. Level of assurance frameworks are classified and defined by regulations and @@ -3930,14 +3930,69 @@

Controllable Identifier Document 1.0

-

A. Examples

This section is non-normative.

+ + +

A. IANA Considerations

This section is non-normative.

+ + +

+This section will be submitted to the Internet Engineering Steering Group +(IESG) for review, approval, and registration with IANA. +

+ +

A.1 application/cid

+ +

+This specification registers the application/cid media type specifically for +identifying documents conforming to the controllable identifier document +format. +

+ + + + + + + + + + + + + + + + + + + + + + + + + +
Type name: application
Subtype name: controller
Required parameters: None
Encoding considerations: +Resources that use the application/cid media type are required to conform to +all of the requirements for the application/json media type and are therefore +subject to the same encoding considerations specified in Section 11 of +The JavaScript Object Notation (JSON) Data Interchange Format. +
Security considerations: As defined in the Controller Documents 1.0.
Contact: +W3C Verifiable Credentials Working Group +public-vc-wg@w3.org +
+ +
+
+ +

B. Examples

This section is non-normative.

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

-

A.1 Multikey Examples

This section is non-normative.

+

B.1 Multikey Examples

This section is non-normative.

@@ -4032,7 +4087,7 @@

Controllable Identifier Document 1.0

}
-

A.2 JsonWebKey Examples

This section is non-normative.

+

B.2 JsonWebKey Examples

This section is non-normative.

@@ -4159,7 +4214,7 @@

Controllable Identifier Document 1.0

-

B. Revision History

This section is non-normative.

+

C. Revision History

This section is non-normative.

@@ -4178,7 +4233,7 @@

Controllable Identifier Document 1.0

-

C. Acknowledgements

This section is non-normative.

+

D. Acknowledgements

This section is non-normative.

@@ -4299,7 +4354,7 @@

Controllable Identifier Document 1.0

-

D. References

D.1 Normative references

+

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/ @@ -4336,9 +4391,11 @@

Controllable Identifier Document 1.0

[XMLSCHEMA11-2]
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/
-

D.2 Informative references

+

E.2 Informative references

-
[DID-CORE]
+
[CONTROLLER-DOCUMENT]
+ Controller Documents 1.0. Manu Sporny; Michael Jones. W3C. 28 October 2024. W3C Working Draft. URL: https://www.w3.org/TR/controller-document/ +
[DID-CORE]
Decentralized Identifiers (DIDs) v1.0. Manu Sporny; Amy Guy; Markus Sabadello; Drummond Reed. W3C. 19 July 2022. W3C Recommendation. URL: https://www.w3.org/TR/did-core/
[DID-USE-CASES]
Use Cases and Requirements for Decentralized Identifiers. Joe Andrieu; Phil Archer; Kim Duffy; Ryan Grant; Adrian Gropper. W3C. 17 March 2021. W3C Working Group Note. URL: https://www.w3.org/TR/did-use-cases/ @@ -4350,6 +4407,8 @@

Controllable Identifier Document 1.0

Privacy by Design. Ann Cavoukian. Information and Privacy Commissioner. 2011. URL: https://iapp.org/media/pdf/resource_center/pbd_implement_7found_principles.pdf
[RFC3552]
Guidelines for Writing RFC Text on Security Considerations. E. Rescorla; B. Korver. IETF. July 2003. Best Current Practice. URL: https://www.rfc-editor.org/rfc/rfc3552 +
[RFC7159]
+ The JavaScript Object Notation (JSON) Data Interchange Format. T. Bray, Ed. IETF. March 2014. Proposed Standard. URL: https://www.rfc-editor.org/rfc/rfc7159
[TURTLE]
RDF 1.1 Turtle. Eric Prud'hommeaux; Gavin Carothers. W3C. 25 February 2014. W3C Recommendation. URL: https://www.w3.org/TR/turtle/
[VC-DATA-INTEGRITY]
@@ -4539,6 +4598,8 @@

Controllable Identifier Document 1.0

§ 6.5 Subject Classification (2) (3) (4)
  • § 6.6 Service Privacy (2) (3) (4) (5) (6) +
  • + § A.1 application/cid