Introduction

This document describes a standard for exchanging data in the tourism domain, called AlpineBits® DestinationData.

AlpineBits® DestinationData is built upon:

The AlpineBits® DestinationData standard is intended for the exchange of touristic information between systems acting as clients and servers, where clients consume the data provided by the servers.

The AlpineBits® DestinationData standard includes the definition of:

  • specific server endpoints

  • resource types

  • support to GET requests

  • request and response headers and parameters

  • additional request features (e.g., pagination and hypermedia controls)

At the current version of the standard, the scope of AlpineBits® DestinationData covers exchanging data about events, event series, event venues, mountain areas, lifts, trails, snowparks, agents, and media objects.

1. Conventions and Definitions

The keywords “MUST”, “MUST NOT”, “REQUIRED”, “SHALL", “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC 2119.

Additionally, the following terminology is consistently used throughout this document:

  • CLIENT: the client system consuming data provided by a server

  • SERVER: the server system provides data to client systems and implements the AlpineBits® DestinationData

  • Resource Type: a type that describes the attributes and relations of a set of resources

  • Resource: an identified object that conforms to a resource type

  • Endpoint: the trailing part of a URL that provides access to HTTP request on an API