As a service builder, I need entities to be identifiable in plain language so that services can present information clearly, support user journeys, and avoid confusion caused by technical references alone.
- Priority
- medium
- Status
- proposed
- Themes
- data-principle
- Actors
- service-builder
- Source
- data-design
Justification
Justification just-0017
Requiring a `name` field on every dataset gives services a consistent display label, which matters when planning decisions rely on human judgement and discussion rather than long identifiers. For example, a planning condition name lets services present conditions clearly instead of relying on codes alone, and a Site name lets planners refer to the site in discussions and reports with less ambiguity.
Satisfaction: full; Confidence: high
Satisfied by:
Rule:
{
"applies_to": "dataset",
"requires": [
{
"field": "name"
}
]
}
See complete justification record: just-0017