Communication between Identities involves exchanging uploaded Files with each other, for example:

• A language school wants to send a student their language certificate.
• A university wants to send a student their certificate of enrollment.
• An applicant wants to send their curriculum vitae to a company.

These examples all represent cases where the File ought to be saved by the recipient for further use. To this end, we store the File in the form of an Attribute. In contrast, it is also possible to send a simple File without an Attribute as an attachment of a Message. However, in this case the File cannot be further used by the recipient. Thus, we only recommend to do so for Files that contain one-time-information for the recipient like a flyer.

This guide describes how an Integrator of a Connector can use a certain kind of Attribute, the IdentityFileReference, to exchange Files. To do so, the respective File must be uploaded to the Backbone first. Then, an explanation of how to share an own File with a peer follows. Also, further options for exchanging Files, such as requesting the reading of a File from a peer, are touched upon. Lastly, the scenario of transferring the ownership of a File to a peer is explained. In contrast to the former case, this way the recipient becomes the owner of the actual File, that was uploaded to the Backbone by the sender. This use case is especially important for certificates that the sender creates for the recipient.

The peer with whom a File is exchanged using Attributes can be an Integrator of another Connector or an App user. The File exchange flow described in this guide remains the same, even if some steps are performed automatically in the App.

Upload a FilePermalink

In order to be able to share a File with a peer or to transfer the ownership of a File to a peer, its content must first be uploaded to the Backbone in encrypted form. To do this, consult the documentation of the Upload own File use case. By uploading the File, it is assigned an id and a truncatedReference with which it can be identified from now on. Either of them can be specified as a parameter when executing the Get File metadata use case in order to display the metadata information of the File. In the context of exchanging Files, particular attention should be paid to the truncatedReference property of the File. All Identities that know its value can download the encrypted content of the File from the Backbone and decrypt it.

Share an Own File With a PeerPermalink

After uploading a File, a certain kind of Attribute can be used to share the value of the truncatedReference property of the File with other Identities. To be more precise, this is an IdentityAttribute that has IdentityFileReference as its value.@type. An IdentityFileReference stores the value of the truncatedReference property of the File within its value property. By sending a suitable Request, this IdentityAttribute can be shared with a peer of an already existing Relationship or in the process of establishing a Relationship. If the peer accepts the Request, a peer shared IdentityAttribute will be created for them and they will gain read access to the underlying File, that was uploaded to the Backbone. For the sender an own shared IdentityAttribute will be created.

Create an IdentityFileReferencePermalink

After uploading the File, an IdentityAttribute with an IdentityFileReference as its value.@type and the truncatedReference of the uploaded File as its value.value can be created by proceeding as described in the documentation on how to create an IdentityAttribute for yourself. The following content can be used during the creation process, with its properties validFrom, validTo and tags being optional:

{
  "content": {
    "validFrom": "<start of IdentityFileReference's validity>",
    "validTo": "<end of IdentityFileReference's validity>",
    "value": {
      "@type": "IdentityFileReference",
      "value": "<truncatedReference of File>"
    },
    "tags": ["<tag of IdentityFileReference to be created>", ...]
  }
}

If an App user uploads a File, such an IdentityAttribute with an IdentityFileReference as its value.@type and the truncatedReference of the uploaded File as its value.value is created automatically in the background. For this reason, it is directly available to the App user for sharing. Furthermore, knowledge of this automation in the App should motivate Integrators of Connectors to strive to exchange Files using Attributes in order to achieve File management compatibility between them and App users.

Share an IdentityFileReferencePermalink

After the IdentityAttribute that has IdentityFileReference as its value.@type and the truncatedReference of the uploaded File as its value.value has been created, the Integrator of the Connector must send a suitable Request to share it. More details on how to share Attributes can be found in the Share Attributes with peer scenario documentation.

Load a Referenced FilePermalink

Once the shared IdentityAttribute that has IdentityFileReference as its value.@type has been obtained, its recipient has knowledge of its value.value and thus also of the truncatedReference of the File to be shared. In order for the recipient to be authorized to download the encrypted content of the File from the Backbone and decrypt it, they must first load the metadata information of the File. This is done by executing the Load File use case and specifying the truncatedReference of the File as the required reference.

Please note that it is also possible to store the truncatedReference of a Token for the File within the value.value property of the IdentityAttribute of IdentityFileReference value.@type instead of the truncatedReference of the File itself. In this case, the Token for the File must be created beforehand. The advantage of using Tokens is that they can be personalized or password protected. When executing the Load File use case, the truncatedReference of the Token can be specified as the reference. If the Token is password protected, the password must additionally be entered for loading.

Further Options for Exchanging FilesPermalink

As for all other kinds of Attributes, the IdentityAttributes of IdentityFileReference value.@type can be read from a peer, created for a peer and proposed to a peer by proceeding as described in the corresponding scenario documentation. In addition, there is the option of updating by succession and deletion. However, the deletion of an IdentityAttribute that has IdentityFileReference as its value.@type does not additionally lead to the deletion of the associated uploaded encrypted content of the File on the Backbone. This must be done separately if required.

Utilization of a ProprietaryFileReferencePermalink

Furthermore, it is possible to represent uploaded Files within a Relationship utilizing a RelationshipAttribute that has ProprietaryFileReference as its value.@type and the truncatedReference of the File as value.value. It is advantageous to use such a RelationshipAttribute instead of an IdentityAttribute of IdentityFileReference value.@type if the File fits more into the context of the Relationship and is less attributable to a single Identity. An overview of the available options for creating a RelationshipAttribute can be found in the corresponding scenario documentation.

Transfer the Ownership of a File to a PeerPermalink

If the sender creates a File for the recipient, simply sharing the File will not be enough. That is, because the uploaded File on the Backbone will still belong to the sender. Instead, the ownership of the File needs to be transferred to the recipient. To this end, firstly the sender needs to upload the File to the Backbone. Then, an appropriate TransferFileOwnershipRequestItem must be sent to the peer, who shall become the new owner of the File. If they accept it, the ownership of the File on the Backbone will be transferred to them. Additionally, a RepositoryAttribute will be created for the recipient, whose content is an IdentityAttribute with IdentityFileReference as value.@type. Moreover, this RepositoryAttribute will be shared with the sender, i.e. an own shared IdentityAttribute will be created for the recipient and a peer shared IdentityAttribute will be created for the sender.

Request for Transferring the Ownership of a FilePermalink

The sender wants to transfer the ownership of a File to the recipient. To do so, the sender must first create a suitable Request, which they can then send to the recipient. In the following subsections, we describe the general appearance of a Request for transferring the ownership of a File.

Role of TransferFileOwnershipRequestItemPermalink

For transferring the ownership of a single File, the sender needs to insert a single RequestItem of type TransferFileOwnershipRequestItem into the items property of the Request. The sender can only transfer the ownership of a File that was already uploaded to the Backbone and is owned by themselves. The latter means that the isOwn property of the corresponding File is true. To create the TransferFileOwnershipRequestItem, the truncatedReference of the File must be inserted into its fileReference property.

To get a list of all Files that are owned by the sender, proceed as described in the Query metadata of own Files use case documentation.

Example of Transferring the Ownership of a FilePermalink

We assume that the Integrator of the sender has uploaded a File to the Backbone, whose ownership they want to transfer to the recipient. To do so, they need to insert the truncatedReference of the corresponding File into the fileReference property of the TransferFileOwnershipRequestItem. The value of the mustBeAccepted property is set to true in this example. Then, the RequestItem needs to be put into the item property of the Request for transferring the ownership of Files.

{
  "@type": "Request",
  "items": [
    {
      "@type": "TransferFileOwnershipRequestItem",
      "mustBeAccepted": true,
      "fileReference": "<truncatedReference of the File>"
    }
  ]
}

Transfer Ownership of Multiple FilesPermalink

Transferring the ownership is not limited to just a single File, but it is possible to request the transfer of ownership of multiple Files at the same time. For this purpose, several TransferFileOwnershipRequestItems or suitable RequestItemGroups can be inserted into the items property of the Request for transferring the File ownership. If you want to use a RequestItemGroup in order to transfer the ownership of multiple Files to the recipient at the same time, you must insert corresponding TranferFileOwnershipRequestItems into the items property of it.

Send and Receive the RequestPermalink

The sender that wants to transfer the ownership of a File may or may not already have a Relationship with the recipient. Depending on which is the case, a different method can be used to send the Request for transferring the ownership of a File. There are two ways to send the Request for transferring the ownership of a File to the recipient.

Request via RelationshipTemplatePermalink

