Examples · valid Roadbook 1.2 files
Example Roadbooks
Nine .roadbook.json files, one per kind of trip, each small enough to read and focused on a few features rather than all of them. Every example validates against the current JSON Schema and the reference validator with zero errors and zero warnings.
Machine-readable manifest (index.json) Open the validator
-
Minimal
The smallest valid Roadbook: one traveler, one day, two items.
1 day(s) · days · items -
City break
Two days in Lisbon on foot and by tram: meal options, rain alternatives, a hotel and two things to book.
2 day(s) · options · alternatives · bookings · to_book · reminder · checklist -
Family vacation
A family of four in Normandy: surprise mode for the youngest, rooms, QR and Code 128 tickets, weather fallbacks.
4 day(s) · children · surpriseMode · rooms · tickets · qr · code128 -
Business trip
Two days in Berlin: flights with PNR and terminals, company-paid hotel and meals, meetings, a conference for one traveler.
2 day(s) · flight · transport · timezone · meeting · conference · payment -
Road trip
Tuscany by electric rental car: charging plan per day, parking with plate, wine tasting, hikes and viewpoints.
4 day(s) · vehicles · electric · rental · route · charging · parking -
Multi-city
Madrid, Lisbon, Porto by train: a night train crossing a timezone, Aztec tickets with berths, one stay per city.
5 day(s) · train · night train · endDate · timezone · endTimezone · aztec -
Agency package
A tour operator's Marrakech package: branded, with a driver and a guide to meet, prepaid transfers and vouchers.
4 day(s) · brand · people · guide · driver · host · transfer -
Flight and hotel
Paris to New York: two long-haul flights with boarding passes, a hotel, and free days still to plan.
4 day(s) · flight · long-haul · timezone · endDate · pdf417 · boarding pass -
Full-featured demo
Lille, Bruges, Amsterdam by electric car with a family: the reference demo exercising nearly every 1.2 field.
4 day(s) · everything · people · vehicles · tickets · options · alternatives
Manifest#
examples/index.json lists every example with its URL, explanatory page, feature tags and day count, so tools and agents can discover them without parsing HTML:
{
"formatVersion": "1.0",
"roadbookVersion": "1.2",
"examples": [
{ "id": "minimal", "name": "Minimal", "url": "/examples/minimal.roadbook.json",
"page": "/examples/minimal.html", "features": ["days", "items"], "days": 1 },
{ "id": "business-trip", "name": "Business trip", "url": "/examples/business-trip.roadbook.json",
"page": "/examples/business-trip.html",
"features": ["flight", "transport", "meeting", "payment", "pdf417"], "days": 2 }
]
}
Conventions used in the examples#
- Booking references, ticket payloads and phone numbers are obviously fictional (
EXAMPLE,+33 1 00 00 00 00); in a real file a ticketpayloadis the exact string encoded in the barcode. - Places are real; prices are indicative (
priceEstimated: true) unless a booking is described as confirmed. - Images are omitted so that no example depends on an external host; see the conventions for image references.
- Want your own example listed (another vertical, another language)? It must validate with zero errors — get in touch.