Published

Route / Itinerary

vr.wm-flw-010 · wm-flw-010-route-itinerary

Represent one governed reusable or computed route, or one candidate or selected itinerary, with ordered structure, constraints, plan clocks, alternatives and successor lineage without becoming its journey, network, schedule, resource or routing engine.

World Models Physical world and living systems PHY.FLW.MOB

Bundle → Layer → Finding → Questions Classifiers What it is Why it exists Distinguishing features What robots and AI may and may not do Moral aspects Owners Links to other meta-models Identity and identifiers Direct properties Recognition Capabilities and actions Hazards and failure modes Standards and interfaces Context of use Sources

Bundle → Layer → Finding → Questions Filled

6 bundles · 12 layers · 24 findings · 72 questions

Identity, kind and boundary Groups the governed Route / Itinerary concern for identity, kind and boundary.

Identity, version and successor

Groups Route / Itinerary context for identity, version and successor without importing neighboring master lifecycles.

Route or itinerary identity, namespace, version and mandatory kind

Records route or itinerary identity, namespace, version and mandatory kind as typed Route / Itinerary context while journey execution, networks, places, schedules, services, assets, bookings and routing engines remain external masters.

Which route or itinerary identity, kind, revision, ordered component, time basis and source establish route or itinerary identity, namespace, version and mandatory kind? identity
Who requested, computed, selected, owns, reviewed, corrected or may access route or itinerary identity, namespace, version and mandatory kind, and under which authority or policy? ownership
Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify route or itinerary identity, namespace, version and mandatory kind? validation

Revision, predecessor, successor, effective period and status

Records revision, predecessor, successor, effective period and status as typed Route / Itinerary context while journey execution, networks, places, schedules, services, assets, bookings and routing engines remain external masters.

Which route or itinerary identity, kind, revision, ordered component, time basis and source establish revision, predecessor, successor, effective period and status? lifecycle
Who requested, computed, selected, owns, reviewed, corrected or may access revision, predecessor, successor, effective period and status, and under which authority or policy? authority
Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify revision, predecessor, successor, effective period and status? security

Scope, owner and plan boundary

Groups Route / Itinerary context for scope, owner and plan boundary without importing neighboring master lifecycles.

Reusable route, computed route, itinerary and combined-plan boundary

Records reusable route, computed route, itinerary and combined-plan boundary as typed Route / Itinerary context while journey execution, networks, places, schedules, services, assets, bookings and routing engines remain external masters.

Which route or itinerary identity, kind, revision, ordered component, time basis and source establish reusable route, computed route, itinerary and combined-plan boundary? classification
Who requested, computed, selected, owns, reviewed, corrected or may access reusable route, computed route, itinerary and combined-plan boundary, and under which authority or policy? constraint
Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify reusable route, computed route, itinerary and combined-plan boundary? privacy

Planner, operator, traveller, vehicle, cargo and authority roles

Records planner, operator, traveller, vehicle, cargo and authority roles as typed Route / Itinerary context while journey execution, networks, places, schedules, services, assets, bookings and routing engines remain external masters.

Which route or itinerary identity, kind, revision, ordered component, time basis and source establish planner, operator, traveller, vehicle, cargo and authority roles? ownership
Who requested, computed, selected, owns, reviewed, corrected or may access planner, operator, traveller, vehicle, cargo and authority roles, and under which authority or policy? process
Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify planner, operator, traveller, vehicle, cargo and authority roles? retention

Network path and ordered structure Groups the governed Route / Itinerary concern for network path and ordered structure.

Endpoints, waypoints and network path

Groups Route / Itinerary context for endpoints, waypoints and network path without importing neighboring master lifecycles.

Origin, destination, via waypoint, node, link and zone reference

Records origin, destination, via waypoint, node, link and zone reference as typed Route / Itinerary context while journey execution, networks, places, schedules, services, assets, bookings and routing engines remain external masters.

Which route or itinerary identity, kind, revision, ordered component, time basis and source establish origin, destination, via waypoint, node, link and zone reference? spatial
Who requested, computed, selected, owns, reviewed, corrected or may access origin, destination, via waypoint, node, link and zone reference, and under which authority or policy? event
Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify origin, destination, via waypoint, node, link and zone reference? access

Directed segment sequence, topology, geometry and CRS

