# Comparison

Training exercise

| Stat | Museum | Petstore | Train Travel |
|  --- | --- | --- | --- |
| References | 43 | 7 | 18 |
| External Documents | 0 | 3 | 0 |
| Schemas | 23 | 8 | 9 |
| Parameters | 6 | 9 | 6 |
| Path Items | 5 | 13 | 5 |
| Operations | 8 | 19 | 7 |
| Tags | 3 | 3 | 4 |


Relative to the others, it seem the Museum has too many Schemas.

The operations to schemas ratio is 35% for the Museum API.
It's 237% for the Petstore and 78% for the Train Travel API.

This indicates the Museum API isn't using a resource-oriented design, and likely has reusable components that are only used once.

details
summary
Source of stats
% redocly stats museum/museum.yaml
Document: museum/museum.yaml stats:

🚗 References: 43
📦 External Documents: 0
📈 Schemas: 23
👉 Parameters: 6
🔗 Links: 0
➡️  Path Items: 5
👷 Operations: 8
🔖 Tags: 3

museum/museum.yaml: stats processed in 6ms

Document: petstore/petstore.yaml stats:

🚗 References: 7
📦 External Documents: 3
📈 Schemas: 8
👉 Parameters: 9
🔗 Links: 0
➡️  Path Items: 13
👷 Operations: 19
🔖 Tags: 3

Document: train-travel/train-travel.yaml stats:

🚗 References: 18
📦 External Documents: 0
📈 Schemas: 9
👉 Parameters: 6
🔗 Links: 0
➡️  Path Items: 5
👷 Operations: 7
🔖 Tags: 4