# OTI standard - draft 0.1 An open draft standard for the quality, accessibility and validity of public transport map information. **Scope:** printed and digital cartographic information for public transport, including onboard diagrams, stop information, local-area maps, line sheets, schematics, network and regional maps, websites, displays and tactile products. **Outside scope:** brand aesthetics. OTI proposes measurable minimums rather than one visual style; maps following different design traditions may meet the same requirements. **Structure:** principles, numbered requirements, A/AA/AAA levels, sufficient techniques and tests, and an open validator named `oti-check`. The level structure is inspired by WCAG; it is not an endorsement or a claim of equivalence. ## Principles 1. **Truthful:** represented information exists in the declared source; relevant omissions are disclosed. 2. **Current:** each product declares its validity period and is renewed when the network changes. 3. **Traceable:** source, version, feed fingerprint, generator, style and manual-edit authorship are recorded and reproducible. 4. **Perceivable:** information never depends on colour alone. Contrast and type size reflect viewing distance; text, tactile and easy-read alternatives depend on the proposed level. 5. **Understandable:** clear hierarchy, explicit frequency thresholds and consistent official and short names. 6. **Consistent:** every route and stop keeps its code, colour, order, name and pictogram across products. 7. **Open:** editorial data in GTFS-Carto is published under an open licence alongside the transport data. ## Proposed levels - **A:** a proposed baseline covering applicable legal requirements, validity and source disclosure. - **AA:** the draft target for authorities and procurement specifications: screen and print accessibility, explicit frequency information, multilingual content, timely renewal and a text alternative. - **AAA:** a proposed advanced level covering user validation, tactile and easy-read versions, continuous regeneration, live information and GTFS-Carto publication through a national access point. Conformance would be declared **per product**, for example: Network map X, A1 format, OTI 0.1 AA. These are draft level descriptions, not a current legal certification or a validated conformity scheme. ## Required validity panel Each product visibly declares its validity dates, generation date, source, feed version and fingerprint, data licence and error-reporting contact. The draft also requires machine-readable metadata, such as JSON-LD in `` or XMP. From AA, the proposal adds the generator, style, declared level and a QR link to the current version. ## Status Research document 04, section 5, explains the initial 56-requirement draft and its regulatory rationale. Numbered requirements, test methods and the proposed automated checks still need to be developed and validated. Existing software diagnostics must not be presented as full OTI certification. English is the primary language. The official project website is https://opentransitinformation.org.