← Back to catalogue
Published

Reservation / Booking

vr.wm-eco-023 · wm-eco-023-reservation-booking

Represent one governed request, hold and confirmation lifecycle for scarce or scheduled capacity so agents can understand what is sought, for whom, from which provider, under which terms, at what time and place, and with what operational evidence without confusing the reservation with inventory, contract, order, ticket, payment or fulfilment.

World Models Society, people and institutions SOC.ECO.RSV
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

6 bundles · 12 layers · 24 findings · 72 questions

Identity, intent, parties and authority Groups reservation context for identity, intent, parties and authority.

Reservation root identity, version, profile and status

Groups source-qualified reservation context for reservation root identity, version, profile and status.

Reservation ID, version head, alias, profile, status and master system

Records reservation id, version head, alias, profile, status and master system as source-qualified reservation context while party, offering, inventory, availability, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain independently identifiable.

  1. What stable reservation, version, request, segment, unit, party, reserved-subject and external-master identities plus explicit profile and unknown state establish reservation id, version head, alias, profile, status and master system? identity
  2. Who requests, books, provides, holds, benefits, guarantees, confirms, modifies, cancels, verifies or may rely on reservation id, version head, alias, profile, status and master system, for which purpose and under what authority? authority
  3. Which desired, observed, offered, held, confirmed, modified, cancelled, expired, checked-in, fulfilled, recorded, ingested and known times, sources and evidence qualify reservation id, version head, alias, profile, status and master system? security

Requested, held, confirmed, waitlisted, cancelled, expired, no-show and disputed classification

Records requested, held, confirmed, waitlisted, cancelled, expired, no-show and disputed classification as source-qualified reservation context while party, offering, inventory, availability, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain independently identifiable.

  1. What stable reservation, version, request, segment, unit, party, reserved-subject and external-master identities plus explicit profile and unknown state establish requested, held, confirmed, waitlisted, cancelled, expired, no-show and disputed classification? classification
  2. Who requests, books, provides, holds, benefits, guarantees, confirms, modifies, cancels, verifies or may rely on requested, held, confirmed, waitlisted, cancelled, expired, no-show and disputed classification, for which purpose and under what authority? requirement
  3. Which desired, observed, offered, held, confirmed, modified, cancelled, expired, checked-in, fulfilled, recorded, ingested and known times, sources and evidence qualify requested, held, confirmed, waitlisted, cancelled, expired, no-show and disputed classification? privacy

Purpose, parties, roles, contact and authority

Groups source-qualified reservation context for purpose, parties, roles, contact and authority.

Requester, booker, holder, beneficiary, provider, broker, payer, contact and operator role

Records requester, booker, holder, beneficiary, provider, broker, payer, contact and operator role as source-qualified reservation context while party, offering, inventory, availability, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain independently identifiable.

  1. What stable reservation, version, request, segment, unit, party, reserved-subject and external-master identities plus explicit profile and unknown state establish requester, booker, holder, beneficiary, provider, broker, payer, contact and operator role? relationship
  2. Who requests, books, provides, holds, benefits, guarantees, confirms, modifies, cancels, verifies or may rely on requester, booker, holder, beneficiary, provider, broker, payer, contact and operator role, for which purpose and under what authority? constraint
  3. Which desired, observed, offered, held, confirmed, modified, cancelled, expired, checked-in, fulfilled, recorded, ingested and known times, sources and evidence qualify requester, booker, holder, beneficiary, provider, broker, payer, contact and operator role? retention

Purpose, authorization, delegation, consent, acknowledgement, reliance and restriction

Records purpose, authorization, delegation, consent, acknowledgement, reliance and restriction as source-qualified reservation context while party, offering, inventory, availability, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain independently identifiable.

  1. What stable reservation, version, request, segment, unit, party, reserved-subject and external-master identities plus explicit profile and unknown state establish purpose, authorization, delegation, consent, acknowledgement, reliance and restriction? authority
  2. Who requests, books, provides, holds, benefits, guarantees, confirms, modifies, cancels, verifies or may rely on purpose, authorization, delegation, consent, acknowledgement, reliance and restriction, for which purpose and under what authority? process
  3. Which desired, observed, offered, held, confirmed, modified, cancelled, expired, checked-in, fulfilled, recorded, ingested and known times, sources and evidence qualify purpose, authorization, delegation, consent, acknowledgement, reliance and restriction? access
Availability, capacity, composition and preferences Groups reservation context for availability, capacity, composition and preferences.

Availability, offering, slot, capacity and allocation

Groups source-qualified reservation context for availability, offering, slot, capacity and allocation.

Availability query, observation, offering, resource, slot, class, channel and source

