Repository navigation
Let an Application and a Process describe themselves #432
Description
Parent
What to build
An Application and each of its Processes can say in one plain sentence what they do. The estate dashboard shows it, so a reader knows what collector or reporter is without reading the code (JorisJonkers-dev/estate-dashboard#31).
- An optional
descriptionon an Application and on a Process in the project file. One sentence, plain words. - The fragment carries it unchanged. It renders nothing in the cluster.
Acceptance criteria
- Both implementations accept the field, and the schemas and worked examples show it.
- A description longer than one short sentence is refused (a length limit).
-
npm run verifyand theemfbuild pass.
Activity
feat(model): let an Application and a Process describe themselves
feat(model): let an Application and a Process describe themselves
ExtraToast commentedon Oct 29, 2026
Landed in #703: an optional
descriptionon an Application and on a Process, one sentence of at most 160 characters. It renders nothing, and the Intent Fragment carries it in the project file unchanged. A longer or empty one is aschemarefusal at the value. Decision: 0125, spec chapter 10 Describing an Application and a Process, REQ-121.emf/is frozen, so the field reaches it in the post-1.0 catch-up.