← Back to catalogue
Published

March 31

vr.tr.march-31 · thing-q2461

Let an agent handle March 31 as a calendar date with weekday computation, observances attributed to their traditions and sourced events.

Thing Registry Cross-cutting context XCT.TME
Bundle → Layer → Finding → QuestionsClassifiersWhat it isWhy it existsDistinguishing featuresWhat robots and AI may and may not doMoral aspectsOwnersLinks to other meta-modelsIdentity and identifiersDirect propertiesRecognitionCapabilities and actionsHazards and failure modesStandards and interfacesContext of useSources

Bundle → Layer → Finding → Questions Filled

4 bundles · 8 layers · 8 findings · 16 questions

Date Calendar facts.

Weekday

Computation.

Weekday

Weekday.

  1. On which weekday does March 31 fall in this year? measurement
  2. Is it a leap year? boundary

Calendar

Julian or Gregorian.

Calendar

Calendar system.

  1. Is the Julian or Gregorian calendar meant? boundary
  2. What is the equivalent date in the other calendar? measurement
Observances Holidays.

Holiday

Public holiday.

Holiday

Holiday status.

  1. Is March 31 a public holiday or observance here? provenance
  2. Which tradition or law sets it? provenance

Attribution

Traditions.

Attribution

Attributed observances.

  1. Which countries or communities observe something on this date, according to them? provenance
  2. Is the observance attributed rather than assumed? boundary
History Past events.

Events

On this day.

Events

Historical events.

  1. Which notable events happened on March 31, according to reliable sources? provenance
  2. Are dates given in the same calendar? boundary

Anniversaries

Recurring.

Anniversaries

Anniversaries.

  1. Which anniversaries fall on this date this year? provenance
  2. Which are round numbers? measurement
Planning Scheduling.

Countdown

Days until.

Countdown

Countdown.

  1. How many days until the next March 31? measurement
  2. From which date? definition

Work

Working day.

Work

Working day.

  1. Is it a working day for this organisation? provenance
  2. Do deadlines move? boundary

Classifiers Filled

Family
Thing Registry
Category
Cross-cutting context
Entry kind
thing
Plane
XCT
Domain
XCT.TME

What it is Filled

March 31, day 90 (day 91 in leap years) of the year in the Gregorian calendar, with 275 days remaining in both common and leap years. Observances on this date vary by country and tradition; it is the last day of March and of the first quarter of the year.

Why it exists Filled

Let an agent handle March 31 as a calendar date with weekday computation, observances attributed to their traditions and sourced events.

Distinguishing features Filled

  • The thirty-first day of March
  • Weekday varies by year
  • Observances vary by place
  • Julian and Gregorian dates differ by 13 days in this era

What robots and AI may and may not do Filled

Must not

  • Present a national or religious observance on March 31 as universal.
  • Assume a quarter or financial year ends on March 31 for an organization without checking.
  • Report events on March 31 without a source.
  • Mix Julian and Gregorian dates when giving historical events on March 31.

Only with a human decision

  • Filing or committing to financial or tax deadlines that fall on March 31.

May

  • Compute the weekday of March 31 in any given year.
  • Note that March 31 ends March and the first calendar quarter, and that financial years may differ.
  • List observances on March 31 with the country or tradition that holds each.

Moral aspects Filled

  • Deadlines on quarter and year ends carry penalties when misreported.
  • Lists of events can favour some countries and forget others.

Who is affected

  • Taxpayers and businesses
  • Readers of calendars

Owners Filled

Steward

Nobody owns it; the Gregorian calendar is held in common.

Links to other meta-models Filled

parent

  • Q11187583 - registry parent class

related

  • March - month
  • March 30 - date
  • calendar date - category
  • ISO 8601 - notation

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • Vercy registry: vr.tr.march-31
  • Wikidata: Q2461 (https://www.wikidata.org/wiki/Q2461)
  • ISO 8601: --03-31 recurring date

Direct properties not applicable Not applicable

  • day of year: 90 or 91 day - common year, leap year where different
  • days remaining: 275 days

Plane XCT: no invented physical properties.

Recognition optional Filled

  • Written 31 March or March 31
  • ISO format --03-31
  • Observances vary by country and tradition
  • A date on calendars.

Capabilities and actions required Filled

  • compute its weekday in a given year
  • check local and international observances
  • find sourced historical events
  • schedule events

Hazards and failure modes required Filled

  • Assuming observances are universal
  • Unsourced on-this-day events
  • Mixing Julian and Gregorian dates

Standards and interfaces required Filled

  • ISO 8601
  • National public holiday laws

Context of use required Filled

  • A calendar date for scheduling, holidays and anniversaries.
  • the recurring calendar date
  • specific dated days in given years

Sources Filled

  1. Wikidata item Q2461: March 31 - identity and sense of the item
  2. Wikipedia: March 31 - general description of the item

Open questions

  • Should dated days be separate entries?
  • How should observances be linked?
  • How should events be sourced?

Machine files

Card as JSON Specification Card backlog vercy.card/1

Provenance

thing registry research (pass 2) · unreviewed

Built from: models/things/publications/thing-q2461/spec.json