trustbloc / activityanchors

Activity Anchors

This repository contains the Activity Anchors specification.

activityanchors's Issues

Remove WebCAS section

The normative need for describing WebCAS in the spec has gone away with the shift to hashlinks.

Invite Witness vocabulary

• Review InviteWitness vocabulary.
• Update context definition.

Remove non-embedded form of Create

AnchorCredentialReference should be renamed

Use DID instead of publicKeyPem

Investigate replacing:

                "publicKey": {
                  "id": "https://alice.example.com/services/anchor#main-key",
                  "owner": "https://alice.example.com/services/anchor",
                  "publicKeyPem": "-----BEGIN PUBLIC KEY-----\nMIIBIjANBgkqhki....."
                },

with a DID-based public key.

Activity to notify about processing

• The Like activity is better used to signal processing status / replication from followers.
• Use Like or another term with the same semantics.
• The current like collections will now be for this purpose.

Vocabulary for witness responses to an offer

• Replace Like activity with a more specific activity
• Create collections for the new activity term.
• Add comment semantics. Add inReplyTo property.

Data model review

• Review Anchor vs AnchorEvent as the term.
• Review the custom terms previous and previousAnchor.
• Review the JSON-LD container types for previous and resources.
• Should we use a "real" namespaces identifier in resources - like did:example:multihash: instead of urn:multihash:?
• published is arguably duplicated by issuanceDate in the verifiable credential wrapper.
• Should we use base64URL in the urn:multihash identifiers? (alternatives are base58 or base32)?