Skip to content

Commit

Permalink
Remove unused references and vendor-specific protocols.
Browse files Browse the repository at this point in the history
  • Loading branch information
@OR13
OR13 authored Oct 21, 2023
1 parent 87a4db3 commit cc5cd92
Show file tree
Hide file tree
Showing 2 changed files with 11 additions and 75 deletions.
64 changes: 2 additions & 62 deletions common.js
View file
Original file line number Diff line number Diff line change
Expand Up @@ -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/",
Expand Down Expand Up @@ -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/',
Expand All @@ -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',
Expand All @@ -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/',
Expand Down
22 changes: 9 additions & 13 deletions index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -2421,7 +2421,7 @@ <h3>Data Schemas</h3>
integrity protection mechanism. The <code>credentialSchema</code>
<a>property</a> also makes it possible to perform syntactic checking on the
<a>credential</a> and to use <a>verification</a> mechanisms such as JSON Schema
[[?VC-JSON-SCHEMA-2023]] validation.
[[?VC-JSON-SCHEMA]] validation.
</p>

<pre class="example nohighlight"
Expand Down Expand Up @@ -2458,13 +2458,13 @@ <h3>Data Schemas</h3>

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

<p class="note" >
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 <a>verification</a> mechanisms, see the Verifiable Credentials
Implementation Guidelines [[VC-IMP-GUIDE]] document.
</p>
Expand Down Expand Up @@ -3301,7 +3301,7 @@ <h3>Terms of Use</h3>
<section>
<h3>Evidence</h3>

<p class="issue" data-number="870" title="(AT RISK) Feature depends on demonstration of independent implementations">
<p class="issue" data-number="1303" title="(AT RISK) Feature depends on demonstration of independent implementations">
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
Expand Down Expand Up @@ -5047,11 +5047,7 @@ <h3>Content Integrity Protection</h3>
<p>
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.
</p>

<pre class="example nohighlight" title="Content-integrity protection for links to external data">
Expand All @@ -5064,7 +5060,7 @@ <h3>Content Integrity Protection</h3>
"type": ["VerifiableCredential", "ExampleAlumniCredential"],
"credentialSubject": {
"id": "did:example:ebfeb1f712ebc6f1c276e12ec21",
"image": <span class="highlight">"ipfs:/ipfs/QmXfrS3pHerg44zzK6QKQj6JDk8H6cMtQS7pdXbohwNQfK/image"</span>,
"image": <span class="highlight">"https://example.com/image"</span>,
"alumniOf": {
"id": "did:example:c276e12ec21ebfeb1f712ebc6f1",
"name": "Example University"
Expand Down Expand Up @@ -5719,7 +5715,7 @@ <h3>Schema</h3>
according to the <code>credentialSchema</code> <a>type</a> definition for the
<a>verifiable credential</a> and the <a>verifier's</a> own schema evaluation
criteria. For example, if the <code>credentialSchema</code>'s <code>type</code> value is
[[?VC-JSON-SCHEMA-2023]], then a <a>verifier</a> can ensure a credential's
[[?VC-JSON-SCHEMA]], then a <a>verifier</a> can ensure a credential's
data is valid against the given JSON Schema.
</p>
</section>
Expand Down Expand Up @@ -5762,7 +5758,7 @@ <h3>Base Context</h3>
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
Expand Down Expand Up @@ -6105,7 +6101,7 @@ <h3>Differences between Contexts, Types, and CredentialSchemas</h3>
<p>
The <a>verifiable credential</a> and <a>verifiable presentation</a> 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
<code>@context</code>, <code>type</code>, and <code>credentialSchema</code>
properties, and cover some of the more specific use cases where it is possible
to use these features of the data model.
Expand Down

0 comments on commit cc5cd92

Please sign in to comment.