Records directed segment sequence, topology, geometry and crs as typed Route / Itinerary context while journey execution, networks, places, schedules, services, assets, bookings and routing engines remain external masters.

Which route or itinerary identity, kind, revision, ordered component, time basis and source establish directed segment sequence, topology, geometry and crs? composition
Who requested, computed, selected, owns, reviewed, corrected or may access directed segment sequence, topology, geometry and crs, and under which authority or policy? measurement
Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify directed segment sequence, topology, geometry and crs? exception

Legs, stages, visits and transfers

Groups Route / Itinerary context for legs, stages, visits and transfers without importing neighboring master lifecycles.

Itinerary leg, stage, call, visit, activity and order

Records itinerary leg, stage, call, visit, activity and order as typed Route / Itinerary context while journey execution, networks, places, schedules, services, assets, bookings and routing engines remain external masters.

Which route or itinerary identity, kind, revision, ordered component, time basis and source establish itinerary leg, stage, call, visit, activity and order? composition
Who requested, computed, selected, owns, reviewed, corrected or may access itinerary leg, stage, call, visit, activity and order, and under which authority or policy? evidence
Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify itinerary leg, stage, call, visit, activity and order? interoperability

Access, egress, transfer, handover, connection and wait

Records access, egress, transfer, handover, connection and wait as typed Route / Itinerary context while journey execution, networks, places, schedules, services, assets, bookings and routing engines remain external masters.

Which route or itinerary identity, kind, revision, ordered component, time basis and source establish access, egress, transfer, handover, connection and wait? relationship
Who requested, computed, selected, owns, reviewed, corrected or may access access, egress, transfer, handover, connection and wait, and under which authority or policy? quality
Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify access, egress, transfer, handover, connection and wait? decision

Constraints, criteria and selection Groups the governed Route / Itinerary concern for constraints, criteria and selection.

Request and feasibility constraints

Groups Route / Itinerary context for request and feasibility constraints without importing neighboring master lifecycles.

Mode, accessibility, vehicle, cargo, height, load and safety constraint

Records mode, accessibility, vehicle, cargo, height, load and safety constraint as typed Route / Itinerary context while journey execution, networks, places, schedules, services, assets, bookings and routing engines remain external masters.

Which route or itinerary identity, kind, revision, ordered component, time basis and source establish mode, accessibility, vehicle, cargo, height, load and safety constraint? constraint
Who requested, computed, selected, owns, reviewed, corrected or may access mode, accessibility, vehicle, cargo, height, load and safety constraint, and under which authority or policy? validation
Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify mode, accessibility, vehicle, cargo, height, load and safety constraint? identity

Avoid, prefer, must-pass, time-window, permission and policy constraint

Records avoid, prefer, must-pass, time-window, permission and policy constraint as typed Route / Itinerary context while journey execution, networks, places, schedules, services, assets, bookings and routing engines remain external masters.

Which route or itinerary identity, kind, revision, ordered component, time basis and source establish avoid, prefer, must-pass, time-window, permission and policy constraint? constraint
Who requested, computed, selected, owns, reviewed, corrected or may access avoid, prefer, must-pass, time-window, permission and policy constraint, and under which authority or policy? security
Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify avoid, prefer, must-pass, time-window, permission and policy constraint? classification

Objective, alternatives and choice

Groups Route / Itinerary context for objective, alternatives and choice without importing neighboring master lifecycles.

Distance, time, cost, emissions, energy, risk and comfort objective

Records distance, time, cost, emissions, energy, risk and comfort objective as typed Route / Itinerary context while journey execution, networks, places, schedules, services, assets, bookings and routing engines remain external masters.

Which route or itinerary identity, kind, revision, ordered component, time basis and source establish distance, time, cost, emissions, energy, risk and comfort objective? decision
Who requested, computed, selected, owns, reviewed, corrected or may access distance, time, cost, emissions, energy, risk and comfort objective, and under which authority or policy? privacy
Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify distance, time, cost, emissions, energy, risk and comfort objective? composition

Candidate alternative, ranking, selection, rejection and rationale

Records candidate alternative, ranking, selection, rejection and rationale as typed Route / Itinerary context while journey execution, networks, places, schedules, services, assets, bookings and routing engines remain external masters.

Which route or itinerary identity, kind, revision, ordered component, time basis and source establish candidate alternative, ranking, selection, rejection and rationale? decision
Who requested, computed, selected, owns, reviewed, corrected or may access candidate alternative, ranking, selection, rejection and rationale, and under which authority or policy? retention
Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify candidate alternative, ranking, selection, rejection and rationale? relationship

Temporal, service and resource plan Groups the governed Route / Itinerary concern for temporal, service and resource plan.

Validity, planned time and continuity

Groups Route / Itinerary context for validity, planned time and continuity without importing neighboring master lifecycles.

Operating day, validity, departure, arrival, duration and time zone

Records operating day, validity, departure, arrival, duration and time zone as typed Route / Itinerary context while journey execution, networks, places, schedules, services, assets, bookings and routing engines remain external masters.

Which route or itinerary identity, kind, revision, ordered component, time basis and source establish operating day, validity, departure, arrival, duration and time zone? temporal
Who requested, computed, selected, owns, reviewed, corrected or may access operating day, validity, departure, arrival, duration and time zone, and under which authority or policy? access
Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify operating day, validity, departure, arrival, duration and time zone? state

Requested, planned, estimated, predicted, committed and slack time

Records requested, planned, estimated, predicted, committed and slack time as typed Route / Itinerary context while journey execution, networks, places, schedules, services, assets, bookings and routing engines remain external masters.

Which route or itinerary identity, kind, revision, ordered component, time basis and source establish requested, planned, estimated, predicted, committed and slack time? classification
Who requested, computed, selected, owns, reviewed, corrected or may access requested, planned, estimated, predicted, committed and slack time, and under which authority or policy? exception
Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify requested, planned, estimated, predicted, committed and slack time? lifecycle

Mode, service, schedule and resource bindings

Groups Route / Itinerary context for mode, service, schedule and resource bindings without importing neighboring master lifecycles.

Mode, line, route pattern, service trip and schedule reference

Records mode, line, route pattern, service trip and schedule reference as typed Route / Itinerary context while journey execution, networks, places, schedules, services, assets, bookings and routing engines remain external masters.

Which route or itinerary identity, kind, revision, ordered component, time basis and source establish mode, line, route pattern, service trip and schedule reference? relationship
Who requested, computed, selected, owns, reviewed, corrected or may access mode, line, route pattern, service trip and schedule reference, and under which authority or policy? interoperability
Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify mode, line, route pattern, service trip and schedule reference? temporal

Vehicle, seat, booking, ticket, fare, activity and facility reference

Records vehicle, seat, booking, ticket, fare, activity and facility reference as typed Route / Itinerary context while journey execution, networks, places, schedules, services, assets, bookings and routing engines remain external masters.

Which route or itinerary identity, kind, revision, ordered component, time basis and source establish vehicle, seat, booking, ticket, fare, activity and facility reference? relationship
Who requested, computed, selected, owns, reviewed, corrected or may access vehicle, seat, booking, ticket, fare, activity and facility reference, and under which authority or policy? decision
Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify vehicle, seat, booking, ticket, fare, activity and facility reference? spatial

Lifecycle, change and evaluation Groups the governed Route / Itinerary concern for lifecycle, change and evaluation.

Plan state, disruption and replanning

Groups Route / Itinerary context for plan state, disruption and replanning without importing neighboring master lifecycles.

Draft, requested, computing, candidate, selected, confirmed and cancelled state

Records draft, requested, computing, candidate, selected, confirmed and cancelled state as typed Route / Itinerary context while journey execution, networks, places, schedules, services, assets, bookings and routing engines remain external masters.

Which route or itinerary identity, kind, revision, ordered component, time basis and source establish draft, requested, computing, candidate, selected, confirmed and cancelled state? lifecycle
Who requested, computed, selected, owns, reviewed, corrected or may access draft, requested, computing, candidate, selected, confirmed and cancelled state, and under which authority or policy? identity
Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify draft, requested, computing, candidate, selected, confirmed and cancelled state? provenance

Disruption, invalidity, reroute, difference, successor and actual divergence

Records disruption, invalidity, reroute, difference, successor and actual divergence as typed Route / Itinerary context while journey execution, networks, places, schedules, services, assets, bookings and routing engines remain external masters.

Which route or itinerary identity, kind, revision, ordered component, time basis and source establish disruption, invalidity, reroute, difference, successor and actual divergence? exception
Who requested, computed, selected, owns, reviewed, corrected or may access disruption, invalidity, reroute, difference, successor and actual divergence, and under which authority or policy? classification
Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify disruption, invalidity, reroute, difference, successor and actual divergence? ownership

Measures, uncertainty and quality

Groups Route / Itinerary context for measures, uncertainty and quality without importing neighboring master lifecycles.

Distance, duration, cost, toll, energy, emissions and risk estimate

Records distance, duration, cost, toll, energy, emissions and risk estimate as typed Route / Itinerary context while journey execution, networks, places, schedules, services, assets, bookings and routing engines remain external masters.

Which route or itinerary identity, kind, revision, ordered component, time basis and source establish distance, duration, cost, toll, energy, emissions and risk estimate? measurement
Who requested, computed, selected, owns, reviewed, corrected or may access distance, duration, cost, toll, energy, emissions and risk estimate, and under which authority or policy? composition
Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify distance, duration, cost, toll, energy, emissions and risk estimate? authority

Coverage, freshness, precision, confidence, uncertainty and validation

Records coverage, freshness, precision, confidence, uncertainty and validation as typed Route / Itinerary context while journey execution, networks, places, schedules, services, assets, bookings and routing engines remain external masters.

Which route or itinerary identity, kind, revision, ordered component, time basis and source establish coverage, freshness, precision, confidence, uncertainty and validation? quality
Who requested, computed, selected, owns, reviewed, corrected or may access coverage, freshness, precision, confidence, uncertainty and validation, and under which authority or policy? relationship
Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify coverage, freshness, precision, confidence, uncertainty and validation? constraint

Provenance, access and interoperability Groups the governed Route / Itinerary concern for provenance, access and interoperability.

Source, engine, algorithm and lineage

Groups Route / Itinerary context for source, engine, algorithm and lineage without importing neighboring master lifecycles.

Network dataset version, engine, algorithm, parameter and job reference

Records network dataset version, engine, algorithm, parameter and job reference as typed Route / Itinerary context while journey execution, networks, places, schedules, services, assets, bookings and routing engines remain external masters.

Which route or itinerary identity, kind, revision, ordered component, time basis and source establish network dataset version, engine, algorithm, parameter and job reference? provenance
Who requested, computed, selected, owns, reviewed, corrected or may access network dataset version, engine, algorithm, parameter and job reference, and under which authority or policy? state
Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify network dataset version, engine, algorithm, parameter and job reference? process

Assertion, derivation, correction, invalidation, review and evidence

Records assertion, derivation, correction, invalidation, review and evidence as typed Route / Itinerary context while journey execution, networks, places, schedules, services, assets, bookings and routing engines remain external masters.

Which route or itinerary identity, kind, revision, ordered component, time basis and source establish assertion, derivation, correction, invalidation, review and evidence? evidence
Who requested, computed, selected, owns, reviewed, corrected or may access assertion, derivation, correction, invalidation, review and evidence, and under which authority or policy? lifecycle
Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify assertion, derivation, correction, invalidation, review and evidence? event

Access, retention and crosswalks

Groups Route / Itinerary context for access, retention and crosswalks without importing neighboring master lifecycles.

Location sensitivity, purpose, consent, access, retention and license

Records location sensitivity, purpose, consent, access, retention and license as typed Route / Itinerary context while journey execution, networks, places, schedules, services, assets, bookings and routing engines remain external masters.

Which route or itinerary identity, kind, revision, ordered component, time basis and source establish location sensitivity, purpose, consent, access, retention and license? privacy
Who requested, computed, selected, owns, reviewed, corrected or may access location sensitivity, purpose, consent, access, retention and license, and under which authority or policy? temporal
Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify location sensitivity, purpose, consent, access, retention and license? measurement

Transmodel, NeTEx, GTFS, OGC, GeoJSON, Schema.org, time and provenance crosswalk

Records transmodel, netex, gtfs, ogc, geojson, schema.org, time and provenance crosswalk as typed Route / Itinerary context while journey execution, networks, places, schedules, services, assets, bookings and routing engines remain external masters.

Which route or itinerary identity, kind, revision, ordered component, time basis and source establish transmodel, netex, gtfs, ogc, geojson, schema.org, time and provenance crosswalk? interoperability
Who requested, computed, selected, owns, reviewed, corrected or may access transmodel, netex, gtfs, ogc, geojson, schema.org, time and provenance crosswalk, and under which authority or policy? spatial
Which constraints, alternatives, estimates, exceptions, evidence, uncertainty and lineage qualify transmodel, netex, gtfs, ogc, geojson, schema.org, time and provenance crosswalk? evidence

