Skip to content
Snippets Groups Projects
Commit 213eddf3 authored by James Lawton's avatar James Lawton
Browse files

updated crid

parent a27a1053
No related branches found
No related tags found
No related merge requests found
Hide whitespace changes
Inline Side-by-side
blips/blip-2-researchcertificate.md
+ 9
− 11
View file @ 213eddf3
...@@ -51,8 +51,6 @@ Each owner of the token is able to augment the tokenURI field to a hosting locat ...@@ -51,8 +51,6 @@ Each owner of the token is able to augment the tokenURI field to a hosting locat
{ {
// Relevant JSON-LD context links in order to validate Verifiable Credentials according to their spec. // Relevant JSON-LD context links in order to validate Verifiable Credentials according to their spec.
"@context": ["https://www.w3.org/2018/credentials/v1", "https://w3id.org/blockcerts/schema/3.0-alpha/context.json"], "@context": ["https://www.w3.org/2018/credentials/v1", "https://w3id.org/blockcerts/schema/3.0-alpha/context.json"],
// UUID generated id corresponding to the certificate - OPTIONAL.
"id": "urn:uuid:94edcd1e-2a1d-43af-9f17-ef97816954b1",
// Credential types which declare what data to expect in the certificate. // Credential types which declare what data to expect in the certificate.
"type": ["VerifiableCredential", "BlockcertsCredential"], "type": ["VerifiableCredential", "BlockcertsCredential"],
// Entity that issued the credential, also could be characterized as a DID. // Entity that issued the credential, also could be characterized as a DID.
...@@ -61,10 +59,10 @@ Each owner of the token is able to augment the tokenURI field to a hosting locat ...@@ -61,10 +59,10 @@ Each owner of the token is able to augment the tokenURI field to a hosting locat
"issuanceDate": "2020-09-10T13:05:11.996623+00:00", "issuanceDate": "2020-09-10T13:05:11.996623+00:00",
// claim about recipient of the certificate. // claim about recipient of the certificate.
"credentialSubject": { "credentialSubject": {
// identifier for the subject of the certificate. // identifier for the subject of the certificate. Must be a resolvable URI if included - OPTIONAL
"id": "einstein@mpg.de", "id": "did:example:ebfeb1f712ebc6f1c276e12ec21",
// assertion about the subject of the certificate. // URI of the issuing party of the research object certificate
"alumniOf": { "issuingOrg": {
"id": "https://bloxberg.org" "id": "https://bloxberg.org"
} }
}, },
...@@ -88,8 +86,8 @@ Each owner of the token is able to augment the tokenURI field to a hosting locat ...@@ -88,8 +86,8 @@ Each owner of the token is able to augment the tokenURI field to a hosting locat
"verificationMethod": "ecdsa-koblitz-pubkey:0xD748BF41264b906093460923169643f45BDbC32e" "verificationMethod": "ecdsa-koblitz-pubkey:0xD748BF41264b906093460923169643f45BDbC32e"
}, },
// Generalized metadata field that can contain additional data to describe the certificate - OPTIONAL // Generalized metadata field that can contain additional data to describe the certificate - OPTIONAL
"@metadata": { "metadataJson": {
"researchObjectName": "NeuronalImpulsePatient12.csv" "authors": "Albert Einstein"
} }
} }
``` ```
...@@ -111,7 +109,7 @@ Steps to Verify Certificate: ...@@ -111,7 +109,7 @@ Steps to Verify Certificate:
</ol> </ol>
These steps ensure that the certificate is valid and secured on the bloxberg blockchain on the issuanceDate. Additional verification steps can be taken to ensure data integrity of any individual research object secured in a batch or individually: These steps ensure that the certificate is valid and secured via the bloxberg blockchain on the issuanceDate. Additional verification steps can be taken to ensure data integrity of any individual research object secured in a batch or individually:
<ol> <ol>
<li>Compute cryptographic identifier of certified research object according to function listed in variable *cidType* or the described hash if self-describing.</li> <li>Compute cryptographic identifier of certified research object according to function listed in variable *cidType* or the described hash if self-describing.</li>
<li>Compare computed value with value secured in research object certificate and ensure that they are identical.</li> <li>Compare computed value with value secured in research object certificate and ensure that they are identical.</li>
...@@ -122,6 +120,6 @@ These steps ensure that the certificate is valid and secured on the bloxberg blo ...@@ -122,6 +120,6 @@ These steps ensure that the certificate is valid and secured on the bloxberg blo
<li>Verifiable Credentials Data Model 1.0. https://www.w3.org/TR/vc-data-model/.</li> <li>Verifiable Credentials Data Model 1.0. https://www.w3.org/TR/vc-data-model/.</li>
<li>Merkle Proof Signature Suite 2019. https://w3c-ccg.github.io/lds-merkle-proof-2019/.</li> <li>Merkle Proof Signature Suite 2019. https://w3c-ccg.github.io/lds-merkle-proof-2019/.</li>
<li>International Standard Content Code. https://iscc.codes.</li> <li>International Standard Content Code. https://iscc.codes.</li>
<li>ERC-721 Non-Fungible Token Standard. https://eips.ethereum.org/EIPS/eip-721</li> <li>ERC-721 Non-Fungible Token Standard. https://eips.ethereum.org/EIPS/eip-721.</li>
<li>Multihash - Self Describing Hashes. https://multiformats.io/multihash/</li> <li>Multihash - Self Describing Hashes. https://multiformats.io/multihash/.</li>
</ol> </ol>
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment