]> Financial Dates Ontology This ontology provides definitions of date and schedule concepts for use in other FIBO ontologies. https://opensource.org/licenses/MIT The https://spec.edmcouncil.org/fibo/ontology/FND/20141101/DatesAndTimes/FinancialDates/ version of this ontology was revised by the FIBO FND 1.2 RTF in order to introduce the definition of a time interval, which is a location, to ground some of the concepts such as a date period, and duration as well as to support the definition of business recurrence intervals for use in parametric schedules for securities. The https://spec.edmcouncil.org/fibo/ontology/FND/20170201/DatesAndTimes/FinancialDates/ version of this ontology was revised by the FIBO 2.0 RFC in order to introduce the definition of a time instant, to eliminate a reasoning issue with relative dates, and remove a circular dependency inadvertently incorporated in the ontology with a FIBO FND 1.2 modification. The https://spec.edmcouncil.org/fibo/ontology/FND/20180801/DatesAndTimes/FinancialDates/ version of this ontology was revised to introduce a composite date datatype to allow for cases whereby the representation of a date for certain purposes, such as GLEIF LEI data, is inconsistent, and to facilitate mapping FIBO to multiple data sources in user environments. The https://spec.edmcouncil.org/fibo/ontology/FND/20190201/DatesAndTimes/FinancialDates/ version of this ontology was revised to eliminate deprecated elements. The https://spec.edmcouncil.org/fibo/ontology/FND/20200201/DatesAndTimes/FinancialDates/ version of this ontology was revised to add the 'has date added' property, which is needed for the date a constituent is added to a basket, among other purposes, to add a TimeOfDay class, needed for representing rate reset times, eliminate duplication with concepts in LCC, and make AdHocScheduleEntry a child of DatedCollectionConstituent. The https://spec.edmcouncil.org/fibo/ontology/FND/20200301/DatesAndTimes/FinancialDates/ version of this ontology was revised to move dated collection and dated collection constituent as well as hasObservedDateTime and hasAcquisitionDate to financial dates in order to improve usability, simplify reasoning, made definitions ISO 704 compliant, and eliminate redundant restrictions on ad hoc schedule entry. The https://spec.edmcouncil.org/fibo/ontology/FND/20200701/DatesAndTimes/FinancialDates/ version of this ontology was revised to add hasOpeningDateTime and hasClosingDateTime for use in defining trading days and sessions and eliminated the functional property declaration on hasExplicitDate. The https://spec.edmcouncil.org/fibo/ontology/FND/20201201/DatesAndTimes/FinancialDates/ version of this ontology was revised to add the concept of age and a corresponding property that supports its use. The https://spec.edmcouncil.org/fibo/ontology/FND/20210601/DatesAndTimes/FinancialDates.rdf version of this ontology was modified to add notes on the custom CombinedDateTime datatype indicating that it is outside the RL profile and that if someone wants to use this ontology with OWL 2 RL rules they might want to comment this out / eliminate it where it is used. The https://spec.edmcouncil.org/fibo/ontology/FND/20210901/DatesAndTimes/FinancialDates.rdf version of this ontology was modified to remove a functional declaration on hasObservedDateTime, which causes reasoning inconsistencies when there are multiple uses of that property for certain individuals, such as for LEI registration. The https://spec.edmcouncil.org/fibo/ontology/FND/20211201/DatesAndTimes/FinancialDates.rdf version of this ontology was modified to address hygiene issues with respect to text formatting. The https://spec.edmcouncil.org/fibo/ontology/FND/20220701/DatesAndTimes/FinancialDates.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/FinancialDates.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. ad hoc schedule schedule consisting of some number of individual events that are not necessarily recurring Other ontologies can extend AdHocSchedule and/or AdHocScheduleEntry as needed to relate the date to something. In particular, the Occurrences ontology extends AdHocScheduleEntry to associate an OccurrenceKind with each entry. The intended meaning is that an Occurrence of the OccurrenceKind happens on the corresponding Date. ad hoc schedule entry entry, including a date or date and time, among multiple non-regularly-recurring entries in a schedule Other ontologies can extend AdHocScheduleEntry as needed. In particular, the Occurrences ontology extends AdHocScheduleEntry to consist of occurrences (events) of a given OccurrenceKind. The meaning is that an ad hoc schedule entry comprises a date and an event which is scheduled to occur on that date. The Date of an AdHocScheduleEntry can be an ExplicitDate or any kind of CalculatedDate, such as: * An OccurrenceBasedDate -- a Date that itself is defined by an Occurrence (see the Occurrences ontology) * A RelativeDate - a Date relative to another Date, such as T+3 * A SpecifiedDate - a Date that is defined by an arbitrary rule The cmns-dt;hasDate property may be used to reify a date, if it is important to do so for a given application, or if not and typically, the inherited cmns-dt;hasObservedDateTime property may be used together with a cmns-dt;CombinedDateTime value, as long as the resulting schedule is consistent in using one or the other. age length of time that something or someone has been alive or existed calculated date date that is or will be determined based on some formula The hasDateValue property of a CalculatedDate is not set until the Date is calculated. Since the calculation may depend upon future events that may or may not ever happen, the hasDateValue property may never be set. calendar month time interval resulting from the division of a calendar year in 12 time intervals, each with a specific name and containing a specific number of calendar days ISO 8601, clause 2.2.11 calendar period time interval that occurs within a system that fixes the beginning and length of a segment of the year with respect to that system The terms 'calendar xxx' are intended to reinforce that these are periods on a calendar, not durations. For example, a calendar year always starts on a January 1 and ends on a December 31. The term 'calendar year' does not mean the same thing as a duration (an amount of time) of 1 year, nor can a calendar year start on any arbitrary day of a year. For example, a calendar year never starts on September 1. Similar points apply to other kinds of calendar periods, such as calendar week, calendar month, and calendar quarter. A calendar-specified date may be figured with respect to a calendar week, a calendar month, a calendar quarter, or a calendar year. calendar quarter time interval of 3 months, starting on January 1, April 1, July 1, or October 1 1 1 1 calendar-specified interval recurrence interval that is defined as the nth day of some calendar period (such as a calendar month), and a time direction (forward from the beginning of the month, or backwards from the end) The 15th day of each calendar month. The last day of each quarter, specified as RelativeDay 1, and TimeDirection set to FromEnd. The nth day is an ordinal number, not a cardinal number. '1' means the first day of the calendar period. calendar week time interval of seven calendar days starting on a Monday ISO 8601, clause 2.2.8 calendar year cyclic time interval in a calendar which is required for one revolution of the Earth around the Sun and approximated to an integral number of calendar days; a year in the Gregorian calendar ISO 8601 clause 2.2.13 true The use of custom datatypes is outside the OWL 2 RL profile and so users should consider commenting this and its usage here, and in other ontologies out, or replacing it with rdfs:Literal out in applications that are constrained to OWL 2 RL. true true true true dated collection constituent element of a collection that is associated with a date and time Note that the use of several options for the representation of a date and time stamp enables extensions for milliseconds, nanoseconds using an xsd:string that has the format of an xsd:dateTime datatype but extends the level of granularity consistently. An example of where this is required is to represent prices that change multiple times in a given day. The use of custom datatypes is outside the OWL 2 RL profile and so users should consider commenting out the restriction on hasObservedDateTime altogether or change the data range to rdfs:Literal in applications that are constrained to OWL 2 RL. dated structured collection structured collection whose elements are required to have a date and time true true true true true 1 explicit recurrence interval recurrence interval defined via an explicit duration Friday time interval that has duration 1 day and that meets a Saturday from the end time direction indicating that a calendar-specified date is the nth date from the end of a calendar period Two days before the end of a calendar month. from the start time direction indicating that a calendar-specified date is the nth day from the beginning of a calendar period. The first day of a calendar quarter. (The offsetDay is zero.) Monday time interval that has duration 1 day and that meets a Tuesday recurrence interval time interval that is consistent between elements of a regular schedule frequency 0 0 regular schedule schedule whose time intervals recur regularly The BusinessDates ontology extends 'RegularSchedule' with an optional BusinessDayAdjustment that specifies what should happen if a scheduled date falls on a weekend or a holiday. A 30 year mortgage is payable monthly on the 10th of the month, starting July 2015. The mortgage is issued on June 15, 2015 so the first payment is for the period June 15-June 30, and the last payment is for June 1-14 2045. The payment schedule is a RegularSchedule with these properties: * comprises: regular payment OccurrenceKind (with payment details) (see the 'comprises' property of the Occurrences ontology) * hasInitialStub: June 15-30, 2015 for initial payment * hasFinalStub: June 1-14, 2045 for final payment * hasCount: 358 * hasOverallPeriod starting Date: June 15, 2015 with a duration of 30 years * hasRecurrenceInterval: specifies 10th day of each calendar month * hasRecurrenceStartDate: July 1, 2015 A corporate bond pays interest for 10 years starting on the first day of 2015. Interest payments are due 15 days after the expiration of each 6 month period: on July 15 and January 16. The payment schedule is a RegularSchedule, with these properties: * comprises: identifies the interest payment details * overall DatePeriod starting date is '2015-01-01', ending date is '2025-01-15', and duration is 'P10Y15D' * hasCount is 20 (2 payments per year for 10 years) * hasRecurrenceInterval is 'P6M' * hasRecurrenceStartDate is '2015-01-15' A RegularSchedule is a Schedule defined as a set of Dates that start on a recurrence start date and repeat after each recurrence interval. The size of this set is defined by a count. The 'initial ScheduleStub' associated with a RegularSchedule identifies any special treatment applied before the recurrence start date. Similarly, a 'final ScheduleStub' identifies any special handling at the end of the recurrences. For example, a mortgage loan that is due each calendar month may have an initial payment due before the first calendar month, or a final payment due after the last monthly payment. Other ontologies can extend RegularSchedule as needed. In particular, the Occurrences ontology extends RegularSchedule to 'comprise' an 'OccurrenceKind'. The intended meaning is that a regular schedule comprises a number of scheduled dates and an event which is scheduled to occur on each of those dates, in other words an Occurrence of the OccurrenceKind should happen on each Date defined by the RegularSchedule. The recurrence start date can be an ExplicitDate or any kind of CalculatedDate. Hence, the starting date could be relative to another Date (e.g. T+3) or triggered by the Occurrence of an OccurrenceKind, etc. The recurrence start date can also be relative to the starting Date of the overall DatePeriod of the Schedule. 1 1 relative date calculated date that is some duration before or after another date A settlement date, defined as T+3: three days after the trade date. The 'hasRelativeDuration' property is set to '3D'. When the 'hasRelativeDuration' property is negative, the RelativeDate is before the 'isRelativeTo' Date; otherwise the RelativeDate is after the 'isRelativeTo' Date. Saturday time interval that has duration 1 day and that meets a Sunday One Saturday is the time interval that has duration 1 day and that starts Gregorian year 2000. This requirement anchors the repeating sequence of days of week to specific Gregorian days. It requires that January 1, 2000 is a Saturday. It follows that January 2, 2000 must be the Sunday that it meets, and so on. 1 schedule collection of events, observations, or other occurrences and the associated dates and/or times when they will be done The overall period covers the entire DatePeriod of the Schedule, from the earliest Date to the final Date of the Schedule. Schedules may be ad hoc, essentially a list of dates and events without any consistency in the durations between events, regular, in which case there is a consistently recurring interval between events, or a combination of the two. 1 schedule stub date period before the start of the recurring part of a schedule or after the end of the recurring part, which may be associated with a specific occurrence kind The Occurrences ontology extends ScheduleStub to 'comprise' an OccurrenceKind. The meaning is that a schedule stub comprises a date period and an event which is scheduled to occur during that date period; in other words that an Occurrence of the OccurrenceKind should happen during the DatePeriod of the ScheduleStub. A 30 year mortgage calls for monthly payments on the first day of each month, according to a RegularSchedule. If the mortgage does not start on the first day of a calendar month, then an initial ScheduleStub specifies the payment due for the DatePeriod up to the first day of the next calendar month. Similarly, a final ScheduleStub specifies the last payment due for the DatePeriod after the end of the last full calendar month. 1 specified date calculated date that is defined by a rule that is captured as a string by the 'hasDateSpecification' property Sunday time interval that has duration 1 day and that meets a Monday Thursday time interval that has duration 1 day and that meets a Friday time direction enumeration that indicates whether a calendar-specified date is figured from the start or the end of a calendar period true true true Tuesday time interval that has duration 1 day and that meets a Wednesday Wednesday time interval that has duration 1 day and that meets a Thursday has acquisition date links an asset or owner/controller/controllee to the date or date and time of purchase The use of custom datatypes is outside the OWL 2 RL profile and so users should consider commenting out the range restriction or change the range to rdfs:Literal in applications that are constrained to OWL 2 RL. has age relates something to the length of time it has existed has as-of date relates something to the date on which it is accurate or valid (e.g. a credit report has an asOfDate that means the date when the information was drawn) It is different from the creation date and need not be the last date of the DatePeriod covered. has calendar period identifies a period of time used in computing a calendar-specified date, such as a calendar week, calendar month, calendar quarter, or calendar year has closing date time the day and time at which something closes The use of custom datatypes is outside the OWL 2 RL profile and so users should consider commenting out the range restriction or change the range to rdfs:Literal in applications that are constrained to OWL 2 RL. has count specifies the total number of things in a collection, such as the number of entries in a regular schedule true has date added indicates the date something was included in something else true has date received relates something to the date it arrived or was delivered, e.g., a loan application request has date specification rule that specifies how a specified date is computed The rule is modeled as a simple String because OWL2 provides no way to model the semantics of such a rule. true true true true true true true true true has final stub identifies any special period at the end of a regular schedule has initial stub identifies any special period at the start of a regular schedule true has opening date time the day and time at which something opens The use of custom datatypes is outside the OWL 2 RL profile and so users should consider commenting out the range restriction or change the range to rdfs:Literal in applications that are constrained to OWL 2 RL. has ordinal number specifies a number designating place in an ordered sequence, i.e., 1st, 2nd, 3rd, etc. Negative ordinal numbers mean 1st before, 2nd before, etc. has overall period identifies a date period that includes all the dates of a schedule, including any schedule stubs has recurrence interval indicates the frequency with which some event or publication occurs has recurrence start date the starting date of the first recurrence in a regular schedule has relative duration duration between two explicit dates A relative duration may be negative. Note that this property is distinct from hasDurationValue, as a relative duration may resolve to a relative date or date time (both of which are time points) rather than an interval, which would result in a logical inconsistency if its parent property is hasDurationValue. has schedule indicates a schedule for something true has stub links an abbreviated period at the start or end of some schedule to the overall schedule has time direction indicates whether a calendar-specified date is figured from the beginning or end of a calendar period true is relative to identifies a specific date that a relative date or relative date period references