Records availability query, observation, offering, resource, slot, class, channel and source as source-qualified reservation context while party, offering, inventory, availability, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain independently identifiable.

  1. What stable reservation, version, request, segment, unit, party, reserved-subject and external-master identities plus explicit profile and unknown state establish availability query, observation, offering, resource, slot, class, channel and source? measurement
  2. Who requests, books, provides, holds, benefits, guarantees, confirms, modifies, cancels, verifies or may rely on availability query, observation, offering, resource, slot, class, channel and source, for which purpose and under what authority? event
  3. Which desired, observed, offered, held, confirmed, modified, cancelled, expired, checked-in, fulfilled, recorded, ingested and known times, sources and evidence qualify availability query, observation, offering, resource, slot, class, channel and source? exception

Inventory pool, quota, capacity unit, hold, allocation, guarantee, overbooking and release

Records inventory pool, quota, capacity unit, hold, allocation, guarantee, overbooking and release as source-qualified reservation context while party, offering, inventory, availability, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain independently identifiable.

  1. What stable reservation, version, request, segment, unit, party, reserved-subject and external-master identities plus explicit profile and unknown state establish inventory pool, quota, capacity unit, hold, allocation, guarantee, overbooking and release? constraint
  2. Who requests, books, provides, holds, benefits, guarantees, confirms, modifies, cancels, verifies or may rely on inventory pool, quota, capacity unit, hold, allocation, guarantee, overbooking and release, for which purpose and under what authority? measurement
  3. Which desired, observed, offered, held, confirmed, modified, cancelled, expired, checked-in, fulfilled, recorded, ingested and known times, sources and evidence qualify inventory pool, quota, capacity unit, hold, allocation, guarantee, overbooking and release? interoperability

Segments, units, party composition, preferences and dependencies

Groups source-qualified reservation context for segments, units, party composition, preferences and dependencies.

Segment, leg, stay, session, sub-event, sub-reservation, package, sequence and link

Records segment, leg, stay, session, sub-event, sub-reservation, package, sequence and link as source-qualified reservation context while party, offering, inventory, availability, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain independently identifiable.

  1. What stable reservation, version, request, segment, unit, party, reserved-subject and external-master identities plus explicit profile and unknown state establish segment, leg, stay, session, sub-event, sub-reservation, package, sequence and link? composition
  2. Who requests, books, provides, holds, benefits, guarantees, confirms, modifies, cancels, verifies or may rely on segment, leg, stay, session, sub-event, sub-reservation, package, sequence and link, for which purpose and under what authority? evidence
  3. Which desired, observed, offered, held, confirmed, modified, cancelled, expired, checked-in, fulfilled, recorded, ingested and known times, sources and evidence qualify segment, leg, stay, session, sub-event, sub-reservation, package, sequence and link? decision

Quantity, party composition, seat, room, table, slot, accessibility, preference, alternative and dependency

Records quantity, party composition, seat, room, table, slot, accessibility, preference, alternative and dependency as source-qualified reservation context while party, offering, inventory, availability, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain independently identifiable.

  1. What stable reservation, version, request, segment, unit, party, reserved-subject and external-master identities plus explicit profile and unknown state establish quantity, party composition, seat, room, table, slot, accessibility, preference, alternative and dependency? composition
  2. Who requests, books, provides, holds, benefits, guarantees, confirms, modifies, cancels, verifies or may rely on quantity, party composition, seat, room, table, slot, accessibility, preference, alternative and dependency, for which purpose and under what authority? quality
  3. Which desired, observed, offered, held, confirmed, modified, cancelled, expired, checked-in, fulfilled, recorded, ingested and known times, sources and evidence qualify quantity, party composition, seat, room, table, slot, accessibility, preference, alternative and dependency? identity
Terms, economics, guarantees and external commerce Groups reservation context for terms, economics, guarantees and external commerce.

Rate, price, tax, deposit, guarantee and charge policy

Groups source-qualified reservation context for rate, price, tax, deposit, guarantee and charge policy.

Rate plan, quoted price, currency, tax, fee, discount, validity and source

Records rate plan, quoted price, currency, tax, fee, discount, validity and source as source-qualified reservation context while party, offering, inventory, availability, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain independently identifiable.

  1. What stable reservation, version, request, segment, unit, party, reserved-subject and external-master identities plus explicit profile and unknown state establish rate plan, quoted price, currency, tax, fee, discount, validity and source? measurement
  2. Who requests, books, provides, holds, benefits, guarantees, confirms, modifies, cancels, verifies or may rely on rate plan, quoted price, currency, tax, fee, discount, validity and source, for which purpose and under what authority? validation
  3. Which desired, observed, offered, held, confirmed, modified, cancelled, expired, checked-in, fulfilled, recorded, ingested and known times, sources and evidence qualify rate plan, quoted price, currency, tax, fee, discount, validity and source? classification

