Deploying to gh-pages from @ 42e1ea2 🚀

tutorials/concepts_public_attestation.html

@@ -182,7 +182,7 @@ <h2 id="data-model"><a class="header" href="#data-model">Data Model</a></h2>
 <p>Public Attestaions live in the DID document of their poster. A DID with a public attestation will have an extra property, "https://rdf.dock.io/alpha/2021#attestsDocumentContent". The value of that property is an IRI that is expected to point to an RDF document. Any statement contained in that document is considered to be a claim made by the DID.</p>
 <p>If <code>DID attestsDocumentContent DOC</code> then for every statement <code>X</code> in <code>DOC</code> <code>DID claims X</code>.</p>
 <p>Two IRI schemes are supported for pionting to attested documents: DIDs and ipfs links. DIDs are dereferenced and interpreted as <a href="https://www.w3.org/TR/json-ld/">json-ld</a>. Ipfs links are dereferenced and interpreted as <a href="https://www.w3.org/TR/turtle/">turtle</a> documents. The sdk makes it easy to dereferece DIDs and ipfs attestation documents but the Public Attestation concept is extendable to other types of IRI, like <a href="https://tools.ietf.org/html/draft-sporny-hashlink-06">hashlinks</a> or <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/Data_URIs">data URIs</a>.</p>
-<p>For Dock DIDs public attestation are made by <a href="https://github.com/docknetwork/sdk/blob/61cbaaf61e11cc8cc57d8582095bffafecd794b9/src/modules/did.js#L94">setting the attestation for the DID</a> on-chain. Changing the value of an attestation effectively revokes the previous attestation and issues a new one. A DIDs attestation can also be set to <code>None</code>, which is equivalent to attesting an empty claimgraph. Dock DIDs have their attestation set to <code>None</code> by default. A Dock DID with attestation set to <code>None</code> will not contain the <code>attestsDocumentContents</code> key.</p>
+<p>For Dock DIDs public attestation are made by <a href="https://github.com/docknetwork/sdk/blob/61cbaaf61e11cc8cc57d8582095bffafecd794b9/src/modules/abstract/did.js#L94">setting the attestation for the DID</a> on-chain. Changing the value of an attestation effectively revokes the previous attestation and issues a new one. A DIDs attestation can also be set to <code>None</code>, which is equivalent to attesting an empty claimgraph. Dock DIDs have their attestation set to <code>None</code> by default. A Dock DID with attestation set to <code>None</code> will not contain the <code>attestsDocumentContents</code> key.</p>
 <h3 id="example-of-a-did-attesting-to-a-document-in-ipfs"><a class="header" href="#example-of-a-did-attesting-to-a-document-in-ipfs">Example of A DID attesting to a document in ipfs</a></h3>
 <p><code>did:ex:ex</code>:</p>
 <pre><code class="language-json">{

tutorials/print.html

@@ -1005,7 +1005,7 @@ <h2 id="data-model"><a class="header" href="#data-model">Data Model</a></h2>
 <p>Public Attestaions live in the DID document of their poster. A DID with a public attestation will have an extra property, "https://rdf.dock.io/alpha/2021#attestsDocumentContent". The value of that property is an IRI that is expected to point to an RDF document. Any statement contained in that document is considered to be a claim made by the DID.</p>
 <p>If <code>DID attestsDocumentContent DOC</code> then for every statement <code>X</code> in <code>DOC</code> <code>DID claims X</code>.</p>
 <p>Two IRI schemes are supported for pionting to attested documents: DIDs and ipfs links. DIDs are dereferenced and interpreted as <a href="https://www.w3.org/TR/json-ld/">json-ld</a>. Ipfs links are dereferenced and interpreted as <a href="https://www.w3.org/TR/turtle/">turtle</a> documents. The sdk makes it easy to dereferece DIDs and ipfs attestation documents but the Public Attestation concept is extendable to other types of IRI, like <a href="https://tools.ietf.org/html/draft-sporny-hashlink-06">hashlinks</a> or <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/Data_URIs">data URIs</a>.</p>
-<p>For Dock DIDs public attestation are made by <a href="https://github.com/docknetwork/sdk/blob/61cbaaf61e11cc8cc57d8582095bffafecd794b9/src/modules/did.js#L94">setting the attestation for the DID</a> on-chain. Changing the value of an attestation effectively revokes the previous attestation and issues a new one. A DIDs attestation can also be set to <code>None</code>, which is equivalent to attesting an empty claimgraph. Dock DIDs have their attestation set to <code>None</code> by default. A Dock DID with attestation set to <code>None</code> will not contain the <code>attestsDocumentContents</code> key.</p>
+<p>For Dock DIDs public attestation are made by <a href="https://github.com/docknetwork/sdk/blob/61cbaaf61e11cc8cc57d8582095bffafecd794b9/src/modules/abstract/did.js#L94">setting the attestation for the DID</a> on-chain. Changing the value of an attestation effectively revokes the previous attestation and issues a new one. A DIDs attestation can also be set to <code>None</code>, which is equivalent to attesting an empty claimgraph. Dock DIDs have their attestation set to <code>None</code> by default. A Dock DID with attestation set to <code>None</code> will not contain the <code>attestsDocumentContents</code> key.</p>
 <h3 id="example-of-a-did-attesting-to-a-document-in-ipfs"><a class="header" href="#example-of-a-did-attesting-to-a-document-in-ipfs">Example of A DID attesting to a document in ipfs</a></h3>
 <p><code>did:ex:ex</code>:</p>
 <pre><code class="language-json">{
@@ -1873,7 +1873,7 @@ <h3 id="writing-a-blob"><a class="header" href="#writing-a-blob">Writing a Blob<
   id: blobId,
   blob: blobHexOrArray, // Contents of your blob as a hex string or byte array
 };
-const result = await dock.blob.new(blobStruct, ownerDid, didKeypair);
+const result = await dock.blob.new(blobStruct, didKeypair);
 </code></pre>
 <p>If everything worked properly <code>result</code> will indicate a successful transaction.
 We'll see how to retrieve the blob next.</p>

tutorials/tutorial_blobs_schemas.html

@@ -210,7 +210,7 @@ <h3 id="writing-a-blob"><a class="header" href="#writing-a-blob">Writing a Blob<
   id: blobId,
   blob: blobHexOrArray, // Contents of your blob as a hex string or byte array
 };
-const result = await dock.blob.new(blobStruct, ownerDid, didKeypair);
+const result = await dock.blob.new(blobStruct, didKeypair);
 </code></pre>
 <p>If everything worked properly <code>result</code> will indicate a successful transaction.
 We'll see how to retrieve the blob next.</p>