publish to leaf topics only (#137)

scripts/generate-bundle.py

@@ -39,6 +39,9 @@
                     if topic_to_add.startswith('/'):
                         topic_to_add = topic_to_add.lstrip('/')
 
+                    test_parent_dir = f'{root}/{row[0]}'
+                    if os.path.isdir(test_parent_dir):
+                        break
                     topics.append(topic_to_add)
 
 with open('topic-hierarchy/earth-system-discipline.csv', 'w') as fh:

standard/requirements/core/REQ_publishing.adoc

@@ -5,4 +5,6 @@
 ^|A |Data SHALL NOT be published with a topic that is not defined in this specification.
 ^|B |Data SHALL be published to at least the level of the sub-discipline topic (level 8 or beyond).
 ^|C |Metadata SHALL be published to at least the level of the notification type (``metadata``).
+^|D |Topics SHALL be published to the lowest possible defined level (leaf).
+^|E |Topics SHALL NOT be published to intermediary levels where sublevels are defined.
 |===

standard/sections/clause_7_normative_text.adoc

@@ -53,7 +53,7 @@ The table below provides an overview of the primary topic levels.
 |Seven high-level categories as defined by the WMO Unified Data Policy, Annex 1: (``atmospheric-composition``, ``climate``, ``cryosphere``, ``hydrology``, ``ocean``, ``space-weather``, or ``weather``)
 |===
 
-==== Publishing guidelines
+==== Publishing
 
 For maximum utility and efficient management of topics, it is recommended that ``data`` and ``metadata`` are published to a detailed level of the topic hierarchy. This helps  avoid the "pollution" of messages under the primary topics.  Note that each discipline has a sub-discipline topic named ``experimental`` for publication to provisional topics.