Deposit, payment guarantee, cancellation, no-show, change, refund and penalty policy

Records deposit, payment guarantee, cancellation, no-show, change, refund and penalty policy as source-qualified reservation context while party, offering, inventory, availability, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain independently identifiable.

  1. What stable reservation, version, request, segment, unit, party, reserved-subject and external-master identities plus explicit profile and unknown state establish deposit, payment guarantee, cancellation, no-show, change, refund and penalty policy? requirement
  2. Who requests, books, provides, holds, benefits, guarantees, confirms, modifies, cancels, verifies or may rely on deposit, payment guarantee, cancellation, no-show, change, refund and penalty policy, for which purpose and under what authority? security
  3. Which desired, observed, offered, held, confirmed, modified, cancelled, expired, checked-in, fulfilled, recorded, ingested and known times, sources and evidence qualify deposit, payment guarantee, cancellation, no-show, change, refund and penalty policy? composition

Offer, contract, order, ticket, payment and eligibility bindings

Groups source-qualified reservation context for offer, contract, order, ticket, payment and eligibility bindings.

Offer, quote, contract, order, ticket, entitlement, invoice, payment and refund reference

Records offer, quote, contract, order, ticket, entitlement, invoice, payment and refund reference as source-qualified reservation context while party, offering, inventory, availability, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain independently identifiable.

  1. What stable reservation, version, request, segment, unit, party, reserved-subject and external-master identities plus explicit profile and unknown state establish offer, quote, contract, order, ticket, entitlement, invoice, payment and refund reference? relationship
  2. Who requests, books, provides, holds, benefits, guarantees, confirms, modifies, cancels, verifies or may rely on offer, quote, contract, order, ticket, entitlement, invoice, payment and refund reference, for which purpose and under what authority? privacy
  3. Which desired, observed, offered, held, confirmed, modified, cancelled, expired, checked-in, fulfilled, recorded, ingested and known times, sources and evidence qualify offer, quote, contract, order, ticket, entitlement, invoice, payment and refund reference? relationship

Eligibility, identity document, membership, loyalty, voucher, promotion and verification

Records eligibility, identity document, membership, loyalty, voucher, promotion and verification as source-qualified reservation context while party, offering, inventory, availability, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain independently identifiable.

  1. What stable reservation, version, request, segment, unit, party, reserved-subject and external-master identities plus explicit profile and unknown state establish eligibility, identity document, membership, loyalty, voucher, promotion and verification? validation
  2. Who requests, books, provides, holds, benefits, guarantees, confirms, modifies, cancels, verifies or may rely on eligibility, identity document, membership, loyalty, voucher, promotion and verification, for which purpose and under what authority? retention
  3. Which desired, observed, offered, held, confirmed, modified, cancelled, expired, checked-in, fulfilled, recorded, ingested and known times, sources and evidence qualify eligibility, identity document, membership, loyalty, voucher, promotion and verification? state
Request, hold, confirmation, change and cancellation Groups reservation context for request, hold, confirmation, change and cancellation.

Request, response, hold, waitlist, confirmation and state axes

Groups source-qualified reservation context for request, response, hold, waitlist, confirmation and state axes.

Request action, correlation, response, decision, reason, confirmation code and evidence

Records request action, correlation, response, decision, reason, confirmation code and evidence as source-qualified reservation context while party, offering, inventory, availability, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain independently identifiable.

  1. What stable reservation, version, request, segment, unit, party, reserved-subject and external-master identities plus explicit profile and unknown state establish request action, correlation, response, decision, reason, confirmation code and evidence? process
  2. Who requests, books, provides, holds, benefits, guarantees, confirms, modifies, cancels, verifies or may rely on request action, correlation, response, decision, reason, confirmation code and evidence, for which purpose and under what authority? access
  3. Which desired, observed, offered, held, confirmed, modified, cancelled, expired, checked-in, fulfilled, recorded, ingested and known times, sources and evidence qualify request action, correlation, response, decision, reason, confirmation code and evidence? lifecycle

Commercial, capacity, hold, booking, payment, ticket, check-in and fulfilment state axis

Records commercial, capacity, hold, booking, payment, ticket, check-in and fulfilment state axis as source-qualified reservation context while party, offering, inventory, availability, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain independently identifiable.

  1. What stable reservation, version, request, segment, unit, party, reserved-subject and external-master identities plus explicit profile and unknown state establish commercial, capacity, hold, booking, payment, ticket, check-in and fulfilment state axis? state
  2. Who requests, books, provides, holds, benefits, guarantees, confirms, modifies, cancels, verifies or may rely on commercial, capacity, hold, booking, payment, ticket, check-in and fulfilment state axis, for which purpose and under what authority? exception
  3. Which desired, observed, offered, held, confirmed, modified, cancelled, expired, checked-in, fulfilled, recorded, ingested and known times, sources and evidence qualify commercial, capacity, hold, booking, payment, ticket, check-in and fulfilment state axis? temporal

