Commit 2e36360e authored by taco@waag.org's avatar taco@waag.org
Browse files

Update documentation/pop-protocol.v0.md

parent 975a0146
......@@ -27,7 +27,9 @@ data-pop-<VERSION>-<ID>-<CATEGORY>
To be complete, all supported data attributes for v0 literally are:
* data-pop-v0-id-title * data-pop-v0-id-abstract * data-pop-v0-id-author
* data-pop-v0-id-title
* data-pop-v0-id-abstract
* data-pop-v0-id-author
* data-pop-v0-id-body
* data-pop-v0-id-img
......@@ -47,7 +49,7 @@ In pop v0 we follow these steps for signing each separate fragment:
- Base64 encode the signature object as the signature string. (So that a fragment can be easily annotated with one value)
- Put the signature string as a value in a pop data attribute (e.g. data-pop-v0-id-body or data-pop-v0-id-img)
A javascript function (pop_sign) can be found [here](https://gitlab.waag.org/code/proof_of_provenance/-/blob/main/src/signing-frontend/pop.js) .
A javascript function (pop_sign) can be found [here](https://gitlab.waag.org/code/proof_of_provenance/-/blob/main/src/signing-frontend/pop.js).
#### Verification
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment