Attribute Document Associations

Created by

Remus Golgot

Last updated Jan 17, 2019

Attribute - Document Associations

  1. Business
  • A "document" is considered to be any attribute that is of data_type "file"

  • A document attribute can be used just like any other attribute, across all the business flows

  • An association is a logical relationship between attributes, representing physical evidence of one of them. Because of this :

    • A non-document attribute cannot be associated to any attribute

    • For Example : First Name → Passport

      • The First Name is not physical evidence of the value of the passport.

      • Instead, the association should be made the other way around : Passport → First Name

  • A non-file type attribute may be the target of any number of associations, at any point in time after the creation of that attribute

  • A document can hold multiple attribute associations

  • A document can be associated with another document

  • The owner of the document associated with an attribute must be the same as the owner of the associated attribute

  • The following business rules are enforced for any attributes that have types which require documents (this configuration is made at attribute type level)

    • RULE : An attribute that requires an associated document but that is not associated with any document cannot be validated

      • because it is not validated, it also cannot be used as part of the consumption or identity use flows
    • RULE : (TBD) When a file type document is updated, all the associated attributes should become inactive somehow

      • This prohibits attributes of certain types to be used without an active underlying document associated
  1. Actions

Attribute Creation

  • Associations towards existing attributes can be specified during attribute creation ( reduces fee costs )
  • After creation, additional changes can be made to the associations list with the Update Attribute operation

Update Attribute

  • During this action, the existing associations can be updated individually, as well as along with the attribute value and/or expiration_timestamp