{"schema":"https://ver.cy/schemas/card/1.0.0","id":"vr.wm-eco-023","code":"wm-eco-023-reservation-booking","url":"https://ver.cy/models/wm-eco-023-reservation-booking/","name":"Reservation / Booking","alternateNames":[],"kind":"world-model","status":"published","version":"0.3.0-research.1","language":"en","classifiers":{"family":"World Models","category":"Society, people and institutions","entryKind":"aggregate","plane":"","domain":["SOC.ECO.RSV"],"industry":["Cross-industry"],"navPath":"NAV.SOC.ECO.RSV","tags":["reservation","booking","soc.eco.rsv"],"facets":{}},"whatItIs":"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.","purpose":"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.","scope":{"in":["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":["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"],"boundaries":[{"neighbor":"WM-ECO-006 Commercial Contract","distinction":"The unfrozen parent agreement establishes obligations and legal terms. The reservation records capacity-seeking and booking lifecycle assertions and does not prove contract formation."},{"neighbor":"Availability, inventory, capacity and allocation","distinction":"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."},{"neighbor":"Appointment, calendar event and reserved service","distinction":"An appointment or calendar event represents scheduled interaction and the service owns execution. The reservation owns booking intent, terms and confirmation bindings."},{"neighbor":"Offer, contract, order, ticket, entitlement, invoice and payment","distinction":"Each external commercial or fulfilment record has independent identity, state and authority; confirmation does not collapse or replace them."},{"neighbor":"UN/EDIFACT, Schema.org, IATA, TM Forum, EU law, RFC, PROV, ODRL, DQV, ISO 4217 and OpenAPI","distinction":"Each representation has a distinct scope; every mapping is version-pinned, profile-qualified and loss-declaring."}]},"distinguishingFeatures":["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."],"structure":{"bundles":[{"id":"identity-intent-parties-and-authority","name":"Identity, intent, parties and authority","description":"Groups reservation context for identity, intent, parties and authority.","layers":[{"id":"reservation-root-identity-version-profile-and-status","name":"Reservation root identity, version, profile and status","description":"Groups source-qualified reservation context for reservation root identity, version, profile and status.","findings":[{"id":"reservation-id-version-head-alias-profile-status-and-master-system","name":"Reservation ID, version head, alias, profile, status and master system","description":"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.","questions":[{"text":"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?","id":"reservation-id-version-head-alias-profile-status-and-master-system-q01","kind":"identity"},{"text":"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?","id":"reservation-id-version-head-alias-profile-status-and-master-system-q02","kind":"authority"},{"text":"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?","id":"reservation-id-version-head-alias-profile-status-and-master-system-q03","kind":"security"}]},{"id":"requested-held-confirmed-waitlisted-cancelled-expired-noshow-and-disputed-classification","name":"Requested, held, confirmed, waitlisted, cancelled, expired, no-show and disputed classification","description":"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.","questions":[{"text":"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?","id":"requested-held-confirmed-waitlisted-cancelled-expired-noshow-and-disputed-classification-q01","kind":"classification"},{"text":"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?","id":"requested-held-confirmed-waitlisted-cancelled-expired-noshow-and-disputed-classification-q02","kind":"requirement"},{"text":"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?","id":"requested-held-confirmed-waitlisted-cancelled-expired-noshow-and-disputed-classification-q03","kind":"privacy"}]}]},{"id":"purpose-parties-roles-contact-and-authority","name":"Purpose, parties, roles, contact and authority","description":"Groups source-qualified reservation context for purpose, parties, roles, contact and authority.","findings":[{"id":"requester-booker-holder-beneficiary-provider-broker-payer-contact-and-operator-role","name":"Requester, booker, holder, beneficiary, provider, broker, payer, contact and operator role","description":"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.","questions":[{"text":"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?","id":"requester-booker-holder-beneficiary-provider-broker-payer-contact-and-operator-role-q01","kind":"relationship"},{"text":"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?","id":"requester-booker-holder-beneficiary-provider-broker-payer-contact-and-operator-role-q02","kind":"constraint"},{"text":"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?","id":"requester-booker-holder-beneficiary-provider-broker-payer-contact-and-operator-role-q03","kind":"retention"}]},{"id":"purpose-authorization-delegation-consent-acknowledgement-reliance-and-restriction","name":"Purpose, authorization, delegation, consent, acknowledgement, reliance and restriction","description":"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.","questions":[{"text":"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?","id":"purpose-authorization-delegation-consent-acknowledgement-reliance-and-restriction-q01","kind":"authority"},{"text":"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?","id":"purpose-authorization-delegation-consent-acknowledgement-reliance-and-restriction-q02","kind":"process"},{"text":"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?","id":"purpose-authorization-delegation-consent-acknowledgement-reliance-and-restriction-q03","kind":"access"}]}]}]},{"id":"availability-capacity-composition-and-preferences","name":"Availability, capacity, composition and preferences","description":"Groups reservation context for availability, capacity, composition and preferences.","layers":[{"id":"availability-offering-slot-capacity-and-allocation","name":"Availability, offering, slot, capacity and allocation","description":"Groups source-qualified reservation context for availability, offering, slot, capacity and allocation.","findings":[{"id":"availability-query-observation-offering-resource-slot-class-channel-and-source","name":"Availability query, observation, offering, resource, slot, class, channel and source","description":"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.","questions":[{"text":"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?","id":"availability-query-observation-offering-resource-slot-class-channel-and-source-q01","kind":"measurement"},{"text":"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?","id":"availability-query-observation-offering-resource-slot-class-channel-and-source-q02","kind":"event"},{"text":"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?","id":"availability-query-observation-offering-resource-slot-class-channel-and-source-q03","kind":"exception"}]},{"id":"inventory-pool-quota-capacity-unit-hold-allocation-guarantee-overbooking-and-release","name":"Inventory pool, quota, capacity unit, hold, allocation, guarantee, overbooking and release","description":"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.","questions":[{"text":"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?","id":"inventory-pool-quota-capacity-unit-hold-allocation-guarantee-overbooking-and-release-q01","kind":"constraint"},{"text":"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?","id":"inventory-pool-quota-capacity-unit-hold-allocation-guarantee-overbooking-and-release-q02","kind":"measurement"},{"text":"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?","id":"inventory-pool-quota-capacity-unit-hold-allocation-guarantee-overbooking-and-release-q03","kind":"interoperability"}]}]},{"id":"segments-units-party-composition-preferences-and-dependencies","name":"Segments, units, party composition, preferences and dependencies","description":"Groups source-qualified reservation context for segments, units, party composition, preferences and dependencies.","findings":[{"id":"segment-leg-stay-session-subevent-subreservation-package-sequence-and-link","name":"Segment, leg, stay, session, sub-event, sub-reservation, package, sequence and link","description":"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.","questions":[{"text":"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?","id":"segment-leg-stay-session-subevent-subreservation-package-sequence-and-link-q01","kind":"composition"},{"text":"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?","id":"segment-leg-stay-session-subevent-subreservation-package-sequence-and-link-q02","kind":"evidence"},{"text":"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?","id":"segment-leg-stay-session-subevent-subreservation-package-sequence-and-link-q03","kind":"decision"}]},{"id":"quantity-party-composition-seat-room-table-slot-accessibility-preference-alternative-and-dependency","name":"Quantity, party composition, seat, room, table, slot, accessibility, preference, alternative and dependency","description":"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.","questions":[{"text":"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?","id":"quantity-party-composition-seat-room-table-slot-accessibility-preference-alternative-and-dependency-q01","kind":"composition"},{"text":"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?","id":"quantity-party-composition-seat-room-table-slot-accessibility-preference-alternative-and-dependency-q02","kind":"quality"},{"text":"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?","id":"quantity-party-composition-seat-room-table-slot-accessibility-preference-alternative-and-dependency-q03","kind":"identity"}]}]}]},{"id":"terms-economics-guarantees-and-external-commerce","name":"Terms, economics, guarantees and external commerce","description":"Groups reservation context for terms, economics, guarantees and external commerce.","layers":[{"id":"rate-price-tax-deposit-guarantee-and-charge-policy","name":"Rate, price, tax, deposit, guarantee and charge policy","description":"Groups source-qualified reservation context for rate, price, tax, deposit, guarantee and charge policy.","findings":[{"id":"rate-plan-quoted-price-currency-tax-fee-discount-validity-and-source","name":"Rate plan, quoted price, currency, tax, fee, discount, validity and source","description":"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.","questions":[{"text":"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?","id":"rate-plan-quoted-price-currency-tax-fee-discount-validity-and-source-q01","kind":"measurement"},{"text":"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?","id":"rate-plan-quoted-price-currency-tax-fee-discount-validity-and-source-q02","kind":"validation"},{"text":"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?","id":"rate-plan-quoted-price-currency-tax-fee-discount-validity-and-source-q03","kind":"classification"}]},{"id":"deposit-payment-guarantee-cancellation-noshow-change-refund-and-penalty-policy","name":"Deposit, payment guarantee, cancellation, no-show, change, refund and penalty policy","description":"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.","questions":[{"text":"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?","id":"deposit-payment-guarantee-cancellation-noshow-change-refund-and-penalty-policy-q01","kind":"requirement"},{"text":"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?","id":"deposit-payment-guarantee-cancellation-noshow-change-refund-and-penalty-policy-q02","kind":"security"},{"text":"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?","id":"deposit-payment-guarantee-cancellation-noshow-change-refund-and-penalty-policy-q03","kind":"composition"}]}]},{"id":"offer-contract-order-ticket-payment-and-eligibility-bindings","name":"Offer, contract, order, ticket, payment and eligibility bindings","description":"Groups source-qualified reservation context for offer, contract, order, ticket, payment and eligibility bindings.","findings":[{"id":"offer-quote-contract-order-ticket-entitlement-invoice-payment-and-refund-reference","name":"Offer, quote, contract, order, ticket, entitlement, invoice, payment and refund reference","description":"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.","questions":[{"text":"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?","id":"offer-quote-contract-order-ticket-entitlement-invoice-payment-and-refund-reference-q01","kind":"relationship"},{"text":"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?","id":"offer-quote-contract-order-ticket-entitlement-invoice-payment-and-refund-reference-q02","kind":"privacy"},{"text":"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?","id":"offer-quote-contract-order-ticket-entitlement-invoice-payment-and-refund-reference-q03","kind":"relationship"}]},{"id":"eligibility-identity-document-membership-loyalty-voucher-promotion-and-verification","name":"Eligibility, identity document, membership, loyalty, voucher, promotion and verification","description":"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.","questions":[{"text":"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?","id":"eligibility-identity-document-membership-loyalty-voucher-promotion-and-verification-q01","kind":"validation"},{"text":"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?","id":"eligibility-identity-document-membership-loyalty-voucher-promotion-and-verification-q02","kind":"retention"},{"text":"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?","id":"eligibility-identity-document-membership-loyalty-voucher-promotion-and-verification-q03","kind":"state"}]}]}]},{"id":"request-hold-confirmation-change-and-cancellation","name":"Request, hold, confirmation, change and cancellation","description":"Groups reservation context for request, hold, confirmation, change and cancellation.","layers":[{"id":"request-response-hold-waitlist-confirmation-and-state-axes","name":"Request, response, hold, waitlist, confirmation and state axes","description":"Groups source-qualified reservation context for request, response, hold, waitlist, confirmation and state axes.","findings":[{"id":"request-action-correlation-response-decision-reason-confirmation-code-and-evidence","name":"Request action, correlation, response, decision, reason, confirmation code and evidence","description":"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.","questions":[{"text":"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?","id":"request-action-correlation-response-decision-reason-confirmation-code-and-evidence-q01","kind":"process"},{"text":"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?","id":"request-action-correlation-response-decision-reason-confirmation-code-and-evidence-q02","kind":"access"},{"text":"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?","id":"request-action-correlation-response-decision-reason-confirmation-code-and-evidence-q03","kind":"lifecycle"}]},{"id":"commercial-capacity-hold-booking-payment-ticket-checkin-and-fulfilment-state-axis","name":"Commercial, capacity, hold, booking, payment, ticket, check-in and fulfilment state axis","description":"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.","questions":[{"text":"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?","id":"commercial-capacity-hold-booking-payment-ticket-checkin-and-fulfilment-state-axis-q01","kind":"state"},{"text":"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?","id":"commercial-capacity-hold-booking-payment-ticket-checkin-and-fulfilment-state-axis-q02","kind":"exception"},{"text":"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?","id":"commercial-capacity-hold-booking-payment-ticket-checkin-and-fulfilment-state-axis-q03","kind":"temporal"}]}]},{"id":"modify-rebook-split-merge-transfer-cancel-expire-and-release","name":"Modify, rebook, split, merge, transfer, cancel, expire and release","description":"Groups source-qualified reservation context for modify, rebook, split, merge, transfer, cancel, expire and release.","findings":[{"id":"modification-rebook-substitution-upgrade-downgrade-split-merge-transfer-and-successor","name":"Modification, rebook, substitution, upgrade, downgrade, split, merge, transfer and successor","description":"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.","questions":[{"text":"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?","id":"modification-rebook-substitution-upgrade-downgrade-split-merge-transfer-and-successor-q01","kind":"lifecycle"},{"text":"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?","id":"modification-rebook-substitution-upgrade-downgrade-split-merge-transfer-and-successor-q02","kind":"interoperability"},{"text":"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?","id":"modification-rebook-substitution-upgrade-downgrade-split-merge-transfer-and-successor-q03","kind":"spatial"}]},{"id":"cancel-request-cancel-effective-expiry-noshow-release-refund-dispute-and-correction","name":"Cancellation request, cancellation effective, expiry, no-show, release, refund, dispute and correction","description":"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.","questions":[{"text":"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?","id":"cancel-request-cancel-effective-expiry-noshow-release-refund-dispute-and-correction-q01","kind":"event"},{"text":"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?","id":"cancel-request-cancel-effective-expiry-noshow-release-refund-dispute-and-correction-q02","kind":"decision"},{"text":"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?","id":"cancel-request-cancel-effective-expiry-noshow-release-refund-dispute-and-correction-q03","kind":"provenance"}]}]}]},{"id":"time-place-checkin-fulfilment-and-outcome","name":"Time, place, check-in, fulfilment and outcome","description":"Groups reservation context for time, place, check-in, fulfilment and outcome.","layers":[{"id":"schedule-timezone-location-route-and-cutoffs","name":"Schedule, timezone, location, route and cutoffs","description":"Groups source-qualified reservation context for schedule, timezone, location, route and cutoffs.","findings":[{"id":"desired-offered-held-confirmed-start-end-duration-recurrence-timezone-and-exception","name":"Desired, offered, held and confirmed start, end, duration, recurrence, timezone and exception","description":"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.","questions":[{"text":"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?","id":"desired-offered-held-confirmed-start-end-duration-recurrence-timezone-and-exception-q01","kind":"temporal"},{"text":"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?","id":"desired-offered-held-confirmed-start-end-duration-recurrence-timezone-and-exception-q02","kind":"identity"},{"text":"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?","id":"desired-offered-held-confirmed-start-end-duration-recurrence-timezone-and-exception-q03","kind":"ownership"}]},{"id":"origin-destination-venue-place-resource-position-route-zone-and-jurisdiction-reference","name":"Origin, destination, venue, place, resource position, route, zone and jurisdiction reference","description":"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.","questions":[{"text":"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?","id":"origin-destination-venue-place-resource-position-route-zone-and-jurisdiction-reference-q01","kind":"spatial"},{"text":"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?","id":"origin-destination-venue-place-resource-position-route-zone-and-jurisdiction-reference-q02","kind":"classification"},{"text":"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?","id":"origin-destination-venue-place-resource-position-route-zone-and-jurisdiction-reference-q03","kind":"authority"}]}]},{"id":"arrival-checkin-admission-handover-fulfilment-noshow-and-outcome","name":"Arrival, check-in, admission, handover, fulfilment, no-show and outcome","description":"Groups source-qualified reservation context for arrival, check-in, admission, handover, fulfilment, no-show and outcome.","findings":[{"id":"arrival-checkin-identity-check-admission-boarding-pickup-handover-and-attendance-reference","name":"Arrival, check-in, identity check, admission, boarding, pickup, handover and attendance reference","description":"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.","questions":[{"text":"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?","id":"arrival-checkin-identity-check-admission-boarding-pickup-handover-and-attendance-reference-q01","kind":"event"},{"text":"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?","id":"arrival-checkin-identity-check-admission-boarding-pickup-handover-and-attendance-reference-q02","kind":"composition"},{"text":"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?","id":"arrival-checkin-identity-check-admission-boarding-pickup-handover-and-attendance-reference-q03","kind":"requirement"}]},{"id":"service-start-completion-partial-fulfilment-noshow-failure-complaint-remedy-and-evidence","name":"Service start, completion, partial fulfilment, no-show, failure, complaint, remedy and evidence","description":"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.","questions":[{"text":"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?","id":"service-start-completion-partial-fulfilment-noshow-failure-complaint-remedy-and-evidence-q01","kind":"evidence"},{"text":"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?","id":"service-start-completion-partial-fulfilment-noshow-failure-complaint-remedy-and-evidence-q02","kind":"relationship"},{"text":"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?","id":"service-start-completion-partial-fulfilment-noshow-failure-complaint-remedy-and-evidence-q03","kind":"constraint"}]}]}]},{"id":"governance-provenance-privacy-validation-and-interoperability","name":"Governance, provenance, privacy, validation and interoperability","description":"Groups reservation context for governance, provenance, privacy, validation and interoperability.","layers":[{"id":"ownership-source-revision-access-privacy-and-retention","name":"Ownership, source, revision, access, privacy and retention","description":"Groups source-qualified reservation context for ownership, source, revision, access, privacy and retention.","findings":[{"id":"owner-steward-source-system-channel-actor-derivation-revision-conflict-and-audit","name":"Owner, steward, source system, channel, actor, derivation, revision, conflict and audit","description":"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.","questions":[{"text":"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?","id":"owner-steward-source-system-channel-actor-derivation-revision-conflict-and-audit-q01","kind":"provenance"},{"text":"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?","id":"owner-steward-source-system-channel-actor-derivation-revision-conflict-and-audit-q02","kind":"state"},{"text":"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?","id":"owner-steward-source-system-channel-actor-derivation-revision-conflict-and-audit-q03","kind":"process"}]},{"id":"purpose-contact-itinerary-access-confidentiality-disclosure-retention-legalhold-and-tombstone","name":"Purpose, contact, itinerary, access, confidentiality, disclosure, retention, legal hold and tombstone","description":"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.","questions":[{"text":"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?","id":"purpose-contact-itinerary-access-confidentiality-disclosure-retention-legalhold-and-tombstone-q01","kind":"privacy"},{"text":"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?","id":"purpose-contact-itinerary-access-confidentiality-disclosure-retention-legalhold-and-tombstone-q02","kind":"lifecycle"},{"text":"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?","id":"purpose-contact-itinerary-access-confidentiality-disclosure-retention-legalhold-and-tombstone-q03","kind":"event"}]}]},{"id":"validation-events-clocks-and-loss-aware-projections","name":"Validation, events, clocks and loss-aware projections","description":"Groups source-qualified reservation context for validation, events, clocks and loss-aware projections.","findings":[{"id":"request-hold-confirm-modify-cancel-expire-checkin-fulfil-observation-ingestion-and-knowledge-time","name":"Request, hold, confirm, modify, cancel, expire, check-in, fulfil, observation, ingestion and knowledge time","description":"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.","questions":[{"text":"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?","id":"request-hold-confirm-modify-cancel-expire-checkin-fulfil-observation-ingestion-and-knowledge-time-q01","kind":"temporal"},{"text":"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?","id":"request-hold-confirm-modify-cancel-expire-checkin-fulfil-observation-ingestion-and-knowledge-time-q02","kind":"temporal"},{"text":"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?","id":"request-hold-confirm-modify-cancel-expire-checkin-fulfil-observation-ingestion-and-knowledge-time-q03","kind":"measurement"}]},{"id":"identity-capacity-state-term-arithmetic-policy-privacy-unedifact-schemaorg-iata-tmf-rfc-prov-and-api-validation","name":"Identity, capacity, state, term, arithmetic, policy, privacy, UN/EDIFACT, Schema.org, IATA, TMF, RFC, PROV and API validation","description":"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.","questions":[{"text":"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?","id":"identity-capacity-state-term-arithmetic-policy-privacy-unedifact-schemaorg-iata-tmf-rfc-prov-and-api-validation-q01","kind":"interoperability"},{"text":"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?","id":"identity-capacity-state-term-arithmetic-policy-privacy-unedifact-schemaorg-iata-tmf-rfc-prov-and-api-validation-q02","kind":"spatial"},{"text":"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?","id":"identity-capacity-state-term-arithmetic-policy-privacy-unedifact-schemaorg-iata-tmf-rfc-prov-and-api-validation-q03","kind":"evidence"}]}]}]}]},"agentConduct":{"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."],"mustNot":["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."],"requiresHuman":["Confirming a booking with financial commitment.","Cancelling with penalties.","Transferring a reservation to another person."]},"ethics":{"considerations":["Itineraries reveal location and movement of people, a safety issue.","Accessibility needs and special requests are sensitive data.","Overbooking practices can harm vulnerable travellers."],"affectedParties":["Travellers, guests and patients","Providers","Brokers and agents"]},"owners":{"steward":"Dimension owner, namespace authority, accountable reservation owner and delegated commercial, capacity, operational and legal authorities","roles":[{"name":"Reservation owner","responsibilities":["Own purpose, scope, profile, lifecycle, compatibility and accountable use."]},{"name":"Capacity and inventory steward","responsibilities":["Own availability, pool, quota, allocation, overbooking and release-system bindings."]},{"name":"Commercial and policy owner","responsibilities":["Own rates, terms, guarantees, cancellation, no-show, change and refund policy references."]},{"name":"Provider and operations steward","responsibilities":["Own confirmation, check-in, admission, handover, fulfilment and exception bindings."]},{"name":"Privacy and legal authority","responsibilities":["Own consent, notice, transfer, itinerary data, access, jurisdiction and retention limitations."]},{"name":"Reviewer and approving authority","responsibilities":["Own validation, exceptions, segregation of duties and authorization for consequential changes."]},{"name":"Interoperability and records steward","responsibilities":["Own mappings, conformance evidence, declared loss, legal hold and disposition policy."]}],"masterSystems":[]},"relations":[{"target":"WM-ECO-006","type":"references","note":"Resolve the commercial agreement when one exists without granting reservation-owned mutation or cascade authority."},{"target":"Party, Offering, Inventory, Availability, Capacity, Schedule, Location, Contract, Order, Ticket, Entitlement, Invoice, Payment, Check-in, Fulfilment and Records models","type":"references","note":"Resolve authoritative external identities, states, events and evidence without duplicating their lifecycles."},{"target":"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","type":"aligned","note":"Project version-pinned booking, transport, discovery, airline, resource, legal, temporal, provenance, policy, quality, currency and API views with declared loss."},{"target":"WM-ECO-006 Commercial Contract","type":"neighbor","note":"The unfrozen parent agreement establishes obligations and legal terms. The reservation records capacity-seeking and booking lifecycle assertions and does not prove contract formation."},{"target":"Availability, inventory, capacity and allocation","type":"neighbor","note":"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."},{"target":"Appointment, calendar event and reserved service","type":"neighbor","note":"An appointment or calendar event represents scheduled interaction and the service owns execution. The reservation owns booking intent, terms and confirmation bindings."},{"target":"Offer, contract, order, ticket, entitlement, invoice and payment","type":"neighbor","note":"Each external commercial or fulfilment record has independent identity, state and authority; confirmation does not collapse or replace them."},{"target":"UN/EDIFACT, Schema.org, IATA, TM Forum, EU law, RFC, PROV, ODRL, DQV, ISO 4217 and OpenAPI","type":"neighbor","note":"Each representation has a distinct scope; every mapping is version-pinned, profile-qualified and loss-declaring."},{"target":"WM-ECO-006","type":"parent"}],"interaction":{"identity":{"applicability":"required","items":["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."]},"properties":{"applicability":"not-applicable","items":[]},"recognition":{"applicability":"optional","items":["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":{"applicability":"required","items":["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":{"applicability":"required","items":["Lost bookings.","Double booking.","Itinerary data leaks.","Missed cancellation deadlines."]},"interfaces":{"applicability":"required","items":["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":{"applicability":"required","items":["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":[{"title":"UN/EDIFACT Reservation request interactive message","url":"https://service.unece.org/trade/untdid/d01c/timd/resreq_c.htm","note":"United Nations Economic Commission for Europe"},{"title":"UN/EDIFACT Reservation response interactive message","url":"https://service.unece.org/trade/untdid/d98b/timd/resrsp_c.htm","note":"United Nations Economic Commission for Europe"},{"title":"UN/EDIFACT Firm booking message","url":"https://service.unece.org/trade/untdid/d09b/trmd/iftmbf_c.htm","note":"United Nations Economic Commission for Europe"},{"title":"Reservation","url":"https://schema.org/Reservation","note":"Schema.org Community Group"},{"title":"ReservationStatusType","url":"https://schema.org/ReservationStatusType","note":"Schema.org Community Group"},{"title":"ReservationPackage","url":"https://schema.org/ReservationPackage","note":"Schema.org Community Group"},{"title":"Fulfilling with Orders: ONE Order Factsheet","url":"https://www.iata.org/en/iata-repository/pressroom/fact-sheets/fact-sheet-one-order/","note":"International Air Transport Association"},{"title":"Appointment Management API TMF646","url":"https://www.tmforum.org/open-digital-architecture/open-apis/TMF646","note":"TM Forum"},{"title":"Open API Directory","url":"https://www.tmforum.org/open-digital-architecture/open-apis","note":"TM Forum"},{"title":"Directive EU 2015/2302 on package travel and linked travel arrangements","url":"https://eur-lex.europa.eu/eli/dir/2015/2302/oj","note":"European Union"},{"title":"Directive 2011/83/EU on consumer rights","url":"https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32011L0083","note":"European Union"},{"title":"Internet Calendaring and Scheduling Core Object Specification","url":"https://www.rfc-editor.org/rfc/rfc5545.html","note":"Internet Engineering Task Force"},{"title":"Date and Time on the Internet: Timestamps","url":"https://www.rfc-editor.org/rfc/rfc3339.html","note":"Internet Engineering Task Force"},{"title":"PROV-O: The PROV Ontology","url":"https://www.w3.org/TR/prov-o/","note":"World Wide Web Consortium"},{"title":"ODRL Information Model 2.2","url":"https://www.w3.org/TR/odrl-model/","note":"World Wide Web Consortium"},{"title":"Data on the Web Best Practices: Data Quality Vocabulary","url":"https://www.w3.org/TR/vocab-dqv/","note":"World Wide Web Consortium"},{"title":"Global Financial Data Standards: ISO 4217 Currency Codes","url":"https://www.six-group.com/en/products-services/financial-information/market-reference-data/data-standards.html","note":"SIX Financial Information"},{"title":"OpenAPI Specification 3.1.1","url":"https://spec.openapis.org/oas/v3.1.1.html","note":"OpenAPI Initiative"}],"openQuestions":["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."],"resources":{"spec":"/models/wm-eco-023-reservation-booking/spec.yaml","agents":"/models/wm-eco-023-reservation-booking/AGENTS.md","source":"https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-eco-023"},"provenance":{"origin":"world-models research","builtFrom":["models/wm-eco-023-reservation-booking/spec.yaml","ver-cy/world-models/card-supplements/wm-eco-023-reservation-booking.json"],"providers":["Codex"],"researchStatus":"reviewable-draft","generatedAt":"2026-09-06T15:12:50Z","builder":"tools/build_cards.py@1.0.0"},"completeness":{"sections":{"classifiers":"filled","whatItIs":"filled","purpose":"filled","distinguishingFeatures":"filled","structure":"filled","agentConduct":"filled","ethics":"filled","owners":"filled","relations":"filled","interaction.identity":"filled","interaction.properties":"not-applicable","interaction.recognition":"filled","interaction.capabilities":"filled","interaction.hazards":"filled","interaction.interfaces":"filled","interaction.context":"filled","sources":"filled"},"notes":{"interaction.properties":"Institutional or informational subject: no invented physical properties.","_supplement":"Sections authored in card supplement 1.0.0 by Claude (Opus 5.5) (2026-10-05, unreviewed). Written from the published specification and established practice in the field; no new sources were read. Unreviewed."},"score":1.0}}