View Issue Details

IDProjectCategoryView StatusLast Update
000614910000-003: Address SpaceSpecpublic2020-12-07 16:47
ReporterWolfgang Mahnke Assigned ToJeff Harding  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Summary0006149: Can hierarchical References by symmetric?
Description

I found in the DI specification a ReferenceType beeing symmetric and hierarchical (ConnectsTo).
That seems fundamentally wrong to me, as a hierarchical Reference always implies an "up" and "down" (parent / child) inside a hierarchy (at least to me). However, I have not found any statement in the spec, stating that this is not allowed.

Consequences if we clarify it: DI spec becomes invalid - we would need to add a mantis issue there.
Consequences if we leave it open: Tree views using hierarchical references will automatically run into a loop since with those symmetric, hierachical references as the child points to the parent with the same reference (not the inverse one).

TagsNo tags attached.
Commit Version
Fix Due Date

Relationships

related to 0006152 resolvedKarl Deiretsbacher 10000-100: Devices Can hierarchical References by symmetric? 

Activities

Jeff Harding

2020-10-13 19:24

developer   ~0013048

I suggest we fix the DI spec and strengthen the description of hierarchical References in Part 3 to state they are never symmetric.

Jeff Harding

2020-10-13 19:41

developer   ~0013049

Added clarification to the definition of HierarchicalReferences as follows:
The HierarchicalReferences ReferenceType is an abstract ReferenceType; only subtypes of it can be used and they shall be a non-symmetric reference

Jim Luth

2020-12-07 16:47

administrator   ~0013380

Agreed to change in Virtual F2F.

Issue History

Date Modified Username Field Change
2020-10-12 11:42 Wolfgang Mahnke New Issue
2020-10-13 15:26 Jim Luth Assigned To => Jeff Harding
2020-10-13 15:26 Jim Luth Status new => assigned
2020-10-13 15:26 Jim Luth Issue cloned: 0006152
2020-10-13 15:26 Jim Luth Relationship added related to 0006152
2020-10-13 19:24 Jeff Harding Note Added: 0013048
2020-10-13 19:41 Jeff Harding Status assigned => resolved
2020-10-13 19:41 Jeff Harding Resolution open => fixed
2020-10-13 19:41 Jeff Harding Fixed in Version => 1.05
2020-10-13 19:41 Jeff Harding Note Added: 0013049
2020-12-07 16:47 Jim Luth Status resolved => closed
2020-12-07 16:47 Jim Luth Note Added: 0013380