01Introduction
Nautic Open is a small, open, machine-readable format for publishing bookable nautical offerings (boats, courses, trips, events) so they can be discovered by search engines, marketplaces, AI agents and other platforms without a bespoke integration per provider.
A provider publishes a feed once. Any platform can read it.
Nautic Open is deliberately narrow in scope. It sits before the actual booking, describing what exists and where to book it. It does not standardize the booking itself.
Nautic Open is not:
- a booking engine
- a marketplace
- a payment standard
- a customer-data standard
- a reservation API
- an inventory management system
- an authentication protocol
- a standard for cancellation policies
- a required platform or central database
Nautic Open only says: this is what I currently offer, and here is where you can book it.
02Design principles
- Minimal. Cover only what's needed to discover and understand bookable offerings.
- Discovery, not transaction. The actual booking always happens on the provider's own system.
- Schema.org-inspired, not schema.org-bound. Concepts borrow schema.org semantics where useful, without importing its full vocabulary.
- Extensible. Resource types are an open set, not a closed enum, so new kinds of nautical offerings don't require a schema change.
- Versioned namespace. Every feed declares which version of Nautic Open it uses, so the format can evolve without breaking existing consumers.
03Data model overview
Provider
└── Resource
├── Offer
└── Schedule
└── Option
Provider ──▶ Resource ──▶ Offers | Schedule
A Provider publishes one or more Resources. Each Resource publishes its bookable availability as either a list of Offers or a Schedule, never both.
04Provider
The organization publishing the feed. Schema.org equivalent: Organization.
| Field | Type | Required | Description |
|---|---|---|---|
id | string | yes | Stable identifier for the provider. |
type | string | yes | Always "Organization". |
name | string | yes | Display name. |
url | string (URI) | no | Informational URL, e.g. the provider's website. |
email | string | no | Contact address. |
description | string | no | Short free-text description. |
05Resource
Something the provider offers: a Boat, Course,
BoatTrip, Event, Service, or another type not yet
listed here.
| Field | Type | Required | Description |
|---|---|---|---|
id | string | yes | Stable identifier, unique within the feed. |
type | string | yes | Open vocabulary, see below. |
name | string | yes | Display name. |
url | string (URI) | yes | Informational URL: tells you more about this resource. |
description | string | no | Short free-text description. |
offers | array of Offer | conditional | See rule below. |
schedule | Schedule | conditional | See rule below. |
type is an open vocabulary. This schema does not restrict it
to an enum, so providers can describe offerings this specification hasn't anticipated.
Well-known values, inspired by schema.org, include:
BoatCourseBoatTripEventService
A resource MUST have exactly one of offers or
schedule, never both and never neither. Use offers for a
small number of concrete, individually priced bookable instances. Use schedule
when the same resource repeats the same time slots across many dates: publishing an Offer
per slot per day would make the feed unnecessarily large.
Resource.url is informational only (tell me more about this
resource). It is distinct from Offer.url, which is transactional.
06Offer
A concrete, bookable instance of a resource: a specific date, price and capacity.
| Field | Type | Required | Description |
|---|---|---|---|
id | string | yes | Stable identifier, unique within the resource. |
name | string | no | Display name. |
price | number | yes | Numeric price. |
priceCurrency | string | yes | ISO 4217 currency code, e.g. EUR. |
starts | string (date-time) | yes | Absolute start instant. |
ends | string (date-time) | yes | Absolute end instant. |
capacity | integer | no | Total capacity, if applicable. |
remaining | integer | no | Remaining capacity, if applicable. |
url | string (URI) | yes | Transactional URL: books this specific offer. |
Offer.url is transactional (book this
specific offer), unlike Resource.url, which is only informational. Don't
confuse the two.
There is no separate availability or "sold out" flag. If an offer is no longer bookable, it is simply not published. A feed that omits a previously published offer means that offer is gone.
07Schedule
A compact way to publish recurring availability, made of reusable Options and an availability map.
| Field | Type | Required | Description |
|---|---|---|---|
options | array of Option | yes | The reusable time-slot templates for this resource. |
availability | object | yes | Maps a date to the option ids available that day. |
availability keys are ISO 8601 dates (YYYY-MM-DD). Each value is
an array of option ids, possibly empty, meaning nothing is available that day.
"availability": {
"2026-09-20": ["morning", "afternoon"],
"2026-09-21": ["afternoon"],
"2026-09-22": []
}
Normative rule (not enforced by the
JSON Schema): every option id used in availability MUST correspond to
an id present in that same schedule's options array. Consumers should treat a
reference to a missing option id as an error in the feed.
08Option
A reusable time-slot template, e.g. "the morning slot."
| Field | Type | Required | Description |
|---|---|---|---|
id | string | yes | Stable identifier, unique within the resource's schedule. |
name | string | no | Display name, e.g. "Ochtend". |
starts | string (time) | yes | Time of day this option starts. |
ends | string (time) | yes | Time of day this option ends. |
price | number | yes | Numeric price. |
priceCurrency | string | yes | ISO 4217 currency code. |
Option.starts/Option.ends are times of day
(HH:MM), not date-times. This is the key difference from
Offer.starts/Offer.ends, which are absolute instants: an Option is
a template reused across many dates, an Offer is a single concrete occurrence.
09Full feed shape
A feed is a single JSON document:
| Field | Type | Required | Description |
|---|---|---|---|
schema | string | yes | Always "https://nauticopen.org/schema/0.1" for this version. |
provider | Provider | yes | The publisher of this feed. |
resources | array of Resource | yes | One or more resources. |
10Versioning
The namespace and schema URL are versioned by path segment: /0.1/, and in
future /0.2/, etc. A feed declares its version via the schema
field. Nautic Open v0.1 is a draft and makes no backward-compatibility guarantees yet;
breaking changes will bump the version segment.
11Examples
Full example feeds, covering both ways of publishing availability, are on the examples page.
{
"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"
}
12Conformance and validation
A conforming feed:
- Validates against feed.schema.json (JSON Schema draft 2020-12).
- Satisfies the normative rules this schema cannot express: every
availabilityoption id exists in that schedule'soptions, andidvalues are unique within their scope.
Check a feed instantly with the online validator, or validate it against the schema with Python:
pip install jsonschema
python3 -c "
import json, jsonschema
schema = json.load(open('feed.schema.json'))
data = json.load(open('your-feed.json'))
jsonschema.Draft202012Validator(schema, format_checker=jsonschema.FormatChecker()).validate(data)
print('OK')
"
13License
Nautic Open is licensed under CC BY-SA 4.0. Anyone, including commercial platforms and services, may implement and build on this specification freely. Published derivatives of the specification itself must be shared under the same license.