← Catalogue
World Models · legacy example

Tourism & Hospitality

This meta-model describes the world of travel for leisure and its service industry: destinations and attractions, accommodation offers and stays, and the catalogue of experiences visitors consume. It is its own model because tourism joins place (destinations), commerce (offers, grades) and personal movement (stays) into one lifecycle, from listing an offer through booking, arrival and departure, that neither a place model nor a generic commerce model expresses on its own.

AI YAMLAGENTS.mdSource
IDworld.d7-tourism-and-hospitality
Version history0.2.0-legacy
CategoryReference example
IndustryCross-industry
Domaincivilization
Tagstourism, hospitality
Data structure

Bundles and layers

Bundle

destination

Places in their role as visitor destinations

Layers

destinationProfile`: destinations, attractions and their visitor-facing identity · `seasonality`: seasons, capacity and visitor flows over time

Bundle

stay

Lodging supply and the fact of staying

Layers

accommodationOffer`: lodging offers, room types, availability · `stayRecord`: bookings, arrivals and departures as facts of the world

Bundle

experience

What visitors do and how well it is done

Layers

experienceCatalogue`: tours, activities and packaged experiences · `serviceQuality`: classifications, star grades and quality signals

Findings

Catalogue-native findings must describe the information grouped by each layer. This legacy version does not declare them separately.

Questions & artifacts

Questions, artifact requirements and serial naming rules are required by Vercy vNext; they remain unassigned in this reference version.

Service layers

How this specification operates

Dimension & namespace

  • REFERENCE `world.territoryAndPlace` (P): destinations are roles over territories and places; geography stays sovereign in the place model
  • REFERENCE `world.buildingAndFacility` (U): accommodation resolves to physical structures (accommodation_ref)
  • REFERENCE `world.organization` (O1): providers, operators and awarding bodies are organizations
  • REFERENCE `world.person` (H1): guests are natural persons; stay records link to them only under consent
  • REFERENCE `world.sportRecreation` (D5): sporting events and recreational activities surface as visitor experiences
  • imports: UNWTO (ALIGN): visitor, trip and stay definitions from international tourism statistics recommendations
  • imports: schema.org (ALIGN): TouristDestination, LodgingBusiness and TouristAttraction typing for public catalogues

Canon, patches & standards

  • REFERENCE `world.territoryAndPlace` (P): destinations are roles over territories and places; geography stays sovereign in the place model
  • REFERENCE `world.buildingAndFacility` (U): accommodation resolves to physical structures (accommodation_ref)
  • REFERENCE `world.organization` (O1): providers, operators and awarding bodies are organizations
  • REFERENCE `world.person` (H1): guests are natural persons; stay records link to them only under consent
  • REFERENCE `world.sportRecreation` (D5): sporting events and recreational activities surface as visitor experiences
  • imports: UNWTO (ALIGN): visitor, trip and stay definitions from international tourism statistics recommendations
  • imports: schema.org (ALIGN): TouristDestination, LodgingBusiness and TouristAttraction typing for public catalogues

Artifact formats & serial data

Format-independent core. Concrete artifact formats and naming prefixes are not declared in this legacy version.

Policies & accepted processes

  • `bookingDataExchange`: provider-to-provider exchange of minimal booking data, guest identity only under the guest's S1 consent
  • `destinationStatisticsFeed`: aggregated visitor flows delivered to the statistics office and destination steward
  • `catalogueSyndication`: public redistribution of offer and experience catalogues to travel channels

Read / add / edit / delete

CRUD procedures and interface bindings are not declared in this legacy version.

Ownership, roles & access

Providers own their offers, stays and service records; the territory steward, as a sub-agent for the destination, owns destination profiles and seasonality. Guest-related data is accessible only under the guest's own grant, with all access issued through the catalogue's S1/S2 ownership and access models and audited via S4.

Existing assembly

Objects, relationships, events and projections

Objects

  • `destination`: a place in its visitor-facing role; key attributes: name, territory reference, profile, seasonality pattern
  • `attraction`: a visitable point of interest; key attributes: name, type, destination, access conditions
  • `accommodationOffer`: a lodging offer by a provider; key attributes: provider reference, facility reference, room types, availability window
  • `stay`: the fact of a guest staying; key attributes: offer reference, guest reference, arrival, departure, party size
  • `experienceOffer`: a bookable activity or tour; key attributes: name, operator reference, destination, schedule, capacity
  • `itinerary`: a planned sequence of stays and experiences; key attributes: owner reference, legs, dates
  • `serviceGrade`: an awarded quality classification; key attributes: scheme, grade, awarding body reference, validity
  • `visitorFlow`: an aggregate measure of visits; key attributes: destination, period, count, method

Relationships

  • `destination` -> features -> `attraction` (1..n): a destination's attractions define its profile
  • `accommodationOffer` -> locatedIn -> `destination` (n..1): every offer belongs to a destination
  • `accommodationOffer` -> housedIn -> `accommodation` (n..1): the physical lodging resolves to a structure in the built-environment model (U)
  • `stay` -> bookedAt -> `accommodationOffer` (n..1): a stay realizes an offer
  • `stay` -> madeBy -> `person` (n..1): the guest resolves to a natural person in H1 under that person's grant
  • `itinerary` -> includes -> `experienceOffer` (n..m): itineraries assemble experiences and stays
  • `serviceGrade` -> awardedTo -> `accommodationOffer` (n..1): grades attach to specific offers or properties
  • `visitorFlow` -> aggregates -> `stay` (1..n): flows are computed from stays with no personal data retained

Events

  • `attractionListed`: an attraction entered a destination's public profile
  • `offerPublished`: a provider published or updated an accommodation or experience offer
  • `stayBooked`: a booking was made against an offer
  • `guestArrived`: a stay began
  • `guestDeparted`: a stay ended
  • `experienceDelivered`: a booked experience took place
  • `gradeAwarded`: a quality classification was granted or renewed
  • `seasonOpened`: a destination's season began, changing capacity and availability

Projections

  • `travellerCatalogue`: offers, experiences and grades for trip planning; omits operational data and all guest records
  • `destinationDashboard`: seasonality and aggregate flows for destination management; contains no individual stays
  • `qualityRegister`: current grades and their awarding bodies; omits pricing and availability