Classifiers Filled

Family: World Models
Category: Physical world and living systems
Entry kind: aggregate
Navigation path: NAV.PHY.FLW.MOB
Domain: PHY.FLW.MOB
Industry: Cross-industry
Tags: routeitineraryphy.flw.mob

What it is Filled

Owns mandatory route-or-itinerary kind; object and revision identity; endpoints, ordered waypoints, segments, legs, visits and transfers; route topology and geometry references; itinerary composition; requested and applied constraints; objectives, candidates, ranking and selection rationale; planned clocks and validity; service, schedule, mode and resource references; plan lifecycle, validation, replanning and actual-journey divergence references; estimates, quality, provenance, access, retention and loss-aware projections. Journey execution, networks, places, schedules, services, people, vehicles, bookings, tickets, fares, activities, shipments, incidents, weather, routing engines, source datasets and evidence masters remain external.

In scope

Route or itinerary identity, revision, mandatory kind, boundary, ownership and successor lineage
Ordered route path or itinerary composition, constraints, objectives, alternatives, selected plan, clocks and external bindings
Validation, disruption, replanning, estimates, provenance, privacy, access, retention and interoperability

Out of scope

Owning journey, network, place, schedule, service, person, vehicle, booking, ticket, fare, activity, shipment, incident, weather, routing-engine, dataset, evidence or document lifecycles
Equating route with itinerary, route or itinerary with journey, line with route, segment with leg, waypoint with visit, plan with actual movement or estimate with commitment
Performing routing computation, autonomous consequential rerouting, safety or legal permission decisions, protected location disclosure or irreversible deletion

Why it exists Filled

Distinguishing features Filled

A route is a directed path through a network; an itinerary is a plan of legs, visits and transfers.
Neither proves movement; actual movement belongs to the journey model.
Candidates, ranking and selection rationale are kept, not just the chosen option.
Routing engines compute routes; this model records them.

What robots and AI may and may not do Filled

Must not

Present a route as legally permitted or safe without evidence.
Book or ticket on behalf of a traveller without consent.
Reroute consequentially without authority.
Disclose protected locations.

Only with a human decision

Selecting routes for hazardous loads or vulnerable travellers.
Rerouting during safety incidents.

May

Register candidate routes and itineraries with constraints.
Validate continuity and connection times.
Present alternatives with rationale.
Supersede a plan on disruption.

Moral aspects Filled

Routes for vulnerable travellers must respect accessibility needs.
Itineraries reveal plans and locations.
Routing choices can push traffic into residential areas.

Who is affected

Travellers
Residents along routes
Operators
Emergency services

Owners Filled

Steward

Declare the Dimension owner, route and itinerary stewards, routing authorities and accountable decision roles.

Roles

Dimension owner: Own namespace, mastership, delegation, access, retention and federation rules.
Route steward: Own reusable or computed path boundary, topology, geometry references and revision lineage.
Itinerary steward: Own ordered planning result, alternatives, selection and successor history.
Network or schedule steward: Own referenced network, place, service and schedule masters.
Routing provider: Own engine, algorithm, dataset, computation job and result assertions it issues.
Traveller, operator or asset authority: Supply applicable preferences, constraints, permissions and accountable decisions.
Reviewer or auditor: Review feasibility, evidence, conflicts, corrections and protected use without rewriting originals.
Disclosure authority: Approve recipient, purpose, location exposure, redaction and publication timing.

Links to other meta-models Filled

references

WM-FLW-009 Journey / Trip - Bind a selected plan to intended or actual movement while preserving execution observations and outcomes in Journey.
Network, Place, Stop, Service, Schedule, Person, Vehicle, Booking, Ticket, Activity, Shipment, Incident, Engine, Dataset and Evidence models - Resolve external masters without duplicating their identity, authority or lifecycle.

aligned

