← Back to catalogue
Published

Wednesday

vr.tr.wednesday · thing-q128

Let an agent handle Wednesday as a weekday with numbering conventions, working-time rules and named occurrences.

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

Calendar Numbering.

Number

ISO and others.

Numbering

Weekday number.

  1. Which number does Wednesday have in this system? definition
  2. Does the week start on Monday or Sunday here? boundary

Date

Which occurrence.

Occurrence

Specific date.

  1. Which Wednesday is meant? definition
  2. Was the weekday computed correctly? boundary
Work Working patterns.

Status

Working day.

Status

Working status.

  1. Is Wednesday a working day here? boundary
  2. Which sectors differ? boundary

Hours

Opening.

Hours

Opening hours.

  1. Which opening rules apply? boundary
  2. Are public services open? definition
Named occurrences Special days.

Names

Named days.

Named days

Named occurrences.

  1. Which named Wednesdays fall this year? measurement
  2. What do they mark? definition

Customs

Observances.

Customs

Customs.

  1. Which customs are tied to this day? definition
  2. Do they vary by culture? boundary
Deadlines Scheduling.

Time zones

Across zones.

Zones

Zone handling.

  1. Is it still Wednesday for all participants across zones? boundary
  2. How should the schedule be shown? action

Legal deadlines

Counting.

Deadlines

Deadline rules.

  1. How do legal deadlines treat this day? boundary
  2. Is it a business day? boundary

Classifiers Filled

Family
Thing Registry
Category
Cross-cutting context
Entry kind
thing
Plane
XCT
Domain
XCT.TME
Other names and narrower kinds
Easter Wednesday, June 10, 1914, 8 January 1800, January 27, 1897, January 29, 1913, February 3, 1909, March 15, 1837, 24 May 1854, June 17, 1914, September 18, 1907, November 18, 1925, 31 December 1845

What it is Filled

The day of the week between Tuesday and Thursday, day 3 in ISO 8601 weeks; the middle of the working week in many countries.

Why it exists Filled

Let an agent handle Wednesday as a weekday with numbering conventions, working-time rules and named occurrences.

Distinguishing features Filled

  • Day 3 in ISO weeks
  • Usually a working day
  • Named occurrences carry meaning
  • Specific dates in aliases are instances

What robots and AI may and may not do Filled

Must not

  • Mix up weekday numbering across conventions without saying which is used.
  • Schedule people for work on days they have declared unavailable.
  • Mistranslate weekday names in a way that shifts dates.

Only with a human decision

  • Changing shared schedules that fall on that day.

May

  • Compute dates and weekdays following ISO 8601.
  • Schedule tasks on Wednesdays as the user asks.

Moral aspects Filled

  • Calendars and rest days differ across cultures and faiths.
  • Scheduling errors cost people time and pay.

Who is affected

  • People whose schedules depend on it
  • Workers

Owners Filled

Steward

Nobody owns a weekday; the calendar is held in common.

Links to other meta-models Filled

parent

  • Q573 - registry parent class
  • Q819073 - registry parent class

related

  • day - weekday
  • week - seven days
  • working time law - rules
  • calendar date - dates

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • Vercy registry: vr.tr.wednesday
  • Wikidata: Q128 (https://www.wikidata.org/wiki/Q128)
  • ISO 8601 weekday number: 3 Monday is 1

Direct properties not applicable Not applicable

Not applicable

Plane XCT: no invented physical properties.

Recognition optional Filled

  • Calendar position between Tuesday and Thursday
  • ISO 8601 weekday number 3
  • Named occurrences such as Ash Wednesday and Easter Wednesday
  • Not a thing to see; a day on the calendar.

Capabilities and actions required Filled

  • schedule around it
  • number it as day 3 in ISO 8601
  • apply working-time rules
  • identify named occurrences

Hazards and failure modes required Filled

  • Week-start mismatches
  • Wrong weekday for historical dates

Standards and interfaces required Filled

  • ISO 8601
  • Working time law

Context of use required Filled

  • Scheduling, work patterns and observances.
  • ordinary occurrences
  • named occurrences such as Ash Wednesday and Easter Wednesday

Sources Filled

  1. Wikidata item Q128: Wednesday - identity and sense of the item
  2. Wikipedia: Wednesday - general description of the item

Open questions

  • Should weekdays share one parameterised model?
  • How should named occurrences be linked?
  • The registry entry has merged specific dates as aliases; should they be removed?

Machine files

Card as JSON Specification Card backlog vercy.card/1

Provenance

thing registry research (pass 2) · unreviewed

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