View Issue Details

IDProjectCategoryView StatusLast Update
000726110000-003: Address SpaceSpecpublic2021-11-23 18:08
ReporterEtienne Rossignon Assigned ToJeff Harding  
PrioritynormalSeverityminorReproducibilityN/A
Status assignedResolutionopen 
Product Version1.05.00 RC1 
Summary0007261: Clarifying HasChild Reference Definition
Description

The specification is not clear as whether a given Child Node can have one or multiple parent.

7.5 HasChild ReferenceType ToC Previous Next
The HasChild ReferenceType is an abstract ReferenceType; only subtypes of it can be used. It is a subtype of HierarchicalReferences.
The semantic is to indicate that References of this type span a non-looping hierarchy.
Starting from Node “A” and only following References of the subtypes of the HasChild ReferenceType it shall never be possible to return to “A”.
But it is allowed that following the References there may be more than one path leading to another Node “B”.


issue 1;
in the sentence "But it is allowed that following the References there may be more than one path leading to another Node “B”.' it is not clear if the term 'References' refers to a HasChild mentioned before or all types references.

issue2:
Although we understand easily that one parent node may have multiple children. The specs doesn't clearly state if it is possible for one given child item to have multiple parents.


I would suggest that the specification clearly states:

  • It is possible for one child node to have one or more parent nodes, as far the non-looping rule is preserved

or

  • one child node should only point to one single parent node.

whichever is correct.

TagsNo tags attached.
Commit Version
Fix Due Date

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2021-09-17 05:39 Etienne Rossignon New Issue
2021-11-23 18:08 Jim Luth Assigned To => Jeff Harding
2021-11-23 18:08 Jim Luth Status new => assigned