ONTOLOGY EXPLORER
regular schedule
<https://spec.edmcouncil.org/fibo/ontology/FND/DatesAndTimes/FinancialDates/RegularSchedule>
プロパティと値
| プロパティ | 値 |
|---|---|
| type | Class |
| label | "regular schedule" |
| subClassOf | Schedule |
| subClassOf | StructuredCollection |
| subClassOf | _:c14n1093 |
| subClassOf | _:c14n1514 |
| subClassOf | _:c14n1765 |
| subClassOf | _:c14n1986 |
| subClassOf | _:c14n2343 |
| subClassOf | _:c14n2370 |
| subClassOf | _:c14n2560 |
| subClassOf | _:c14n2708 |
| subClassOf | _:c14n3360 |
| definition | "schedule whose time intervals recur regularly" |
| editorialNote | "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." |
| example | "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.\n\nThe payment schedule is a RegularSchedule with these properties:\n\n* comprises: regular payment OccurrenceKind (with payment details) (see the 'comprises' property of the Occurrences ontology)\n* hasInitialStub: June 15-30, 2015 for initial payment\n* hasFinalStub: June 1-14, 2045 for final payment\n* hasCount: 358\n* hasOverallPeriod starting Date: June 15, 2015 with a duration of 30 years\n* hasRecurrenceInterval: specifies 10th day of each calendar month\n* hasRecurrenceStartDate: July 1, 2015" |
| example | "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.\n\nThe payment schedule is a RegularSchedule, with these properties:\n\n* comprises: identifies the interest payment details\n* overall DatePeriod starting date is '2015-01-01', ending date is '2025-01-15', and duration is 'P10Y15D'\n* hasCount is 20 (2 payments per year for 10 years)\n* hasRecurrenceInterval is 'P6M'\n* hasRecurrenceStartDate is '2015-01-15'" |
| example | "An ISDA FpML schedule has a specified date (via a convention), and a date roll rule which is specified for the whole schedule and applies to each of the dates returned by the parametric specification of the schedule. It has: (1) a schedule beginning and end; (2) a set of regular repeating periods: the scheduled event takes place once per period; (3) optionally one or two stubs (one start and one end), which may be longer than the repeating period, or shorter. The precise parameters used are: Start of the overall Schedule period: Effective Date End of the overall Schedule period: Termination Date Start of first regular period: not specified (assume Effective Date) Length of each regular period: Frequency (a duration) There are generally three ways in which the regular periods of a parametric schedule may be expressed: first plus last first plus period length last plus period length event date plus period length. In FpML, Roll events (the date that something rolls over from the value used in one period to the value used in the next) is defined in a Roll Convention, which may be a day of the month, a day of the week, or some published set of dates, typically the ISDA quarterly dates for these events. This is therefore the date within the regular period (before adjustments) when the event occurs. This is in addition to a date for the start or end of such a period. In general this applies to the Calculation Schedule (i.e. the event is the calculation event) with other dates specified relative to this, however in principle the other related events (payment and reset or refix) are specified relative to this." |
| explanatoryNote | "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.\n\nThe '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." |
| explanatoryNote | "A parametric schedule is a regular schedule for one of the events that occur in a periodic schedule of interest accruals, interest payments, and (for floating rate swapstreams), changes to the interest rate. Parametric schedules may be specified individually but more commonly, calculation events are scheduled, with other dates specified as offsets. In a regular schedule, related dates may be independently parametrically scheduled." |
| synonym | "parametric schedule" |
| usageNote | "Other ontologies can extend RegularSchedule as needed.\n\nIn 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." |
| usageNote | "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.\n\nThe recurrence start date can also be relative to the starting Date of the overall DatePeriod of the Schedule." |