If there is currently no Relationship between the sender and the recipient, this approach must be used. However, it is also possible for the sender to use a RelationshipTemplate to send a Request to the recipient if there is already an active Relationship between them. All details on how to send and receive a Request via a RelationshipTemplate in general can be found in the Requests via RelationshipTemplates guide.

Request via MessagePermalink

The sender only has the option of sending a Request to the recipient via a Message if there is already an active Relationship between them. All information on how to send and receive a Request via a Message can be found in the Requests via Messages guide.

Accept the RequestPermalink

After the recipient has received the Request for transferring the ownership of Files, they can accept it to receive the ownership of all or some of the sender’s Files. To do this, proceed as described in the Accept incoming Request use case documentation and specify the id of the received Request. Also, you need to decide and specify for each TransferFileOwnershipRequestItem contained in the Request for transferring the ownership of Files whether you want to accept or reject it.

If the recipient does not want to receive the ownership of any of the sender’s Files and, therefore, does not want to accept the Request for transferring the ownership of Files of the sender, they can reject it as a whole, too. For that, follow the instructions of the Reject incoming Request use case.

Accept a TransferFileOwnershipRequestItemPermalink

If the recipient agrees to receive the ownership of one of the sender’s Files, they can accept the associated TransferFileOwnershipRequestItem. The AcceptRequestItemParameters must be used for this. The acceptance of a TransferFileOwnershipRequestItem leads to the transfer of the ownership of the File on the Backbone. Additionally, a RepositoryAttribute will be created for the recipient, whose content is an IdentityAttribute with IdentityFileReference as value.@type. The value of the IdentityFileReference is the truncatedReference of the File that is now owned by the recipient. Also, the newly created RepositoryAttribute of the recipient will be shared with the sender, i.e. an own shared IdentityAttribute will be created for the recipient. Based on this, an appropriate AcceptResponseItem of type TransferFileOwnershipAcceptResponseItem is generated. It contains the id and the content of the created own shared IdentityAttribute in its attributeId and attribute property, respectively. This ResponseItem will appear within the items property of the Response to the Request for transferring the ownership of Files, which will be sent back to the sender.

Currently, there is no implementation for changing the actual ownership of a File that was uploaded to the Backbone. Instead, accepting a TransferFileOwnershipRequestItem downloads the corresponding File and uploads it again to the Backbone, such that the recipient is its owner. The created IdentityAttributes with value.@type IdentityFileReference reference this newly uploaded File. Consequently, after receiving the Response, the sender can delete their uploaded File if they wish to do so, without impacting the File owned by the recipient.

Reject a TransferFileOwnershipRequestItemPermalink

Even if the recipient accepts the Request for transferring the ownership of Files as a whole, it may decide not to accept the ownership of all of the sender’s Files. To be more precise, the recipient has the option of rejecting TransferFileOwnershipRequestItems that have the value false specified in their mustBeAccepted property. To reject a TransferFileOwnershipRequestItem, use the RejectRequestItemParameters. The rejection of a TransferFileOwnershipRequestItem leads to the creation of a corresponding ResponseItem of type RejectResponseItem. This will be contained within the items property of the Response to the Request for transferring the ownership of Files.

Receive the Response to the RequestPermalink

We now assume that the recipient has accepted the Request for transferring the ownership of Files of the sender. In order for the sender to receive the Response of the recipient, they need to synchronize the updates of the Backbone. Please note that this synchronization can also be automated by using the Sync Module.

To view the Response to the Request, proceed as described in the Query outgoing Requests use case documentation and use the following query parameter:

• If the Request was sent via a RelationshipTemplate: Specify <ID of RelationshipTemplate> as the value for the source.reference query parameter.
• If the Request was sent via a Message: Specify <ID of Request> as the value for the id query parameter.

The Integrator of the sender can now get the Response of the recipient from the response.content property of the result. In the items property of the Response is a TransferFileOwnershipAcceptResponseItem for each accepted TransferFileOwnershipRequestItem and a RejectResponseItem for each rejected TransferFileOwnershipRequestItem included. Note that each accepted TransferFileOwnershipRequestItem leads to the creation of an appropriate peer shared IdentityAttribute of the sender. The content and id of the LocalAttribute are the underlying attribute and attributeId of the TransferFileOwnershipAcceptResponseItem, respectively.

In case of an error, ErrorResponseItems can also be included in the Response. If the Request for transferring the ownership of Files contains a RequestItemGroup in its items property, the Response to this Request contains a corresponding ResponseItemGroup in its items property.