Integrate enmeshed

If the content.value of an OwnIdentityAttribute changes, this can be replicated in enmeshed with this use case. It allows you to update the content and keeps a coherent history of all versions by establishing a doubly linked list, using the OwnIdentityAttribute’s parameters succeeds and succeededBy. Hence, every OwnIdentityAttribute may have exactly one predecessor and one successor. In case you shared the preceeding version of an OwnIdentityAttribute, the corresponding successor will only be shared if you decide to notify the peer about the succession.

Parameters

  • predecessorId describes the id of the OwnIdentityAttribute you want to succeed.
  • The successorContent according to the parameters of an IdentityAttribute as described in the data model, except for the owner, which is automatically set to the address of your Identity.

On Success

  • The response returns a predecessor and a successor OwnIdentityAttribute.
  • The predecessor is an updated version of the OwnIdentityAttribute belonging to predecessorId, having the succeededBy field set to the id of the successor.
  • The successor is a new OwnIdentityAttribute with the updated successorContent. Its succeeds property links to the predecessor.

On Failure

  • The response cannot be created if the predecessorId doesn’t belong to an OwnIdentityAttribute.
  • The response cannot be created if the OwnIdentityAttribute already has a successor.
  • The response cannot be created if the successorContent contains invalid changes, e.g. of the IdentityAttribute value.@type.
  • The response cannot be created if the parameters are malformed.

How to execute this use case with the Connector?

The Connector is our first-class citizen, thus we provide you with a detailed API description for every use case. This use case can be executed with the REST API of the Connector which you can Access the Connector.
Corresponding interactive API docs excerpt: