NotableDateRule and adjustment-policy reference
This page is the authoritative element-by-element reference for the document model on the notable-date schema (urn:bodu:globalization:calendar): the <NotableDate> concept, the <Rule> recipe, the <Applicability> filter, the most common <Strategy> elements (the strategy reference covers all 13 single-date strategies and the four recurrence sources), and the reusable <AdjustmentPolicy> shape. For the vocabulary it assumes, start with Core concepts. For how to assemble a whole document - imports and overrides - see Authoring notable date rules. For where the service processes these elements, see The resolution pipeline.
A rule is authored as XML or JSON and loaded into an immutable NotableDateResource; the loaded form is exposed through NotableDateDefinition and NotableDateRule, which are immutable and constructed by the loader - there is no object-initializer authoring API.
<NotableDateResource> - the document root
The root element declares the schema namespace, version, and id, and contains its child sections in this order: <Metadata>, <ResolutionPolicy>, <AdjustmentPolicies>, <Imports>, <NotableDates>, <Overrides> (all optional). The root maps to NotableDateResource.
| Attribute | Required | Type | Description |
|---|---|---|---|
xmlns |
Yes | namespace | Always urn:bodu:globalization:calendar. |
schemaVersion |
Yes | string | The document's schema version, e.g. 1.0. Surfaces as NotableDateResource.SchemaVersion. |
resourceId |
Yes | identifier | Stable resource id (lowercase, digits, hyphens, dots - e.g. data.au). Surfaces as NotableDateResource.ResourceId and as the ResourceId part of every NotableDateRuleIdentity. |
<Metadata> - descriptive provenance
<Metadata> is optional and carries an optional <Name>, an optional <Description>, and zero or more <Source> string entries. It is documentation only - it does not affect resolution.
<ResolutionPolicy> - resource-level reconciliation
<ResolutionPolicy> is optional; an absent element means ResolutionPolicy.Default. It maps to the loaded ResolutionPolicy and decides how duplicate declarations, same-day collisions and overlapping spans are settled, which span of an occurrence controls range inclusion, and which days are the working week.
| Attribute | Type | Default | Description |
|---|---|---|---|
duplicatePolicy |
DuplicatePolicy | Error |
Settles the concepts and rules this document declares with one id, at load: Error reports BODU-CAL-DUP-ND / BODU-CAL-DUP-RULE, KeepFirst and KeepLast keep one declaration, Merge appends a later concept's rules to the first. Imports and <AddRule> overrides keep their own rules. |
sameDayCollisionPolicy |
CollisionPolicy | KeepAll |
Settles distinct occurrences that share an emitted date: KeepAll, HighestPriorityOnly, CategoryPriority, Custom. |
spanCollisionPolicy |
CollisionPolicy | KeepAll |
Settles, after the same-day groups, every chain of occurrences connected through overlapping spans that holds a multi-day occurrence (same value set). |
priorityDirection |
PriorityDirection | HigherWins |
Whether a larger or smaller Priority wins a tie: HigherWins, LowerWins. |
observedDateRangePolicy |
ObservedDateRangePolicy | ObservedOccurrenceControlsInclusion |
Which span a range query tests: the emitted span (ObservedOccurrenceControlsInclusion), the actual span (ActualOccurrenceControlsInclusion), or either (BothOccurrencesControlInclusion). |
workingDays |
week pattern | Mon-Fri | The working week the weekend-related triggers and working-day arithmetic interpret, as a seven-character Sunday-first mask (e.g. 0111110 = Mon-Fri). Maps to ResolutionPolicy.WorkingWeek (a Bodu.Core DayOfWeekSet). Only the binary form is accepted: any other value, a letter mask such as _MTWTF_ included, fails the load with BODU-CAL-WORKING-DAYS. |
An optional <CategoryPrecedence> child orders categories for CollisionPolicy.CategoryPriority. See Rule identity, priority, and observed-date resolution for the settlement semantics.
<ResolutionPolicy duplicatePolicy="KeepFirst"
sameDayCollisionPolicy="HighestPriorityOnly"
priorityDirection="HigherWins"
observedDateRangePolicy="ObservedOccurrenceControlsInclusion"
workingDays="0111110" />
<NotableDate> - the concept
<NotableDate> declares one notable-date concept. It carries an optional <Tags> block and a required <Rules> block of one or more <Rule> elements.
| Attribute | Required | Type | Default | Description |
|---|---|---|---|---|
id |
Yes | identifier | - | Stable concept id (lowercase, digits, hyphens), e.g. easter-sunday. Unique within the resource. |
displayName |
Yes | string | - | Human-readable name surfaced as NotableDate.DisplayName. |
category |
Yes | category | - | Default NotableDateCategory for every rule that does not override it. |
defaultDurationDays |
No | positive int | 1 |
Default span in days for rules that do not set durationDays. |
defaultNonWorkingDay |
No | bool | (unset) | Default non-working flag inherited by rules that do not set nonWorking. |
<NotableDate id="anzac-day" displayName="Anzac Day" category="Remembrance" defaultNonWorkingDay="true">
<Tags>
<Tag value="national" />
</Tags>
<Rules>
<Rule id="default">
<Strategy><Fixed month="April" day="25" /></Strategy>
</Rule>
</Rules>
</NotableDate>
A <Tags> block contains one or more <Tag value="..."/> elements. Concept-level tags apply to every rule that declares none of its own; a rule's own <Tags> block replaces the concept's tags for that rule. Tags survive into NotableDate.Tags and are matched by NotableDateFilter.WithTag / WithAnyTag / WithAllTags.
<Rule> - the recipe
A <Rule> is one calculation recipe for its concept. It contains, in order, an optional <Applicability>, exactly one <Strategy> or <Recurrence>, an optional <Duration>, an optional <Tags>, and an optional <Adjustments>.
| Attribute | Required | Type | Default | Description |
|---|---|---|---|---|
id |
Yes | identifier | - | Distinguishes this rule from its siblings under the same concept (e.g. default, nsw, wa). Targeted by <OffsetFromRule ruleRef> and <Overrides>. |
priority |
No | int | 0 |
Tie-break weight when several occurrences share a day, applied per the resource's priorityDirection. It also orders observed-date placement among occurrences with the same actual date, the higher value first. |
category |
No | category | (concept default) | Overrides the concept's category for this rule. |
nonWorking |
No | bool | (concept default) | Overrides defaultNonWorkingDay for this rule. |
durationDays |
No | positive int | (concept default) | Overrides defaultDurationDays for this rule. |
comment |
No | string | - | Authoring annotation; not surfaced to consumers. |
<Rule id="wa" priority="100" comment="Western Australia observes a substitute Monday when 25 April is a weekend.">
<Applicability calendar="Gregorian"><Territory code="AU-WA" /></Applicability>
<Strategy><Fixed month="April" day="25" /></Strategy>
<Tags><Tag value="public-holiday" /></Tags>
<Adjustments><Adjustment policyRef="weekend-roll" /></Adjustments>
</Rule>
The <Adjustments> block holds one or more <Adjustment policyRef="..."/> references to policies declared in <AdjustmentPolicies>. Adjustments are always referenced by id; see <AdjustmentPolicy> below.
<Applicability> - calendar, year, and territory filtering
<Applicability> constrains when and where a rule applies. All of its attributes and children are optional; an absent <Applicability> means the rule applies in the Gregorian calendar, in every year, and in every territory.
| Attribute | Type | Default | Description |
|---|---|---|---|
calendar |
calendar name | Gregorian |
The calendar the rule's <Strategy> is expressed in: Gregorian, Hijri, UmmAlQura, Hebrew, Persian, ChineseLunisolar. |
fromYear |
year | - | Inclusive first Gregorian year the rule is active. |
toYear |
year | - | Inclusive last Gregorian year the rule is active. |
everyYears |
positive int | - | Periodicity - the rule applies every nth year, counted from anchorYear. |
anchorYear |
year | - | The reference year for everyYears. |
| Child element | Repeats | Description |
|---|---|---|
<Territory code="..."/> |
Yes | Scopes the rule to an ISO 3166 country or subdivision (AU, AU-NSW). Multiple entries broaden the scope. A rule with no <Territory> applies to every territory. |
<OnlyYear value="..."/> |
Yes | Restricts the rule to the listed year(s) only. |
<ExceptYear value="..."/> |
Yes | Excludes the listed year(s) from an otherwise-applicable range. |
<!-- A trial public holiday active only in 2026 and 2027, scoped to New South Wales. -->
<Applicability calendar="Gregorian" fromYear="2026" toYear="2027">
<Territory code="AU-NSW" />
</Applicability>
Territory scoping is hierarchical: a rule scoped to AU resolves for an AU query and for any AU-XXX subdivision query; a rule scoped to AU-NSW resolves only for AU-NSW (and an AU query that enumerates its subdivisions). When several rules of one concept match a territory, the engine selects the most specific. See Territories and regional composition.
Strategy elements
A rule carries exactly one occurrence source: a <Strategy> child (one of the elements below) or a <Recurrence> child (recurrence elements). Each <Strategy> element maps to a public IDateCalculationStrategy. Pick the simplest strategy that matches how the date is defined; reach for <Algorithm> only when the date cannot be expressed as calendar arithmetic. The six most common are detailed below; the positional (<OrdinalDayOfMonth>, <DayOfYear>, <IsoWeekDate>), dynamic-reference (<WeekdayNearRule>, <NthWeekdayFromRule>), and business-day (<WorkingDayOffsetFromRule>, <WorkingDayInMonth>) strategies - plus a per-attribute treatment of all of them - are catalogued in Notable-date rule strategies. The strategy kinds are also covered, with the engine's view, in Date calculation algorithms.
<Fixed> - a fixed month and day
| Attribute | Required | Type | Description |
|---|---|---|---|
month |
Yes | string | Month number 1-12 or an English month name. In another calendar, a month number up to the most months its year can have (1-13 in the Hebrew calendar, and in the Chinese lunisolar calendar unless skipLeapMonth is set; 1-12 in the Hijri, Umm al-Qura and Persian calendars) or, in the Hebrew calendar alone, a Hebrew month name. A month name matches ignoring case. |
day |
Yes | day (1-31) | Day of month. |
skipLeapMonth |
No | bool | Chinese lunisolar only - advance an ordinal lunar month past an intercalary leap month. |
sweepCalendarYears |
No | bool | Non-Gregorian only - evaluate both candidate calendar years overlapping the requested Gregorian year. |
<!-- Christmas Day - 25 December. -->
<Rule id="default">
<Strategy><Fixed month="December" day="25" /></Strategy>
</Rule>
An impossible date (e.g. 29 February in a non-leap year) yields no occurrence for that year. skipLeapMonth and sweepCalendarYears apply only when the enclosing <Applicability calendar="..."> is non-Gregorian - see Working with non-Gregorian calendars.
<DayOfWeekInMonth> - the nth weekday in a month
| Attribute | Required | Type | Description |
|---|---|---|---|
month |
Yes | string | Month number or English month name. |
dayOfWeek |
Yes | day of week | The target weekday. |
weekOrdinal |
Yes | ordinal | WeekOrdinal: First, Second, Third, Fourth, Fifth, Last. |
<!-- US Thanksgiving - the fourth Thursday in November. -->
<Rule id="default">
<Strategy><DayOfWeekInMonth month="11" dayOfWeek="Thursday" weekOrdinal="Fourth" /></Strategy>
</Rule>
Last resolves to the final occurrence in the month regardless of whether it is the fourth or fifth; a Fifth that does not exist yields no occurrence for that year.
<WeekdayNearDate> - a weekday near a fixed date
| Attribute | Required | Type | Description |
|---|---|---|---|
month |
Yes | string | Reference month (number or name). |
day |
Yes | day (1-31) | Reference day of month. |
dayOfWeek |
Yes | day of week | The target weekday. |
direction |
Yes | proximity | WeekdayProximity: Before, OnOrBefore, Nearest, OnOrAfter, After. |
<!-- Victoria Day (CA) - the Monday on or before 24 May. -->
<Rule id="default">
<Strategy><WeekdayNearDate month="5" day="24" dayOfWeek="Monday" direction="OnOrBefore" /></Strategy>
</Rule>
Because a weekday recurs every seven days, each direction selects a single unambiguous occurrence in the seven-day window anchored at the reference date. OnOrBefore / OnOrAfter include the reference date itself when it already falls on the target weekday; Nearest picks the closest in either direction (the forward and backward distances sum to seven, so the result is never a tie). When the reference (year, month, day) is not a valid date, the rule produces no occurrence.
<RelativeWeekdayInMonth> - a weekday relative to an anchor weekday
| Attribute | Required | Type | Description |
|---|---|---|---|
month |
Yes | string | The anchor month. |
dayOfWeek |
Yes | day of week | The anchor weekday - combined with weekOrdinal it identifies the reference occurrence. |
weekOrdinal |
Yes | ordinal | Which occurrence of the anchor weekday. |
relativeDayOfWeek |
Yes | day of week | The target weekday the rule resolves to. |
direction |
Yes | proximity | How the target weekday is positioned relative to the anchor. |
<!-- US Election Day - the Tuesday after the first Monday in November. -->
<Rule id="default">
<Strategy>
<RelativeWeekdayInMonth month="11" dayOfWeek="Monday" weekOrdinal="First"
relativeDayOfWeek="Tuesday" direction="After" />
</Strategy>
</Rule>
The strategy first computes the anchor (the weekOrdinal-th dayOfWeek of month), then positions relativeDayOfWeek relative to it using the same window semantics as <WeekdayNearDate>. When the anchor occurrence does not exist (a Fifth in a month with only four) the rule produces no occurrence.
Note
"The next weekday after a known weekday" is always a fixed offset, so <RelativeWeekdayInMonth> and <OffsetFromRule> can describe the same date. Prefer <OffsetFromRule> whenever the anchor already exists as a rule (it tracks that rule); use <RelativeWeekdayInMonth> when the ordinal-weekday anchor is not itself a modelled concept (US Election Day has no "first Monday of November" rule to offset from).
<OffsetFromRule> - a signed offset from another rule
| Attribute | Required | Type | Description |
|---|---|---|---|
notableDateRef |
Yes | identifier | The id of the concept whose occurrence is the reference point. |
ruleRef |
No | identifier | The id of a specific rule within that concept (e.g. default). |
offsetDays |
Yes | int | Signed day offset - negative moves before the reference, positive after. |
<NotableDate id="easter-sunday" displayName="Easter Sunday" category="Religious">
<Rules>
<Rule id="default"><Strategy><Algorithm key="western-easter" /></Strategy></Rule>
</Rules>
</NotableDate>
<NotableDate id="good-friday" displayName="Good Friday" category="PublicHoliday">
<Rules>
<Rule id="default">
<Strategy><OffsetFromRule notableDateRef="easter-sunday" ruleRef="default" offsetDays="-2" /></Strategy>
</Rule>
</Rules>
</NotableDate>
The referenced rule is resolved first and the offset applied - this is how Good Friday and Easter Monday hang off Easter Sunday. References are resolved cycle-safely within the resource: a self- or mutually-referential chain is not reported by validation; it is broken when the dates are resolved, and the rules caught in it produce no occurrence. When the referenced rule produces no occurrence for the year, the offset rule produces none in turn.
<Algorithm> - dispatch to a named calculator
| Attribute | Required | Type | Description |
|---|---|---|---|
key |
Yes | string | Names a built-in calculator or a custom INotableDateAlgorithm registered in a NotableDateAlgorithmRegistry. |
<!-- Easter Sunday by the Gregorian computus. -->
<Rule id="default">
<Strategy><Algorithm key="western-easter" /></Strategy>
</Rule>
Built-in keys include western-easter, orthodox-easter, vernal-equinox, autumnal-equinox, qingming, vesak, asalha-puja, losar, matariki, and the Hindu-festival keys (diwali, holi, ram-navami, …). An unknown key resolves against a custom registry; an unregistered unknown key surfaces as a validation diagnostic at load time. See Date calculation algorithms for the full key catalogue and how to register a custom algorithm.
Recurrence elements
In place of a <Strategy>, a rule may carry a <Recurrence> child holding exactly one of the elements below, each mapping to a public IDateRecurrenceStrategy. A recurrence generates many occurrences within a window; each is a normal candidate that receives the rule's category, non-working flag, duration, and adjustments. An anchor is required only when the interval is greater than one. Full semantics and worked scenarios are in Notable-date rule strategies.
| Element | Key attributes | Yields |
|---|---|---|
<DailyInterval> |
anchorDate (req.), intervalDays (≥1, default 1) |
An occurrence every n days from the anchor. |
<Weekly> |
<Day dayOfWeek="…" /> (1+), intervalWeeks (≥1), anchorDate (req. when intervalWeeks > 1) |
The selected weekdays every n weeks. |
<MonthlyDay> |
dayOfMonth (1-31), intervalMonths (≥1), anchorDate (req. when > 1), invalidDayBehavior (Skip | UseLastDayOfMonth) |
A calendar day every n months. |
<MonthlyWeekday> |
dayOfWeek, weekOrdinal, intervalMonths (≥1), anchorDate (req. when > 1) |
An ordinal weekday every n months. |
<!-- The last Friday of every month. -->
<Rule id="default">
<Recurrence><MonthlyWeekday dayOfWeek="Friday" weekOrdinal="Last" /></Recurrence>
</Rule>
anchorDate is an ISO-8601 yyyy-MM-dd date. A rule declaring both <Strategy> and <Recurrence>, or neither, is rejected at load time with BODU-CAL-RULE-SOURCE, in XML and JSON alike.
<Duration> - a calculated span
A rule's span is either the fixed durationDays attribute (above) or a calculated <Duration><UntilDate> whose end is computed by a second <Strategy>. A rule declares one or the other, never both. The end strategy is evaluated for the start anchor's civil year and, when that yields nothing acceptable, the following year - so the span can cross the year boundary and vary in length. Maps to CalculatedEndDateDurationDefinition.
<UntilDate> attribute |
Required | Type | Description |
|---|---|---|---|
startBoundary |
No | proximity | DateBoundary: Inclusive (default) or Exclusive. |
endBoundary |
No | proximity | Inclusive (default) or Exclusive. |
selection |
No | enum | EndDateSelection: FirstOnOrAfterStart (default) or FirstAfterStart. |
<!-- Year-end shutdown: the Friday before Boxing Day to the Monday after New Year's Day. -->
<Rule id="default">
<Strategy><WeekdayNearDate month="12" day="26" dayOfWeek="Friday" direction="Before" /></Strategy>
<Duration>
<UntilDate startBoundary="Exclusive" endBoundary="Exclusive">
<Strategy><WeekdayNearDate month="1" day="1" dayOfWeek="Monday" direction="After" /></Strategy>
</UntilDate>
</Duration>
</Rule>
See Notable-date rule strategies - Durations for the full treatment.
<AdjustmentPolicy> - the reusable shift
A weekend substitution or "move to next working day" shift is declared once in <AdjustmentPolicies> and referenced from rules by id. It models the runtime AdjustmentPolicy. A policy contains, in order, an optional <Scope>, a required <Trigger>, a required <Action>, a required <Emission>, and optional <Parameters>.
<AdjustmentPolicy> attribute |
Required | Type | Default | Description |
|---|---|---|---|---|
id |
Yes | identifier | - | Policy id referenced by <Adjustment policyRef="...">. |
priority |
No | int | 0 |
Evaluation order when a rule references several policies. |
description |
No | string | - | Authoring annotation. |
<AdjustmentPolicy id="weekend-roll" priority="100"
description="If the holiday falls on a weekend, observe it on the following Monday.">
<Trigger type="IfWeekend" />
<Action type="MoveToNextWorkingDay" skipWeekends="true" skipNonWorkingDates="false" maxSearchDays="7" />
<Emission mode="ObservedOnly" reason="Substitute public holiday" />
</AdjustmentPolicy>
<Scope> - where the policy applies
<Scope> is optional; an absent scope means the policy applies wherever it is referenced. It carries optional fromYear / toYear attributes and any mix of these children: <Territory code="..."/>, <Calendar name="..."/>, <Category value="..."/>, <NotableDate ref="..."/>, <Rule notableDateRef="..." ruleRef="..."/>, <OnlyYear value="..."/>, <ExceptYear value="..."/>. It maps to AdjustmentScope.
<Trigger> - when it fires
<Trigger> has a required type (an AdjustmentTrigger value) and optional month, day, weekOrdinal, and handlerKey attributes, plus zero or more <Weekday value="..."/> children for day-specific triggers.
type |
Fires when… |
|---|---|
Always |
Unconditionally. |
IfDayOfWeek |
The actual date falls on a listed <Weekday>. |
IfWeekend |
The actual date is a weekend day per the resource's working week. |
IfWeekday |
The actual date is a working-week day. |
IfNonWorkingDay |
The actual date is already a non-working day (weekend or another non-working occurrence). |
IfWorkingDay |
The actual date is a working day. |
IfLeapYear |
The resolution year is a leap year. |
IfBeforeFixedDate / IfAfterFixedDate |
The actual date is before / after the month+day reference. |
IfNthOccurrenceInMonth |
The actual date is the weekOrdinal-th <Weekday> of its month. |
Custom |
A registered IAdjustmentTriggerHandler (named by handlerKey) returns true. |
<Action> - what it does
<Action> has a required type (an AdjustmentAction value) and optional days, dayOfWeek, maxSearchDays, skipWeekends, skipNonWorkingDates, notableDateRef, ruleRef, and handlerKey attributes.
type |
Effect |
|---|---|
None |
Records the trigger but leaves the date unchanged. |
AddDays |
Adds days (may be negative). |
MoveToNextWeekday / MoveToPreviousWeekday |
Moves to the dayOfWeek on or after / on or before the actual date, ignoring the working week and other holidays. Without dayOfWeek the date is unchanged. |
MoveToNextWorkingDay / MoveToPreviousWorkingDay |
Starting the day after / before the actual date, skips the days skipWeekends (default true) and skipNonWorkingDates (default false) block, scanning at most maxSearchDays days (default 7; at the bound the last day scanned is used). |
ReplaceWithRule |
Replaces the date with the occurrence of the rule named by notableDateRef / ruleRef. |
Suppress |
Drops the occurrence. |
Custom |
Delegates to a registered IAdjustmentHandler named by handlerKey. |
<Emission> - what is emitted
<Emission> has a required mode (a EmissionMode value) and optional reason and nonWorking attributes. The reason is carried into NotableDate.AdjustmentReason; nonWorking, when set, replaces the rule's flag on the observed occurrence (NotableDate.IsNonWorkingDay) and decides whether it claims its day.
mode |
Emits |
|---|---|
ActualOnly |
Only the nominal (actual) date. |
ObservedOnly |
Only the shifted (observed) date - the single occurrence moves. |
ActualAndObserved |
Both the nominal and the observed dates, as two occurrences. |
ObservedAsAdditional |
[Obsolete] - behaves identically to ActualAndObserved and is normalised to it at load time. Author ActualAndObserved for the "keep the actual date and add a substitute" pattern. |
Suppress |
Nothing - drops the occurrence. |
<Parameters> - handler inputs
When type="Custom" on a trigger or action, an optional <Parameters> block of <Param key="..." value="..."/> entries is passed to the registered handler. See Observance adjustment rules for custom trigger / action handlers.
Reading the resolved NotableDate
NotableDateService.Resolve(...) returns NotableDate records - one per resolved occurrence. The record is positional and immutable; its key members:
| Member | Type | Description |
|---|---|---|
Date |
DateOnly |
The emitted (observed) date - the date to display, after any adjustment. |
ActualDate |
DateOnly? |
The originally calculated (nominal) date. |
IsObserved |
bool |
Whether this is the observed occurrence emitted by a fired adjustment policy; Date can equal ActualDate when the action left it unchanged. |
EndDate |
DateOnly |
The inclusive last day (Date + DurationDays − 1). |
DurationDays |
int |
Span in days (1 for single-day events). |
DisplayName |
string |
The display name (subject to optional localization). |
Category |
NotableDateCategory |
The classification carried from the rule. |
Priority |
int |
Tie-break weight consulted by the collision policy. |
TerritoryCode |
string |
The territory the occurrence applies to. |
IsNonWorkingDay |
bool |
Whether working-day arithmetic should skip this date. |
Tags |
IReadOnlyList<string> |
Free-form classification tags from the rule. |
AdjustmentPolicyId, AdjustmentReason |
string? |
Which adjustment policy moved the date, and the reason text - set when IsObserved. |
Identity (NotableDateId, RuleId) |
NotableDateRuleIdentity | The originating concept and rule ids. |
foreach (NotableDate date in service.Resolve(2027, "AU"))
{
Console.WriteLine($"{date.Date:d MMM yyyy} {date.DisplayName}");
if (date.DurationDays > 1)
Console.WriteLine($" Multi-day: ends {date.EndDate:d MMM yyyy}");
if (date.IsObserved)
Console.WriteLine($" Observed (nominal {date.ActualDate:d MMM yyyy}, via {date.AdjustmentPolicyId}: {date.AdjustmentReason})");
}
There is no Name property (use DisplayName) and no WasAdjusted property (use IsObserved).
NotableDateCategory
category on a concept or rule is a NotableDateCategory value, carried unchanged into NotableDate.Category.
| Value | Intended use |
|---|---|
None |
No category assigned. |
PublicHoliday |
Statutory public holiday in the territory. |
BankHoliday |
Bank / financial-sector holiday, distinct from a general public holiday. |
Observance |
Recognised observance without statutory non-working status. |
Remembrance |
Day of national remembrance or mourning. |
Cultural |
Cultural event or celebration. |
Religious |
Religious festival or feast day. |
Seasonal |
Season boundary, solstice, or equinox event. |
Civic |
Civic or government-driven observance (election day, census day). |
School |
School term boundary or teacher-only day. |
Regional |
Sub-national regional event not classified elsewhere. |
Other |
Catch-all. |
Where to go next
- Authoring notable date rules - assembling a whole document: imports and ID-targeted overrides.
- Date calculation algorithms - the strategy kinds in depth, built-in
<Algorithm>keys, and custom algorithms. - Observance adjustment rules - the full
<AdjustmentPolicy>trigger / action / emission catalogues and custom handlers. - Holiday patterns and examples - end-to-end worked examples for common holiday types.
- The resolution pipeline - how these elements are processed to produce
NotableDateresults. - Globalization & Calendars guides - every guide in this topic: the runtime, companions, data packs, and the notable-date catalogue.