Modify, rebook, split, merge, transfer, cancel, expire and release

Groups source-qualified reservation context for modify, rebook, split, merge, transfer, cancel, expire and release.

Modification, rebook, substitution, upgrade, downgrade, split, merge, transfer and successor

Records modification, rebook, substitution, upgrade, downgrade, split, merge, transfer and successor as source-qualified reservation context while party, offering, inventory, availability, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain independently identifiable.

  1. What stable reservation, version, request, segment, unit, party, reserved-subject and external-master identities plus explicit profile and unknown state establish modification, rebook, substitution, upgrade, downgrade, split, merge, transfer and successor? lifecycle
  2. Who requests, books, provides, holds, benefits, guarantees, confirms, modifies, cancels, verifies or may rely on modification, rebook, substitution, upgrade, downgrade, split, merge, transfer and successor, for which purpose and under what authority? interoperability
  3. Which desired, observed, offered, held, confirmed, modified, cancelled, expired, checked-in, fulfilled, recorded, ingested and known times, sources and evidence qualify modification, rebook, substitution, upgrade, downgrade, split, merge, transfer and successor? spatial

Cancellation request, cancellation effective, expiry, no-show, release, refund, dispute and correction

Records cancellation request, cancellation effective, expiry, no-show, release, refund, dispute and correction as source-qualified reservation context while party, offering, inventory, availability, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain independently identifiable.

  1. What stable reservation, version, request, segment, unit, party, reserved-subject and external-master identities plus explicit profile and unknown state establish cancellation request, cancellation effective, expiry, no-show, release, refund, dispute and correction? event
  2. Who requests, books, provides, holds, benefits, guarantees, confirms, modifies, cancels, verifies or may rely on cancellation request, cancellation effective, expiry, no-show, release, refund, dispute and correction, for which purpose and under what authority? decision
  3. Which desired, observed, offered, held, confirmed, modified, cancelled, expired, checked-in, fulfilled, recorded, ingested and known times, sources and evidence qualify cancellation request, cancellation effective, expiry, no-show, release, refund, dispute and correction? provenance
Time, place, check-in, fulfilment and outcome Groups reservation context for time, place, check-in, fulfilment and outcome.

Schedule, timezone, location, route and cutoffs

Groups source-qualified reservation context for schedule, timezone, location, route and cutoffs.

Desired, offered, held and confirmed start, end, duration, recurrence, timezone and exception

Records desired, offered, held and confirmed start, end, duration, recurrence, timezone and exception as source-qualified reservation context while party, offering, inventory, availability, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain independently identifiable.

  1. What stable reservation, version, request, segment, unit, party, reserved-subject and external-master identities plus explicit profile and unknown state establish desired, offered, held and confirmed start, end, duration, recurrence, timezone and exception? temporal
  2. Who requests, books, provides, holds, benefits, guarantees, confirms, modifies, cancels, verifies or may rely on desired, offered, held and confirmed start, end, duration, recurrence, timezone and exception, for which purpose and under what authority? identity
  3. Which desired, observed, offered, held, confirmed, modified, cancelled, expired, checked-in, fulfilled, recorded, ingested and known times, sources and evidence qualify desired, offered, held and confirmed start, end, duration, recurrence, timezone and exception? ownership

Origin, destination, venue, place, resource position, route, zone and jurisdiction reference

Records origin, destination, venue, place, resource position, route, zone and jurisdiction reference as source-qualified reservation context while party, offering, inventory, availability, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain independently identifiable.

  1. What stable reservation, version, request, segment, unit, party, reserved-subject and external-master identities plus explicit profile and unknown state establish origin, destination, venue, place, resource position, route, zone and jurisdiction reference? spatial
  2. Who requests, books, provides, holds, benefits, guarantees, confirms, modifies, cancels, verifies or may rely on origin, destination, venue, place, resource position, route, zone and jurisdiction reference, for which purpose and under what authority? classification
  3. Which desired, observed, offered, held, confirmed, modified, cancelled, expired, checked-in, fulfilled, recorded, ingested and known times, sources and evidence qualify origin, destination, venue, place, resource position, route, zone and jurisdiction reference? authority

Arrival, check-in, admission, handover, fulfilment, no-show and outcome

Groups source-qualified reservation context for arrival, check-in, admission, handover, fulfilment, no-show and outcome.

