fxdemo:05-part:07-naming-and-file-conventions:07-7-topic-naming:start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

fxdemo:05-part:07-naming-and-file-conventions:07-7-topic-naming:start [2026/08/09 17:23] – created owenfxdemo:05-part:07-naming-and-file-conventions:07-7-topic-naming:start [2026/08/09 17:24] (current) owen
Line 24: Line 24:
 Topic names should use stable business or architectural concepts rather than implementation-specific class names. A topic name should not change because the team refactors a class, moves a file, or renames a container. Topic names should use stable business or architectural concepts rather than implementation-specific class names. A topic name should not change because the team refactors a class, moves a file, or renames a container.
  
-The team should document every Phase 0 topic in the Topic Catalogue. A topic should not enter the [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]] unless the team can identify its purpose, [[dido:99_annexes:annex-b-terms-and-definitions:d:data_structure|Data Structure]], participating [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Nodes]], QoS expectations, and relationship to the Phase 0 demonstration.+The team should document every Phase 0 topic in the Topic Catalogue. A topic should not enter the [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]] unless the team can identify its purpose, data structure, participating [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Nodes]], QoS expectations, and relationship to the Phase 0 demonstration.
  
 ---- ----
  • fxdemo/05-part/07-naming-and-file-conventions/07-7-topic-naming/start.1786321437.txt.gz
  • Last modified: 2026/08/09 17:23
  • by owen