Every booking platform speaks its own language.
A new website, marketplace or AI assistant has to integrate with every provider's booking system individually. There's no common way to just ask "what's bookable, and where?"
Provider ──▶ Nautic Open ──▶ Any platform
The whole model fits in four concepts.
- Provider
- Who offers it?
- Resource
- What is it?
- Offer
- What can I book?
- Schedule
- When can I book it?
A resource publishes offers or a schedule, but never both.
Offers
For concrete, individually priced bookable moments, like a course on a specific date, a single trip, or an event.
CWO 1
3 October
€295
2 places left
→ Book
Schedule
For recurring time slots, like a boat rental that runs the same slots every day, published compactly instead of as hundreds of offers.
| Date | 09:00–13:00 | 14:00–18:00 |
|---|---|---|
| 20 Sep | ✓ | ✓ |
| 21 Sep | – | ✓ |
| 22 Sep | – | – |
How a platform turns a feed into a booking.
- 01 Discover A platform reads the feed and finds what's on offer.
- 02 Understand Price, timing and capacity are all in the feed already.
- 03 Book The offer's url sends the user to the provider to complete it.
Nautic Open standardizes only the first two steps. Booking stays with the provider.
Nautic Open borrows its semantics from schema.org where useful. A Provider is close to
an Organization, a Resource close to a schema.org type. It doesn't adopt
schema.org's full vocabulary, only the structure this specific problem needs.
Read the spec
The full data model, field reference and validation rules live in the specification and the JSON Schema.
{
"id": "cwo-1-2026-10-03",
"price": 295,
"priceCurrency": "EUR",
"starts": "2026-10-03T09:00:00+02:00",
"ends": "2026-10-04T17:00:00+02:00",
"capacity": 6,
"remaining": 2,
"url": "https://example.com/boeken/cwo-1-2026-10-03"
}