Arrival, check-in, identity check, admission, boarding, pickup, handover and attendance reference

Records arrival, check-in, identity check, admission, boarding, pickup, handover and attendance reference as source-qualified reservation context while party, offering, inventory, availability, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain independently identifiable.

  1. What stable reservation, version, request, segment, unit, party, reserved-subject and external-master identities plus explicit profile and unknown state establish arrival, check-in, identity check, admission, boarding, pickup, handover and attendance reference? event
  2. Who requests, books, provides, holds, benefits, guarantees, confirms, modifies, cancels, verifies or may rely on arrival, check-in, identity check, admission, boarding, pickup, handover and attendance reference, for which purpose and under what authority? composition
  3. Which desired, observed, offered, held, confirmed, modified, cancelled, expired, checked-in, fulfilled, recorded, ingested and known times, sources and evidence qualify arrival, check-in, identity check, admission, boarding, pickup, handover and attendance reference? requirement

Service start, completion, partial fulfilment, no-show, failure, complaint, remedy and evidence

Records service start, completion, partial fulfilment, no-show, failure, complaint, remedy and evidence as source-qualified reservation context while party, offering, inventory, availability, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain independently identifiable.

  1. What stable reservation, version, request, segment, unit, party, reserved-subject and external-master identities plus explicit profile and unknown state establish service start, completion, partial fulfilment, no-show, failure, complaint, remedy and evidence? evidence
  2. Who requests, books, provides, holds, benefits, guarantees, confirms, modifies, cancels, verifies or may rely on service start, completion, partial fulfilment, no-show, failure, complaint, remedy and evidence, for which purpose and under what authority? relationship
  3. Which desired, observed, offered, held, confirmed, modified, cancelled, expired, checked-in, fulfilled, recorded, ingested and known times, sources and evidence qualify service start, completion, partial fulfilment, no-show, failure, complaint, remedy and evidence? constraint
Governance, provenance, privacy, validation and interoperability Groups reservation context for governance, provenance, privacy, validation and interoperability.

Ownership, source, revision, access, privacy and retention

Groups source-qualified reservation context for ownership, source, revision, access, privacy and retention.

Owner, steward, source system, channel, actor, derivation, revision, conflict and audit

Records owner, steward, source system, channel, actor, derivation, revision, conflict and audit as source-qualified reservation context while party, offering, inventory, availability, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain independently identifiable.

  1. What stable reservation, version, request, segment, unit, party, reserved-subject and external-master identities plus explicit profile and unknown state establish owner, steward, source system, channel, actor, derivation, revision, conflict and audit? provenance
  2. Who requests, books, provides, holds, benefits, guarantees, confirms, modifies, cancels, verifies or may rely on owner, steward, source system, channel, actor, derivation, revision, conflict and audit, for which purpose and under what authority? state
  3. Which desired, observed, offered, held, confirmed, modified, cancelled, expired, checked-in, fulfilled, recorded, ingested and known times, sources and evidence qualify owner, steward, source system, channel, actor, derivation, revision, conflict and audit? process

Purpose, contact, itinerary, access, confidentiality, disclosure, retention, legal hold and tombstone

Records purpose, contact, itinerary, access, confidentiality, disclosure, retention, legal hold and tombstone as source-qualified reservation context while party, offering, inventory, availability, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain independently identifiable.

  1. What stable reservation, version, request, segment, unit, party, reserved-subject and external-master identities plus explicit profile and unknown state establish purpose, contact, itinerary, access, confidentiality, disclosure, retention, legal hold and tombstone? privacy
  2. Who requests, books, provides, holds, benefits, guarantees, confirms, modifies, cancels, verifies or may rely on purpose, contact, itinerary, access, confidentiality, disclosure, retention, legal hold and tombstone, for which purpose and under what authority? lifecycle
  3. Which desired, observed, offered, held, confirmed, modified, cancelled, expired, checked-in, fulfilled, recorded, ingested and known times, sources and evidence qualify purpose, contact, itinerary, access, confidentiality, disclosure, retention, legal hold and tombstone? event

Validation, events, clocks and loss-aware projections

Groups source-qualified reservation context for validation, events, clocks and loss-aware projections.

Request, hold, confirm, modify, cancel, expire, check-in, fulfil, observation, ingestion and knowledge time

