Best practice: topological aggregation vs owns*
Jump to navigation
Jump to search
Introduction
Normally <netElement> which is referred from <operationalPoint>/<spotLocation>/@netElemetRef is modelled as follows:
- It’s a non-linear <netElement>. Therefore, it does not have a child <netElement>/<associatedPositioningSystem>/<intrinsicCoordinate>/@instrinsicCoord=”1”
- It’s an aggregating (composition (external link)) <netElement> of either Meso or Macro <level> of aggregation. It aggregates everything that is “inside” station.
Some <infrastructure> however can be directly related to the station and be “outside” of it. A descriptive example is a distant <signalIS>. This <infrastructure> element is located on <netElement>s that can be not aggregated into the one referred from <operationalPoint>/<spotLocation>/@netElemetRef.
| Overview | Element is inside the <operationalPoint> | Element is used by the <operationalPoint> |
Rules
- Use topological aggregation for indicating that an entity (signal 69P2) is inside (within) the station (Cranz)
- Use <owns*> (<ownsSignal>) for indicating that an entity (signal 69Va) is “used” by the station (Cranz)