This section lists URL values that might change during the Candidate -Recommendation phase based on migration of documents to the W3C Technical -Reports namespace and implementer feedback that requires the referenced URLs to -be modified. +Recommendation phase based on migration of documents to time-stamped locations, +migration of documents to the W3C Technical Reports namespace, and/or +implementer feedback that requires the referenced URLs to be modified.
-Implementations MUST ensure that the following vocabulary URLs used in the base -context ultimately resolve to the following files, which are normative: +Implementations that depend on RDF vocabulary processing MUST ensure that the +following vocabulary URLs used in the base context ultimately resolve to the +following files, which are normative. Other semantically equivalent +serializations of the vocabulary files MAY be used by implementations. +Cryptographic hashes are provided for all content to ensure that developers can +verify that the contents of each file are correct.
| URL | -Media Type | -Content | +URL and Media Type | +Content and Hashes |
|---|---|---|---|---|
|
-https://www.w3.org/2018/credentials#
+https://www.w3.org/2018/credentials# +`application/ld+json` |
-text/html - | -
-https://www.w3.org/2018/credentials/index.html
+https://www.w3.org/2018/credentials/index.jsonld +sha256: `z52TgKqh2nqTCuACI8lCvhRdjwxQjeVmuOMCDCEijq4=` +sha3-512: m8Ss+jgZiyL2Ws/ICJcWjHFd9PccJWsXPvMatBOhrH
|
||
|
-https://www.w3.org/2018/credentials#
+https://w3id.org/security# +`application/ld+json` |
-application/ld+json - | --https://www.w3.org/2018/credentials/index.jsonld - | -||
| -https://schema.org/ - | --text/html - | --https://schema.org/ - | -||
| -https://schema.org/ - | --application/ld+json - | --https://schema.org/version/latest/schemaorg-current-https.jsonld - | -||
| -https://w3id.org/security# - | --text/html - | --https://w3c.github.io/vc-data-integrity/vocab/security/vocabulary.html - | -||
| -https://w3id.org/security# - | --application/ld+json - | -
-https://w3c.github.io/vc-data-integrity/vocab/security/vocabulary.jsonld
+https://w3c.github.io/vc-data-integrity/vocab/security/vocabulary.jsonld +sha256: `LEaoTyf796eTaSlYWjfPe3Yb+poCW9TjWYTbFDmC0tc=` +sha3-512: f4DhJ3xhT8nT+GZ8UUZi4QC+HT//wXE2fRTgUP4UNw
|
-The URLs listed above that start with -`https://w3c.github.io/vc-data-integrity/vocab/security/` are expected to change -to `https://www.w3.org/ns/security/` or an equally normative and archived -location under W3C control. +
+It is possible to confirm the cryptographic digests listed above by running the +following command from a modern Unix command interface line: +`curl -sL -H "Accept: <MEDIA_TYPE>" <DOCUMENT_URL> | openssl dgst -<DIGEST_ALGORITHM> -binary | openssl base64 -nopad -a`
--The Working Group is currently discussing how it might want to normatively -refer to the vocabulary files that are under the control of the Working Group. -Current options are: inclusion of the files directly into the specification or -publishing the files in W3C TR space and referring to them by using a -cryptographic hash. +
+Implementers and document authors might note that cryptographic digests for +`schema.org` are not provided. This is because the `schema.org` vocabulary +undergoes regular changes; any digest provided would be out of date within +weeks of publication. The Working Group discussed this concern and concluded +that the vocabulary terms from `schema.org`, that are used by this +specification, have been stable for years and are highly unlikely to change in +their semantic meaning.