Transmodel v6.2 and NeTEx - Project European public-transport route and journey-pattern views with explicit type and version mappings.
GTFS Schedule - Project routes, trips, stop-time sequences, shapes, calendars and transfers without adopting GTFS terminology as universal.
OGC API Routes, Route Exchange Model, GeoSPARQL and GeoJSON - Project engine-independent route requests and geometry while pinning developing OGC drafts and declared conformance.
ISO 19133, ISO 19141 and OGC Moving Features - Align navigation and planned-route concepts while keeping actual moving-feature trajectory external.
EU multimodal travel information and Schema.org Trip - Project regional machine-readable itinerary and lightweight web-discovery views with explicit limitations.
OWL-Time, RFC 3339, PROV-O, DQV and ODRL - Project temporal, provenance, quality and access semantics with exact pins and semantic-loss declarations.

neighbor

WM-FLW-009 Journey / Trip - Journey owns the planned or actual movement episode, observations and outcomes. Route / Itinerary owns reusable or computed path and planning-result structure; a journey references a selected plan and may diverge from it.
Network, Place and Stop - Route / Itinerary orders typed references and may carry snapshot geometry. Network topology, place identity, facilities, restrictions and authoritative geometry remain externally mastered.
Line, Journey Pattern, Service and Schedule - A line groups service presentation, a route describes a path, a journey pattern orders scheduled points, and a scheduled trip instantiates service. Their identities and lifecycles remain distinct.
Routing Engine, Algorithm and Computation Job - The model records requests, parameters, versions and results. Execution, resource use, optimization implementation and job control remain owned by external computation masters.
Booking, Ticket, Fare, Activity and Resource - An itinerary may reference entitlements, offers, reservations, activities, vehicles and facilities, but does not own or imply their availability, validity or lifecycle.
Trajectory and Moving Feature - Route / Itinerary describes intended path or plan. Actual temporal geometry and movement observations remain journey or moving-feature evidence and are compared rather than merged.

parent

WM-FLW-009

What else AI and robots need to interact with it Filled

Sources Filled

Transmodel v6.2 Data Dictionary - CEN Transmodel
Transmodel at a glance - CEN Transmodel
NeTEx - CEN NeTEx
GTFS Schedule Reference - MobilityData
OGC API - Routes overview - Open Geospatial Consortium
OGC Routing Pilot Engineering Report - Open Geospatial Consortium
WPS Routing API Engineering Report - Open Geospatial Consortium
OGC Standards Roadmap - Open Geospatial Consortium
GeoSPARQL - Open Geospatial Consortium
RFC 7946: The GeoJSON Format - Internet Engineering Task Force
ISO 19133 Geographic information - Location-based services - Tracking and navigation - International Organization for Standardization
ISO 19141 Geographic information - Schema for moving features - International Organization for Standardization
Commission Delegated Regulation (EU) 2024/490 - European Union
Multimodal travel information services - European Commission
Trip - Schema.org Community Group
Time Ontology in OWL - World Wide Web Consortium
RFC 3339: Date and Time on the Internet - Internet Engineering Task Force
PROV-O: The PROV Ontology - World Wide Web Consortium
Data Quality Vocabulary - World Wide Web Consortium
ODRL Information Model 2.2 - World Wide Web Consortium
OGC Moving Features standards - Open Geospatial Consortium

Open questions

Decide whether Route and Itinerary should split into separate registry models after paired implementation and query-pattern review.
Create independently validated pedestrian, bicycle, road, rail, maritime, aviation, indoor, multimodal, freight, evacuation and autonomous-route profiles.
Benchmark path continuity, transfer feasibility, map matching, traffic prediction, routing algorithms, multi-objective ranking, replanning and actual-plan divergence.
Pin exact external releases and licensing conditions and obtain independent transport, geospatial, accessibility, safety, privacy, optimization, data and records review before promotion beyond reviewable-draft assurance.
Mode, region, safety, accessibility, border, traffic-law, passenger-rights, privacy, licensing and retention profiles require exact current rules and competent review.
Network, place, journey, service, schedule, person, vehicle, booking, ticket, fare, activity, shipment, incident, weather, routing-engine, dataset and evidence lifecycles remain in neighboring masters.
Certified field crosswalks, routing algorithms, map matching, traffic prediction, feasibility solvers and legal proof requirements remain future work.
The aggregate family may require a future breaking split into separate Route and Itinerary specifications after wider implementation evidence.

Machine files

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

Provenance

world-models research · reviewable-draft

Built from: models/wm-flw-010-route-itinerary/spec.yaml, ver-cy/world-models/card-supplements/wm-flw-010-route-itinerary.json