test-Profile-Documentation

This is a test for collaborative profile documentation Notes / Ideas for structure:

• TODO: Review and harmonize naming conventions with the Transmodel and NeTEx standards.
• Align the structure with Transmodel and NeTEx.

Table of Contents

• Foreword
• MMTIS Requirments
• Glossary
• Frames
• Common
• Reference Data
• Publishing Data
• Use Cases

Foreword

TODO: Write a foreword to NeTEx, explaining how to understand its parts and profiles. Suggested content structure:

Introduction to NeTEx

NeTEx

NeTEx (Network Timetable Exchange) is a European CEN standard for exchanging public transport data. It defines a comprehensive and flexible XML-based format for:

• Transport networks (routes, stops, operators)
• Timetables and schedules
• Fare structures
• Accessibility
• Operational data

NeTEx is modular, meaning it has different parts (frames) for different types of data. It’s designed to support national and international data exchange, especially for multimodal journey planning and passenger information systems.

Profiles

Profiles

Profiles are subsets or specializations of NeTEx. They define which parts of NeTEx to use, and how to use them, for specific purposes or use cases. Profiles help ensure interoperability and consistency across systems and countries.

🔹 EPIP – European Passenger Information Profile

• A profile of NeTEx focused on passenger information.
• Defines a minimum set of data needed for journey planning and real-time information.
• Used in systems like National Access Points (NAPs) across Europe.

🔹 EPIAP – European Passenger Information Accessibility Profile

• Builds on EPIP, but adds accessibility data for persons with reduced mobility.
• Includes data about stop accessibility, vehicle features, and boarding/alighting conditions.
• Supports compliance with PRM TSI (Technical Specifications for Interoperability).

Standard (NeTEx) vs Profile

NeTEx vs Profiles

Feature	NeTEx	Profiles (EPIP, EPIAP, etc.)
Scope	Full standard with all data structures	Subset tailored for specific use cases
Flexibility	Very flexible and comprehensive	Restrictive to ensure interoperability
Use	National/international data exchange	Harmonized implementation across systems
Complexity	High – requires configuration	Lower – predefined structure
Examples	All NeTEx frames	EPIP, EPIAP, Nordic Profile, DELFI+

MMTIS Requrements

TODO: Determine whether this section is necessary.

Glossary

TODO: Create a glossary of terms, possibly as a table of definitions.

Frames

TODO: Add a short introduction to frames—what they are and what they contain.

• CompositFrame
• ResourceFrame
• SiteFrame
• ServiceFrame
• ServiceCalendarFrame
• TimetableFrame
• VehicleScheduleFrame
• DriverScheduleFrame
• FareFrame

Common

TODO: Add a short introduction to the "Common" section.

• DateFormats
• Calendars

Reference Data

TODO: Add a short introduction to reference data.

• Stops
• Organisations
• VehicleType
• Vehicle

Publish Data

TODO: Add a short introduction to this section. It should describe how data is published in different scenarios and use cases.

• How to publish FareZone

Use Case

TODO: Add a short introduction explaining the purpose of use cases—when and why they are used, and how they help describe the application of profiles. Each use case should include:

• Required fields and frames
• Relevant objects
• Real-world examples

Use Cases and descriptions

Proposed Use Cases (to be modeled in examples and separate documentation files):

• Stops
  • Accesibility (with images, as Johan is doing with stops)
• Organisations
• Timetables
• Timetables with booking
• FareZones
• Fares
  • Documentation of relevant objects and fields