Content (In Member Review)
Adds extra content fields to OCTO Core object schemas on select endpoints to provide detailed descriptive information about supplier, products, options, units, booking, etc.
Last updated
Adds extra content fields to OCTO Core object schemas on select endpoints to provide detailed descriptive information about supplier, products, options, units, booking, etc.
Last updated
This new proposed capability is currently undergoing Specification Committee and Member reviews.
We'd love to hear your feedback on this draft! Use #content-capability-development channel on OCTO Slack, or comment on on the draft here:
https://docs.google.com/spreadsheets/d/12bAjNcmW92ZIsghLNfDlpuZALzO7GLkOODWrocu3sic/edit?usp=sharing
To use this capability add octo/content
to your Octo-Capabilities
header.
This capability extends the Supplier, Product, Option, Unit, Availability and Booking schemas to add additional descriptive content that can be used to populate product listings as well as for various for other use cases that require this information.
Since suppliers and their systems may offer content in different languages, this content capability supports localization through Accept-Language
request header as well as Content-Language
and Available-Languages
response headers as described below.
Header | Required | Description |
---|---|---|
Header | Required | |
---|---|---|
Content capability enriches existing OCTO Core Supplier, Product, Option, Unit, Availability and Booking objects with additional information listed below when octo/content
is added to the Octo-Capabilities
header of the request of any OCTO Core endpoint containing this object, given that the supplier system supports this capability.
Please select a tab below to view exact fields and details for each object:
Supplier object will be extended with additional information about the supplier as indicated below.
Please note introduction of an optional venue
concept. venue
object, whose fields mostly repeat supplier
ones, is designed for larger suppliers that operate multiple locations, venues, brands or destinations that may need to have different more specific supplier content information, as show in example below.
Working draft in Google Sheets: https://docs.google.com/spreadsheets/d/12bAjNcmW92ZIsghLNfDlpuZALzO7GLkOODWrocu3sic/edit?gid=478235837#gid=478235837
Fields | Type (Format) | Field Description |
---|---|---|
Fields | Type (Format) | Field Description |
---|---|---|
Fields | Type (Format) | Field Description |
---|---|---|
Fields | Type (Format) | Field Description |
---|---|---|
Fields | Format (Type) | Field Description |
---|---|---|
Fields | Type (Format) | Field Description |
---|---|---|