Records request, hold, confirm, modify, cancel, expire, check-in, fulfil, observation, ingestion and knowledge time as source-qualified reservation context while party, offering, inventory, availability, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain independently identifiable.

  1. What stable reservation, version, request, segment, unit, party, reserved-subject and external-master identities plus explicit profile and unknown state establish request, hold, confirm, modify, cancel, expire, check-in, fulfil, observation, ingestion and knowledge time? temporal
  2. Who requests, books, provides, holds, benefits, guarantees, confirms, modifies, cancels, verifies or may rely on request, hold, confirm, modify, cancel, expire, check-in, fulfil, observation, ingestion and knowledge time, for which purpose and under what authority? temporal
  3. Which desired, observed, offered, held, confirmed, modified, cancelled, expired, checked-in, fulfilled, recorded, ingested and known times, sources and evidence qualify request, hold, confirm, modify, cancel, expire, check-in, fulfil, observation, ingestion and knowledge time? measurement

Identity, capacity, state, term, arithmetic, policy, privacy, UN/EDIFACT, Schema.org, IATA, TMF, RFC, PROV and API validation

Records identity, capacity, state, term, arithmetic, policy, privacy, un/edifact, schema.org, iata, tmf, rfc, prov and api validation as source-qualified reservation context while party, offering, inventory, availability, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain independently identifiable.

  1. What stable reservation, version, request, segment, unit, party, reserved-subject and external-master identities plus explicit profile and unknown state establish identity, capacity, state, term, arithmetic, policy, privacy, un/edifact, schema.org, iata, tmf, rfc, prov and api validation? interoperability
  2. Who requests, books, provides, holds, benefits, guarantees, confirms, modifies, cancels, verifies or may rely on identity, capacity, state, term, arithmetic, policy, privacy, un/edifact, schema.org, iata, tmf, rfc, prov and api validation, for which purpose and under what authority? spatial
  3. Which desired, observed, offered, held, confirmed, modified, cancelled, expired, checked-in, fulfilled, recorded, ingested and known times, sources and evidence qualify identity, capacity, state, term, arithmetic, policy, privacy, un/edifact, schema.org, iata, tmf, rfc, prov and api validation? evidence

Classifiers Filled

Family
World Models
Category
Society, people and institutions
Entry kind
aggregate
Navigation path
NAV.SOC.ECO.RSV
Domain
SOC.ECO.RSV
Industry
Cross-industry
Tags
reservationbookingsoc.eco.rsv

What it is Filled

Owns reservation identity, versions, profiles and lifecycle; requester, booker, provider, beneficiary, broker, payer and contact bindings; reserved subject and external offering, inventory, availability and capacity references; segments, sub-reservations, units, quantities, party composition, preferences, accessibility needs, alternatives and dependencies; rate, price, tax, deposit, guarantee, cancellation, change, no-show and refund policy references; external offer, contract, order, ticket, entitlement, invoice and payment bindings; request, hold, waitlist, confirmation, modification, rebooking, split, merge, transfer, cancellation, expiry, no-show, correction and dispute assertions; desired, offered, held, confirmed, service, cancellation, check-in, fulfilment, observation and knowledge times; locations, routes, check-in and fulfilment evidence; provenance, privacy, retention, validation and loss-aware projections. External party, offering, inventory, contract, order, ticket, payment, schedule, location, fulfilment and records masters remain authoritative.

In scope

  • Reservation identity, versions, profiles, parties, reserved subject, availability and capacity references, composition, quantities, preferences and dependencies
  • Terms, guarantee and financial references, request, hold, confirmation, modification, cancellation, time, place, check-in and fulfilment evidence, governance, privacy, retention and projections

Out of scope

  • Owning Party, Account, Offering, Product, Service, Resource, Inventory, Availability, Capacity Ledger, Schedule, Calendar Event, Location, Offer, Contract, Order, Ticket, Entitlement, Invoice, Payment, Check-in, Fulfilment or Records masters
  • Treating requested, held, confirmed, paid, ticketed, checked-in, fulfilled, cancelled or expired status as universal proof of legal validity, capacity allocation, attendance, service completion, refund or release
  • Autonomous scarce-capacity commitment, contract acceptance, charging, refunding, ticketing, transfer, cancellation, sensitive disclosure or physical record disposition

Why it exists Filled

Represent one governed request, hold and confirmation lifecycle for scarce or scheduled capacity so agents can understand what is sought, for whom, from which provider, under which terms, at what time and place, and with what operational evidence without confusing the reservation with inventory, contract, order, ticket, payment or fulfilment.

Distinguishing features Filled

  • A request, hold and confirmation lifecycle for scarce or scheduled capacity.
  • Differs from a ticket, which is evidence of an entitlement to use the capacity.
  • Differs from an appointment or calendar event, which records time but not commercial terms.
  • Keeps confirmation, payment, ticketing, check-in and fulfilment states apart.

What robots and AI may and may not do Filled

Must not

  • Commit scarce capacity or accept terms without approval.
  • Charge or refund.
  • Issue tickets or transfer bookings.
  • Disclose itineraries or guest data.
  • Overbook beyond allowed policy.

