public:99_annexes:annex-b-terms-and-definitions:e:effective_period

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

public:99_annexes:annex-b-terms-and-definitions:e:effective_period [2026/10/08 11:43] – created nick_didopublic:99_annexes:annex-b-terms-and-definitions:e:effective_period [2026/10/19 15:17] (current) – nick_dido
Line 5: Line 5:
 ===== Discussion ===== ===== Discussion =====
  
-An Effective Period identifies the time interval during which specified information, status, relationship, Authority, Role Assignment, classification, or rule applies.+An Effective Period identifies the time interval during which a specified thing applies or has effect. 
 + 
 +An Effective Period may apply to an [[public:99_annexes:annex-b-terms-and-definitions:a:agreement|Agreement]], Agreement Term, information item, status, relationship, Authority, Role Assignment, classification, rule, or other modeled thing.
  
 An Effective Period may identify: An Effective Period may identify:
Line 18: Line 20:
   * Provenance describing how the period was established   * Provenance describing how the period was established
  
-An Effective Period may have a defined start without a defined end when the subject remains effective until a later event establishes the end. An Effective Period may have a defined end without a known start when historical information is incomplete.+An Effective Period may have a defined start without a defined end when the subject remains effective until a later event establishes the end.
  
-The applicable Information Structure Definition determines whether the start or end is mandatory.+An Effective Period may have a defined end without a known start when historical information is incomplete.
  
-An Effective Period remains distinct from the time at which information is recorded, received, processed, or stored. The Effective Period identifies when the subject applies. A processing timestamp identifies when a system performed an activity involving the information.+The applicable Information Structure Definition determines whether the start boundary or end boundary is mandatory. 
 + 
 +An Effective Period is distinct from an [[public:99_annexes:annex-b-terms-and-definitions:e:effective_date|Effective Date]] and an [[public:99_annexes:annex-b-terms-and-definitions:e:execution_date|Execution Date]]. 
 + 
 +An Effective Date identifies the date on which the subject begins to apply or have effect. When an Effective Period has a defined start boundary, the Effective Date ordinarily identifies that boundary. 
 + 
 +An Execution Date identifies the date on which an Agreement or other instrument was executed. Execution does not necessarily cause the Agreement or all of its terms to become effective immediately. 
 + 
 +An Effective Period is also distinct from the time at which information is recorded, received, processed, or stored. The Effective Period identifies when the subject applies. A processing timestamp identifies when a system performed an activity involving the information.
  
 ===== Definition ===== ===== Definition =====
  
-> //time interval during which specified information, status, relationship, Authority, Role Assignment, classification, or rule applies//+> //time interval during which a specified thing applies or has effect//
  
 ===== Source ===== ===== Source =====
Line 33: Line 43:
  
   * [[https://www.omg.org/spec/Commons/DatesAndTimes|OMG Commons Dates and Times Ontology]]   * [[https://www.omg.org/spec/Commons/DatesAndTimes|OMG Commons Dates and Times Ontology]]
-    * Relevant concepts: Time Period, Date Period, Start Time, End Time, and Duration+    * Relevant concepts include Time Period, Date Period, Start Time, End Time, and Duration
     * Retrieved: 2026-10-08     * Retrieved: 2026-10-08
   * [[https://www.omg.org/spec/Commons/ContextualIdentifiers|OMG Commons Contextual Identifiers Ontology]]   * [[https://www.omg.org/spec/Commons/ContextualIdentifiers|OMG Commons Contextual Identifiers Ontology]]
-    * Relevant concepts: identifiers and designators applicable during specified periods+    * Relevant concepts include identifiers and designators applicable during specified periods
     * Retrieved: 2026-10-08     * Retrieved: 2026-10-08
   * [[https://www.omg.org/spec/Commons/1.3|OMG Commons Ontology Library, Version 1.3]]   * [[https://www.omg.org/spec/Commons/1.3|OMG Commons Ontology Library, Version 1.3]]
Line 45: Line 55:
 ===== Note ===== ===== Note =====
  
-  * An Effective Period identifies when something applies+  * An Effective Period identifies when something applies or has effect 
 +  * An Effective Date ordinarily identifies the start boundary of an Effective Period 
 +  * An Effective Period may begin on an Effective Date and end on an Expiration Date, Termination Date, or another applicable boundary 
 +  * An Execution Date and an Effective Date may be the same date but represent different facts 
 +  * An Agreement may have an Execution Date different from its Effective Date 
 +  * Different Agreement Terms may have different Effective Dates and Effective Periods
   * An Effective Period does not identify when information was recorded unless the two periods are explicitly the same   * An Effective Period does not identify when information was recorded unless the two periods are explicitly the same
   * An Effective Period may be bounded or open-ended   * An Effective Period may be bounded or open-ended
Line 51: Line 66:
   * The applicable time zone must be identified when local time is used   * The applicable time zone must be identified when local time is used
   * Multiple versions of information may have different Effective Periods   * Multiple versions of information may have different Effective Periods
-  * Effective Periods must not overlap when the applicable model requires exactly one effective value at a time+  * Effective Periods must not overlap when the applicable model permits exactly one effective value at a time
   * The platform-independent definition does not require a particular date-time representation or serialization format   * The platform-independent definition does not require a particular date-time representation or serialization format
  
 ===== Example ===== ===== Example =====
  
-A Person receives Authority to submit regulatory reports beginning on 1 January 2027 and ending on 31 December 2027.+An Agreement is executed on 15 December 2026 and becomes effective on 1 January 2027.
  
-The Effective Period applies to the Authority and the corresponding Role Assignment. The timestamp recording when the Role Assignment entered the system remains separate from the Effective Period.+The Execution Date is 15 December 2026. 
 + 
 +The Effective Date is 1 January 2027 and establishes the start boundary of the Agreement's Effective Period. 
 + 
 +The Agreement remains effective until it expires, is terminated, is superseded, or another applicable event establishes the end of its Effective Period. 
 + 
 +The timestamp recording when the Agreement entered an information system remains separate from the Execution Date, Effective Date, and Effective Period.
  
 ---- ----
 +
 <WRAP centeralign> <WRAP centeralign>
 © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 </WRAP> </WRAP>
  • public/99_annexes/annex-b-terms-and-definitions/e/effective_period.1791484987.txt.gz
  • Last modified: 2026/10/08 11:43
  • by nick_dido