Agreement Document Identifier [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Agreement Document Identifier ======

[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]

===== Discussion =====

An Agreement Document Identifier is an [[public:99_annexes:annex-b-terms-and-definitions:i:identifier|Identifier]] that identifies an [[public:99_annexes:annex-b-terms-and-definitions:a:agreement_document|Agreement Document]].

An Agreement Document Identifier identifies the documentary artifact that records, expresses, or provides Evidence of an [[public:99_annexes:annex-b-terms-and-definitions:a:agreement|Agreement]]. It does not identify the Agreement itself.

An Agreement Document Identifier may be assigned by:

  * A Party to the Agreement
  * A document-management system
  * A contract-management system
  * An electronic-signature service
  * A records-management system
  * A repository
  * A regulatory authority
  * Another authorized assigning authority

An Agreement Document may have more than one Agreement Document Identifier when different systems, Parties, repositories, or identifier schemes identify the same document.

An Agreement Document Identifier should be interpreted together with the identifier scheme, assigning authority, and uniqueness scope under which it was assigned.

An Agreement Document Identifier may identify:

  * A document considered across its managed lifecycle
  * A particular version of a document
  * A particular executed copy
  * A particular representation or rendition
  * A document stored within a specified repository

The applicable identifier scheme must specify which of these things the identifier identifies.

===== Definition =====

> //[[public:99_annexes:annex-b-terms-and-definitions:i:identifier|identifier]] that identifies an [[public:99_annexes:annex-b-terms-and-definitions:a:agreement_document|agreement document]]//

===== Source =====

Adapted from:

  * [[public:99_annexes:annex-b-terms-and-definitions:i:identifier|Identifier]]
  * [[public:99_annexes:annex-b-terms-and-definitions:a:agreement_document|Agreement Document]]
  * [[https://www.omg.org/spec/Commons/Identifiers|OMG Commons Identifiers Ontology]]
    * Relevant concepts include Identifier, Identifier Scheme, identifies, and is identified by
  * [[https://www.omg.org/spec/Commons/Documents|OMG Commons Documents Ontology]]
    * Relevant concepts include Document, Document Part, and Record
  * [[https://www.omg.org/spec/Commons/1.3|OMG Commons Ontology Library, Version 1.3]]
  * [[https://spec.edmcouncil.org/fibo/ontology/FND/Arrangements/Documents/|Financial Industry Business Ontology, Documents Ontology]]

This defines //Agreement Document Identifier// as a specialization of Identifier for Agreement Documents.

===== Note =====

  * An Agreement Document Identifier identifies an Agreement Document
  * An Agreement Document Identifier does not identify the Agreement itself
  * An Agreement Identifier identifies an Agreement
  * One Agreement may be associated with multiple Agreement Documents
  * One Agreement Document may have multiple Agreement Document Identifiers
  * Multiple identifiers may identify the same Agreement Document under different identifier schemes
  * An Agreement Document Identifier must be interpreted within its identifier scheme and uniqueness scope
  * The assigning authority should be identified
  * The date and method of assignment should be recorded when required
  * An Agreement Document Identifier should remain stable within its defined scope
  * An identifier must not be reassigned to a different Agreement Document when reassignment would create ambiguity
  * The identifier scheme must specify whether the identifier applies to a document, document version, executed copy, or representation
  * A document version may require its own version identifier
  * A content digest may verify the content of a document representation but does not necessarily serve as the Agreement Document Identifier
  * A storage location or file path is not necessarily an Agreement Document Identifier
  * Changing the storage location does not necessarily change the Agreement Document Identifier
  * An Agreement Document Identifier does not by itself establish the authenticity, validity, or legal effect of the identified document
  * Evidence and provenance associated with identifier assignment should be preserved
  * An Agreement Document Identifier is distinct from a Legal Entity Identifier and a Unique Transaction Identifier

===== Example =====

An executed master agreement is stored in two contract-management systems.

The first system assigns:

  * Identifier value: `AGR-DOC-2027-00419`
  * Identifier scheme: Party A Contract Document Identifier Scheme
  * Assigning authority: Party A

The second system assigns:

  * Identifier value: `DOC-883721`
  * Identifier scheme: Party B Document Repository Identifier Scheme
  * Assigning authority: Party B

Both Agreement Document Identifiers identify the same Agreement Document.

The Agreement recorded by the document has a separate Agreement Identifier.

A later version of the document receives a separate version identifier while retaining its relationship to the original Agreement Document.

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>