Summary
This epic tracks the work required to establish GTFS Validator as a standalone service that can be developed, deployed, and operated independently from the core gtfs-validator release cycle and from MobilityData-specific deployment assumptions.
A key objective of this effort is to ensure that the standalone GTFS Validator service is not tied to MobilityData-specific infrastructure, web deployment patterns, or operational constraints. The service should be designed so it can be adopted, deployed, and integrated in a more generic way by different environments and clients. At the same time, this will help to release more regularly on the UI and API components without affecting the core validation rules.
Goals
- Refine the OpenAPI schema to improve clarity, integration, and maintainability
- Decouple web validator deployment from core validator releases
- Define and implement a standalone validator API service
- Remove dependency on MobilityData-specific deployment details and assumptions
- Support API-based access for the Web UI and other consumers
Scope
This epic covers the design and implementation work needed to expose GTFS validation through a dedicated service layer, including deployment architecture, API design, and Web UI integration.
The work should aim to:
- Separate the validator service from MobilityData-specific deployment concerns
- Define stable service interfaces for validation workflows
- Allow the Web UI to consume validator functionality through the API
- Enable future reuse by other clients and environments
Expected outcomes
- The web validator can be deployed independently of core validator releases
- A standalone validator API service is available for programmatic access
- The service is no longer coupled to MobilityData-specific deployment details
- The Web UI can consume validator functionality through the API
- The architecture is better positioned to support additional clients and deployment environments in the future
Related issues
Summary
This epic tracks the work required to establish GTFS Validator as a standalone service that can be developed, deployed, and operated independently from the core
gtfs-validatorrelease cycle and from MobilityData-specific deployment assumptions.A key objective of this effort is to ensure that the standalone GTFS Validator service is not tied to MobilityData-specific infrastructure, web deployment patterns, or operational constraints. The service should be designed so it can be adopted, deployed, and integrated in a more generic way by different environments and clients. At the same time, this will help to release more regularly on the UI and API components without affecting the core validation rules.
Goals
Scope
This epic covers the design and implementation work needed to expose GTFS validation through a dedicated service layer, including deployment architecture, API design, and Web UI integration.
The work should aim to:
Expected outcomes
Related issues