From cc5cd920acbbc88481993323dacfdaa699686896 Mon Sep 17 00:00:00 2001 From: Orie Steele Date: Sat, 21 Oct 2023 14:54:11 -0500 Subject: [PATCH] Remove unused references and vendor-specific protocols. --- common.js | 64 ++---------------------------------------------------- index.html | 22 ++++++++----------- 2 files changed, 11 insertions(+), 75 deletions(-) diff --git a/common.js b/common.js index b51ca0e52..481be3ef6 100644 --- a/common.js +++ b/common.js @@ -5,15 +5,6 @@ var vcwg = { // Add as the respecConfig localBiblio variable // Extend or override global respec references localBiblio: { - "REST": { - title: "Architectural Styles and the Design of Network-based Software Architectures", - date: "2000", - href: "http://www.ics.uci.edu/~fielding/pubs/dissertation/", - authors: [ - "Fielding, Roy Thomas" - ], - publisher: "University of California, Irvine." - }, "VC-SPECS": { title: "Verifiable Credential Specifications Directory", href: "https://w3c.github.io/vc-specs-dir/", @@ -44,38 +35,6 @@ var vcwg = { status: "WD", publisher: "Verifiable Credentials Working Group" }, - "LDP-REGISTRY": { - title: "Linked Data Cryptographic Suite Registry", - href: "https://w3c-ccg.github.io/ld-cryptosuite-registry/", - authors: [ - "Manu Sporny", - "Drummond Reed", - "Orie Steele" - ], - status: "CG-DRAFT", - publisher: "Credentials Community Group" - }, - // aliases to known references - "HTTP-SIGNATURES": { - aliasOf: "http-signatures" - }, - "MACAROONS": { - title: 'Macaroons', - // TODO: create spec - href: 'http://macaroons.io/', - authors: ['Arnar Birgisson', 'Joe Gibbs Politz', 'Úlfar Erlingsson', - 'Ankur Taly', 'Michael Vrable', 'Mark Lentczner'], - status: 'unofficial', - publisher: 'Credentials Community Group' - }, - 'OPEN-BADGES': { - title: 'Open Badges', - href: 'https://github.com/openbadges/openbadges-specification', - authors: ['Brian Brennan', 'Mike Larsson', 'Chris McAvoy', - 'Nate Otto', 'Kerri Lemoie'], - status: 'BA-DRAFT', - publisher: 'Badge Alliance Standard Working Group' - }, 'RDF-NORMALIZATION': { title: 'RDF Dataset Normalization', href: 'http://json-ld.github.io/normalization/spec/', @@ -96,20 +55,8 @@ var vcwg = { status: 'ED', publisher: 'Credentials Community Group' }, - 'HASHLINK': { - title: 'Cryptographic Hyperlinks', - href: 'https://datatracker.ietf.org/doc/draft-sporny-hashlink/', - authors: ['Manu Sporny'], - status: 'Internet-Draft', - publisher: 'Internet Engineering Task Force (IETF)' - }, - 'IPFS': { - title: 'InterPlanetary File System (IPFS)', - href: 'https://en.wikipedia.org/wiki/InterPlanetary_File_System', - publisher: 'Wikipedia' - }, - 'VC-JSON-SCHEMA-2023': { - title: 'Verifiable Credentials JSON Schema 2023', + 'VC-JSON-SCHEMA': { + title: 'Verifiable Credentials JSON Schema Specification', href: 'https://www.w3.org/TR/vc-json-schema/', authors: ['Gabe Cohen', 'Orie Steele'], status: 'FPWD', @@ -122,13 +69,6 @@ var vcwg = { status: 'WD', publisher: 'W3C JSON-LD 1.1 Working Group' }, - 'VC-JWT': { - title: 'Securing Verifiable Credentials using JSON Web Tokens', - href: 'https://w3c.github.io/vc-jwt/', - authors: ['Orie Steele', 'Michael Jones'], - status: 'ED', - publisher: 'W3C Verifiable Credentials Working Group' - }, 'VC-SPECS': { title: 'Verifiable Credentials Specifications Directory', href: 'https://w3c.github.io/vc-specs-dir/', diff --git a/index.html b/index.html index c61928413..e90ba2830 100644 --- a/index.html +++ b/index.html @@ -2421,7 +2421,7 @@

Data Schemas

integrity protection mechanism. The credentialSchema property also makes it possible to perform syntactic checking on the credential and to use verification mechanisms such as JSON Schema -[[?VC-JSON-SCHEMA-2023]] validation. +[[?VC-JSON-SCHEMA]] validation. 

Data Schemas
 
         

 In the example above, the issuer is specifying a
-credentialSchema, which points to a [[?VC-JSON-SCHEMA-2023]] file that
+credentialSchema, which points to a [[?VC-JSON-SCHEMA]] file that
 can be used by a verifier to determine if the
 verifiable credential is well formed.
         

 
         

-For information about linkages to JSON Schema [[?VC-JSON-SCHEMA-2023]] or other
+For information about linkages to JSON Schema [[?VC-JSON-SCHEMA]] or other
 optional verification mechanisms, see the Verifiable Credentials
 Implementation Guidelines [[VC-IMP-GUIDE]] document.
         

@@ -3301,7 +3301,7 @@ 
Terms of Use

       

         
Evidence

 
-        

+        

 This feature is at risk and will be removed from the specification if at least
 two independent, interoperable implementations are not demonstrated for a
 single extension type by the end of the Candidate Recommendation Phase. If
@@ -5047,11 +5047,7 @@ 
Content Integrity Protection

         

 While this specification does not recommend any specific content integrity
 protection, document authors who want to ensure links to content are integrity
-protected are advised to use URL schemes that enforce content integrity. Two
-such schemes are the [[HASHLINK]] specification and the [[IPFS]]. The example
-below transforms the previous example and adds content integrity protection to
-the JSON-LD Contexts using the [[HASHLINK]] specification, and content integrity
-protection to the image by using an [[IPFS]] link.
+protected are advised to use URL schemes that enforce content integrity.
         

 
         
@@ -5064,7 +5060,7 @@ 
Content Integrity Protection

   "type": ["VerifiableCredential", "ExampleAlumniCredential"],
   "credentialSubject": {
     "id": "did:example:ebfeb1f712ebc6f1c276e12ec21",
-    "image": "ipfs:/ipfs/QmXfrS3pHerg44zzK6QKQj6JDk8H6cMtQS7pdXbohwNQfK/image",
+    "image": "https://example.com/image",
     "alumniOf": {
       "id": "did:example:c276e12ec21ebfeb1f712ebc6f1",
       "name": "Example University"
@@ -5719,7 +5715,7 @@ 
Schema

 according to the credentialSchema type definition for the
 verifiable credential and the verifier's own schema evaluation
 criteria. For example, if the credentialSchema's type value is
-[[?VC-JSON-SCHEMA-2023]], then a verifier can ensure a credential's
+[[?VC-JSON-SCHEMA]], then a verifier can ensure a credential's
 data is valid against the given JSON Schema.
         

       

@@ -5762,7 +5758,7 @@ 
Base Context

 JSON-LD Context to be either stabilized, or removed, before the publication of
 this specification as a Proposed Recommendation. While that means that this
 specification could be delayed if dependencies such as [[?VC-DATA-INTEGRITY]],
-[[?VC-JOSE-COSE]], SD-JWT, [[?VC-JSON-SCHEMA-2023]], or status list
+[[?VC-JOSE-COSE]], SD-JWT, [[?VC-JSON-SCHEMA]], or status list
 do not enter the Proposed Recommendation phase around the same time frame, the
 Working Group is prepared to remove the dependencies if an undue burden is
 placed on transitioning to the Recommendation phase. This is a calculated
@@ -6105,7 +6101,7 @@ 
Differences between Contexts, Types, and CredentialSchemas

         

 The verifiable credential and verifiable presentation data models
 leverage a variety of underlying technologies including [[JSON-LD]] and
-[[?VC-JSON-SCHEMA-2023]]. This section will provide a comparison of the
+[[?VC-JSON-SCHEMA]]. This section will provide a comparison of the
 @context, type, and credentialSchema
 properties, and cover some of the more specific use cases where it is possible
 to use these features of the data model.