> For the complete documentation index, see [llms.txt](https://contributor.openactive.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://contributor.openactive.io/style-guide.md).

# Style Guide

## Consistency of the OpenActive brand name and specs

"OpenActive" must always be referenced as "**OpenActive**", rather than "OA" or "Open Active".

When OpenActive is included in a URL path, it should be styled "**openactive**", rather than "open-active" or "open\_active".

Real-time Paged Data Exchange feeds must always be referred to as the "**RPDE feeds**", rather than "OpenActive feeds" or "feeds".

The Modelling Opportunity Data specification must always be referred to as the "**Modelling specification**".

Implementations of the Open Booking API must always be referred to as the "**Open Booking API**", rather than "OBA" or "Open Booking".

## Naming of data model terms

The [OpenActive Vocabulary](https://openactive.io/ns/) is based on [schema.org](https://schema.org/), and therefore the [schema.org style guide](https://schema.org/docs/styleguide.html) must be followed for all data model terms (all [OpenActive Vocabulary terms](https://openactive.io/ns/), [beta terms](https://openactive.io/ns-beta/), and extension terms), as any of these may be [considered for inclusion](https://github.com/schemaorg/schemaorg/issues/1457) by schema.org in future.

## Use of US and UK English spellings

The [schema.org style guide](https://schema.org/docs/styleguide.html) states "US spellings must be used", therefore all data model terms must use US spelling.

Except when referencing Vocabulary terms, OpenActive documentation and specifications are written using UK English spellings.

## General writing guidelines

The [OpenStack guidelines](https://docs.openstack.org/doc-contrib-guide/writing-style/general-writing-guidelines.html) must be applied when writing documentation.