← Back to catalogue
Published

January 3

vr.tr.january-3 · thing-q2156

Let an agent handle January 3 as a calendar date with weekday computation, observances 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 3 fall in this year? measurement
  2. Is it a leap year? boundary

Format

Notation.

Format

Date format.

  1. How should the date be written for this audience? action
  2. Is the Julian or Gregorian calendar meant? boundary
Observances Holidays.

Holiday

Public holiday.

Holiday

Holiday status.

  1. Is January 3 a public holiday or observance here? provenance
  2. Which calendar or tradition sets it? provenance

Closures

Services.

Closures

Closures.

  1. Which services are closed or reduced? provenance
  2. Where can emergency help be found? action
History Past events.

Events

On this day.

Events

Historical events.

  1. Which notable events happened on January 3, 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 3? 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 3, the third day of the year in the Gregorian calendar, with 362 days remaining (363 in leap years).

Why it exists Filled

Let an agent handle January 3 as a calendar date with weekday computation, observances and sourced events.

Distinguishing features Filled

  • Early January date
  • Often in the New Year holiday period
  • Weekday varies by year
  • Some churches using the Julian calendar observe feasts on shifted dates

What robots and AI may and may not do Filled

Must not

  • Present an observance as universal when it is national, religious or local.
  • State on-this-day events without a source.
  • Mix Julian and Gregorian dates without saying which calendar is used.
  • Infer anything about a person from their birth date.

Only with a human decision

  • Publishing a date list used for official or commemorative purposes.

May

  • Give the date's position in the calendar and convert it between calendars, stating which.
  • Report observances or events on this date with a source and the places they apply to.

Moral aspects Filled

  • Commemorative dates carry religious and national meaning that differs between communities.
  • Wrong calendar conversion misplaces historical events by days.

Who is affected

  • Readers of historical records
  • Religious and national communities
  • Archivists

Owners Filled

Steward

Nobody: a calendar date held in common.

Links to other meta-models Filled

parent

  • Q11187733 - registry parent class

related

  • January - month
  • January 2 - 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-3
  • Wikidata: Q2156 (https://www.wikidata.org/wiki/Q2156)
  • ISO 8601: --01-03 recurring date

Direct properties not applicable Not applicable

  • day of year: 3 day
  • days remaining: 362 or 363 days - common or leap year

Plane XCT: no invented physical properties.

Recognition optional Filled

  • Written 3 January or January 3
  • ISO format --01-03
  • Observances vary by country and church calendar
  • A date on calendars.

Capabilities and actions required Filled

  • compute its weekday in a given year
  • check local 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 Q2156: January 3 - identity and sense of the item
  2. Wikipedia: January 3 - general description of the item

Open questions

  • Should dated days be separate entries?
  • How should regional 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-q2156/spec.json