]> Occurrences Ontology This ontology extends definitions of date and schedule concepts from the FinancialDates ontology with concepts defining occurrences (i.e., event-related concepts) for use in other FIBO ontologies. https://opensource.org/licenses/MIT The https://spec.edmcouncil.org/fibo/ontology/FND/20141101/DatesAndTimes/Occurrences/ version of this ontology was revised to address the issue resolutions in the FIBO 2.0 RFC, primarily to add properties that are relevant to the inputs and outputs from processes, events, systems and the like. The https://spec.edmcouncil.org/fibo/ontology/FND/20180801/DatesAndTimes/Occurrences/ version of this ontology was revised to make use of the new composite date type added to Financial Dates. The https://spec.edmcouncil.org/fibo/ontology/FND/20190201/DatesAndTimes/Occurrences/ version of this ontology was revised to eliminate duplication of concepts in LCC, and eliminate unnecessary complexity in restrictions. The https://spec.edmcouncil.org/fibo/ontology/FND/20200701/DatesAndTimes/Occurrences/ version of this ontology was revised to eliminate the hasDescription property, which can easily supported using an annotation or isDescribedBy, depending on the situation, clarify the formal definition of occurrence kind, and correct circular and/or non-ISO 704 compliant definitions. The https://spec.edmcouncil.org/fibo/ontology/FND/20200901/DatesAndTimes/Occurrences/ version of this ontology was revised to fix spelling errors. The https://spec.edmcouncil.org/fibo/ontology/FND/20211201/DatesAndTimes/Occurrences/ version of this ontology was revised to address hygiene errors with respect to text formatting. The https://spec.edmcouncil.org/fibo/ontology/FND/20220701/DatesAndTimes/Occurrences.rdf version of the ontology was modified to use the Commons Ontology Library (Commons) Annotation Vocabulary rather than the OMG's Specification Metadata vocabulary. The https://spec.edmcouncil.org/fibo/ontology/FND/20230101/DatesAndTimes/Occurrences.rdf version of this ontology was modified to use the Commons Ontology Library (Commons) rather than the OMG's Languages, Countries and Codes (LCC), eliminating redundancies in FIBO as appropriate. This ontology was added to Foundations in advance of the December 2014 Long Beach meeting in support of the SEC specification. It is also needed to provide temporal relationships for Ownership and Control. These three ontologies are designed for use together: * FinancialDates -- financial Dates and Schedules * BusinessDates -- business day adjustments * Occurrences -- occurrences (events) and kinds of occurrences They are modularized this way to minimize the ontological committments that are imposed upon ontologies that rely upon them. Ontologies can import FinancialDates alone, or FinancialDates + BusinessDates, or FinancialDates + Occurrences, or all three together. Copyright (c) 2014-2023 EDM Council, Inc. Copyright (c) 2014-2023 Object Management Group, Inc. 0 0 0 0 0 1 1 1 0 1 occurrence happening of an OccurrenceKind, i.e., an event Each occurrence has a date time stamp, which identifies when the event occurred, and, optionally, a location (possibly virtual), that identifies where the occurrence happened. event In order for other ontologies to accept FinancialDates without committing to the particular notions of 'Occurrence' and 'OccurrenceKind' that is modeled here, all aspects of Occurrences are captured in this ontology. 1 occurrence-based date calculated date that is defined with respect to the occurrence of some occurrence kind The 'hasDateValue' property of an OccurrenceBasedDate is not set until the Occurrence happens. The 'triggeredBy' property relates an OccurrenceBasedDate to the OccurrenceKind that gives the meaning of the OccurrenceBasedDate. occurrence kind classifier that specifies the general nature of an occurrence (event) loan origination trade settlement As types (or categories) of events, OccurenceKinds do not happen; OccurenceKinds describe Occurrences which happen and exemplify an OccurenceKind. As occurrences are things that actually happen, they have an actual date where as OccurenceKinds do not have an actual date. In order for other ontologies to accept FinancialDates without committing to the particular notions of 'Occurrence' and 'OccurrenceKind' that is modeled here, all aspects of Occurrences are captured in this ontolog exemplifies is a realization or example of http://www.merriam-webster.com/dictionary/exemplify has event date identifies a date associated with an event (occurrence) has event date value identifies a date or date and time value associated with an event (occurrence) has input relates something (e.g. an occurrence) to something that is used as an input to some activity or process has occurrence identifies events of a given occurrence kind, typically as they occur in a schedule has output relates something (e.g. an occurrence) to something that is the result of some activity or process is exemplified by identifies examples of a given concept is input to indicates a precondition, requirement, or other contribution (e.g., data) to some activity, process, system, report, analysis, etc. is output from indicates post condition or other product of some activity, process, system, report, analysis, etc. is triggered by is activated or initiated by An OccurrenceBasedDate is triggered by an Occurrence that exemplifies the OccurrenceKind.