Only with a human decision

  • Confirming a booking with financial commitment.
  • Cancelling with penalties.
  • Transferring a reservation to another person.

May

  • Search availability and draft a reservation request.
  • Place a provisional hold within delegated limits.
  • Track changes, cancellations and deadlines.
  • Notify travellers or guests of changes.

Moral aspects Filled

  • Itineraries reveal location and movement of people, a safety issue.
  • Accessibility needs and special requests are sensitive data.
  • Overbooking practices can harm vulnerable travellers.

Who is affected

  • Travellers, guests and patients
  • Providers
  • Brokers and agents

Owners Filled

Steward

Dimension owner, namespace authority, accountable reservation owner and delegated commercial, capacity, operational and legal authorities

Roles

Reservation owner
Own purpose, scope, profile, lifecycle, compatibility and accountable use.
Capacity and inventory steward
Own availability, pool, quota, allocation, overbooking and release-system bindings.
Commercial and policy owner
Own rates, terms, guarantees, cancellation, no-show, change and refund policy references.
Provider and operations steward
Own confirmation, check-in, admission, handover, fulfilment and exception bindings.
Privacy and legal authority
Own consent, notice, transfer, itinerary data, access, jurisdiction and retention limitations.
Reviewer and approving authority
Own validation, exceptions, segregation of duties and authorization for consequential changes.
Interoperability and records steward
Own mappings, conformance evidence, declared loss, legal hold and disposition policy.

Links to other meta-models Filled

references

  • WM-ECO-006 - Resolve the commercial agreement when one exists without granting reservation-owned mutation or cascade authority.
  • Party, Offering, Inventory, Availability, Capacity, Schedule, Location, Contract, Order, Ticket, Entitlement, Invoice, Payment, Check-in, Fulfilment and Records models - Resolve authoritative external identities, states, events and evidence without duplicating their lifecycles.

aligned

  • UN/EDIFACT RESREQ, RESRSP and IFTMBF; Schema.org Reservation; IATA ONE Order; TMF646 and TMF716; EU booking profiles; RFC 5545 and RFC 3339; PROV-O; ODRL; DQV; ISO 4217; OpenAPI 3.1.1 - Project version-pinned booking, transport, discovery, airline, resource, legal, temporal, provenance, policy, quality, currency and API views with declared loss.

neighbor

  • WM-ECO-006 Commercial Contract - The unfrozen parent agreement establishes obligations and legal terms. The reservation records capacity-seeking and booking lifecycle assertions and does not prove contract formation.
  • Availability, inventory, capacity and allocation - Availability is an observation and inventory systems own pools, quotas, units and allocation. The reservation stores source-qualified bindings and observed hold or release results.
  • Appointment, calendar event and reserved service - An appointment or calendar event represents scheduled interaction and the service owns execution. The reservation owns booking intent, terms and confirmation bindings.
  • Offer, contract, order, ticket, entitlement, invoice and payment - Each external commercial or fulfilment record has independent identity, state and authority; confirmation does not collapse or replace them.
  • UN/EDIFACT, Schema.org, IATA, TM Forum, EU law, RFC, PROV, ODRL, DQV, ISO 4217 and OpenAPI - Each representation has a distinct scope; every mapping is version-pinned, profile-qualified and loss-declaring.

parent

  • WM-ECO-006

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • Authoritative master-system identifier for reservation, version, request, segment, hold, confirmation, lifecycle event or artifact, qualified by provider namespace and record kind.
  • Governed globally resolvable reservation or artifact IRI.
  • Dimension UUID or ULID when neither preceding identifier exists.

Direct properties not applicable Not applicable

Not applicable

Institutional or informational subject: no invented physical properties.

Recognition optional Filled

  • A reservation names a provider, a beneficiary, a reserved resource, a time and place and a status.
  • Often confused with a ticket, an invoice, an appointment or an order.

