← Back to catalogue
Published

January 31

vr.tr.january-31 · thing-q2289

Let an agent handle January 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 January 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 January 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 January 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 January 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

January 31, day 31 of the year in the Gregorian calendar, with 334 days remaining (335 in leap years). Observances on this date vary by country and tradition.

Why it exists Filled

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

Distinguishing features Filled

  • The thirty-first day of January
  • 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

  • Attribute an event to 31 January without a source.
  • Miss or misstate a 31 January filing deadline that a user has asked the agent to track.
  • Assume every month has a 31st day when scheduling recurring dates.

Only with a human decision

  • Submitting filings due on 31 January on someone's behalf.

May

  • Report events, births and observances on 31 January with sources.
  • Flag 31 January as a common end-of-month deadline when it applies to a user's own commitments.

Moral aspects Filled

  • Missed deadlines at month end can cost people money or legal standing.

Who is affected

  • People with deadlines on the date
  • Readers of historical records

Owners Filled

Steward

Nobody owns a date; the Gregorian calendar is held in common.

Links to other meta-models Filled

parent

  • Q11187583 - registry parent class

related

  • January - month
  • January 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.january-31
  • Wikidata: Q2289 (https://www.wikidata.org/wiki/Q2289)
  • ISO 8601: --01-31 recurring date

Direct properties not applicable Not applicable

  • day of year: 31 day - common year, leap year where different
  • days remaining: 334 or 335 days

Plane XCT: no invented physical properties.

Recognition optional Filled

  • Written 31 January or January 31
  • ISO format --01-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 Q2289: January 31 - identity and sense of the item
  2. Wikipedia: January 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-q2289/spec.json