[Spike] How to organize seal of approval criteria endpoint(s)

[Alessandro100]

For users and clients (mobilitydatabase) determine the best way to deliver all the necessary information to figure out the status of the feed based on:

• Official
• Available
• Compliant
• Fresh
• Stable
• Unstable

Some of this data is already available as separate endpoints or bundled in others.

Acceptance Criteria

• A clear decision of endpoint(s) that need to be created for users to get the reliability status of the feed
• An openAPI schema with the endpoints

[emmambd]

Roughly finalized definition is available here

Main changes are:

Freshness now has 3 components rather than 2

_- Includes 7 days or more service coverage each day

• Has continuous service coverage across datasets with no coverage gaps
• Has service coverage that covers a period of two years or less_

We're using both feed info and calendar dates to evaluate continuous service coverage

• Calculation in the document above

Minor changes to grace periods

We will be marking some feeds as "seasonal" and omitting the 7 day rolling service coverage check for those