Capabilities and actions required Filled

  • Draft reservation request: Governed operation to draft reservation request without autonomous contract formation, capacity commitment, financial execution, ticketing, disclosure or records disposition.
  • Evaluate availability reference: Governed operation to evaluate availability reference without autonomous contract formation, capacity commitment, financial execution, ticketing, disclosure or records disposition.
  • Place provisional hold: Governed operation to place provisional hold without autonomous contract formation, capacity commitment, financial execution, ticketing, disclosure or records disposition.
  • Confirm booking: Governed operation to confirm booking without autonomous contract formation, capacity commitment, financial execution, ticketing, disclosure or records disposition.
  • Compose or split reservation: Governed operation to compose or split reservation without autonomous contract formation, capacity commitment, financial execution, ticketing, disclosure or records disposition.
  • Modify or rebook: Governed operation to modify or rebook without autonomous contract formation, capacity commitment, financial execution, ticketing, disclosure or records disposition.
  • Cancel, expire or request release: Governed operation to cancel, expire or request release without autonomous contract formation, capacity commitment, financial execution, ticketing, disclosure or records disposition.
  • Record check-in, no-show or fulfilment reference: Governed operation to record check-in, no-show or fulfilment reference without autonomous contract formation, capacity commitment, financial execution, ticketing, disclosure or records disposition.
  • Validate and reconcile reservation: Governed operation to validate and reconcile reservation without autonomous contract formation, capacity commitment, financial execution, ticketing, disclosure or records disposition.
  • Query, project, retain and audit: Governed operation to query, project, retain and audit without autonomous contract formation, capacity commitment, financial execution, ticketing, disclosure or records disposition.

Hazards and failure modes required Filled

  • Lost bookings.
  • Double booking.
  • Itinerary data leaks.
  • Missed cancellation deadlines.

Standards and interfaces required Filled

  • UN/EDIFACT reservation and booking messages.
  • Schema.org Reservation types.
  • IATA passenger name record and NDC standards.
  • IETF RFC 5545 iCalendar.
  • ISO 4217 currency codes and ISO 8601 dates.

Context of use required Filled

  • Booking confirmation, transfer, cancellation, withdrawal, no-show, accessibility, identity, tax, fees, refunds and retention depend on governing law, sector, provider policy and party type.
  • EU package-travel and consumer rules are scoped profiles, not universal governing law; UN/EDIFACT transport and travel messages do not establish contract effect by themselves.

Sources Filled

  1. UN/EDIFACT Reservation request interactive message - United Nations Economic Commission for Europe
  2. UN/EDIFACT Reservation response interactive message - United Nations Economic Commission for Europe
  3. UN/EDIFACT Firm booking message - United Nations Economic Commission for Europe
  4. Reservation - Schema.org Community Group
  5. ReservationStatusType - Schema.org Community Group
  6. ReservationPackage - Schema.org Community Group
  7. Fulfilling with Orders: ONE Order Factsheet - International Air Transport Association
  8. Appointment Management API TMF646 - TM Forum
  9. Open API Directory - TM Forum
  10. Directive EU 2015/2302 on package travel and linked travel arrangements - European Union
  11. Directive 2011/83/EU on consumer rights - European Union
  12. Internet Calendaring and Scheduling Core Object Specification - Internet Engineering Task Force
  13. Date and Time on the Internet: Timestamps - Internet Engineering Task Force
  14. PROV-O: The PROV Ontology - World Wide Web Consortium
  15. ODRL Information Model 2.2 - World Wide Web Consortium
  16. Data on the Web Best Practices: Data Quality Vocabulary - World Wide Web Consortium
  17. Global Financial Data Standards: ISO 4217 Currency Codes - SIX Financial Information
  18. OpenAPI Specification 3.1.1 - OpenAPI Initiative

Open questions

  • Canonically approve the WM-ECO-006 relation and register Party, Offering, Inventory, Availability, Capacity, Schedule, Location, Contract, Order, Ticket, Entitlement, Payment, Check-in, Fulfilment and Records edges.
  • Create airline, rail, hotel, restaurant, medical, event, rental, logistics, facility and jurisdiction-specific profiles and code lists.
  • Conformance-test request, hold, confirmation, modification, cancellation, release, time, composition and projection mappings against concrete implementations.
  • Validate organization-specific capacity, overbooking, guarantee, cancellation, no-show, transfer, accessibility, privacy, retention and emergency-access policies.
  • Obtain authorized legal, consumer, financial and sector review before making jurisdiction-specific or contract-effect claims.
  • Obtain independent external research review before promoting beyond reviewable-draft assurance.
  • Claude and Grok each timed out on one bounded attempt; no independent external result was admitted.
  • The WM-ECO-006 parent signal has no frozen approved relation and grants no cascade authority.
  • Airline, rail, hotel, restaurant, medical, event, rental, logistics, facility and other domain profiles need separate rules and code lists.
  • National contract, consumer, identity, accessibility, payment, privacy, emergency-access and records rules require jurisdiction and sector profiles.
  • UN/EDIFACT, Schema.org, IATA and TM Forum sources are loss-aware projections and do not universally define legal booking effect or capacity truth.

Machine files

Card as JSON Specification AGENTS.md Source Card backlog vercy.card/1

Provenance

world-models research · reviewable-draft

Built from: models/wm-eco-023-reservation-booking/spec.yaml, ver-cy/world-models/card-supplements/wm-eco-023-reservation-booking.json