ObjectClassification.isTopParent - new property to be added

[essvee]

See meeting notes: 12th Jan 23

Instances of this class can be nested within each other/used to represent a more informal hierarchy of classification. We need to allow implementers to explicitly state in which direction the hierarchy goes. We want to allow both but the most common situation will be Increasing levels of specificity. How will we let the user indicate that?

~Question: i'm pretty sure we decided on the following approach, but the notes aren't definite. Also do we want to make this mandatory, or just recommended for use at the whichever end is the 'top' of the hierarchy if that's what you're trying to model? (if the latter, why not just have an isTopOfHierarchy' flag?) ~ Answered - see comments

• [ ] ~Add new property: ClassificationLevelRank (integer, required = ???. repeatable = no)~
• [ ] ~In usage notes need to explain how this is intended to be used and make it clear that 1 is the highest rank.~

[essvee]

See meeting notes: 31st March 23

This term should not be mandatory.

• [x] Rename to ‘isTopParent’ is flag
• [x] Add recommendation that if you use it, the 'parent' instance of the class is set to 'true' and all other instances of isTopParent are 'false'. If you don't need to flag the parent/it is self-evident, do not populate this term.

[essvee]

Closed by #474