Talk:Object positioning in the network: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
== Assumptions and Questions == | == Assumptions and Questions == | ||
# ''ElementPart'' is a class needed for splitting and fusioning NetElements for creating a new Network level. It has no specific role for positioning. Here, ''AssociatedNetElement'' is used, as described in the model | # ''ElementPart'' is a class needed for splitting and fusioning NetElements for creating a new Network level. It has no specific role for positioning. Here, ''AssociatedNetElement'' is used, as described in the model | ||
# Each AssociatedNetElement refers to one and only one PositionedNetElement. If this is so, then the association netElements of Linearlocation is somehow redundant, since it is covered by the netElements relation of AssociatedNetElement (see class diagram | # Each AssociatedNetElement in my understanding refers to one and only one PositionedNetElement. If this is so, then the association netElements of Linearlocation is somehow redundant, since it is covered by the netElements relation of AssociatedNetElement (see class diagram OrderedAssociatedNetElement on the wiki page). The model allows one ore more PositionedNetElement, but in case of more than one, where do the intrinsic coordinates or the parameter keepsOrientation refer to? | ||
# The ''applicationDirection'' of a SpotLocation refers to the orientation of the ''netElement'' of the SpotLocation. In the model it is defined with repect to the "LinearLocation" - might be an error. | # The ''applicationDirection'' of a SpotLocation refers to the orientation of the ''netElement'' of the SpotLocation. In the model it is defined with repect to the "LinearLocation" - might be an error. | ||
# The parameter ''keepsOrientation'' of AssociateNetElement is "1=true" if the orientation of the AssociateNetElement is the same as the PositionedNetElement. It is "0=false" if the orientation is reverse. (Model says in Fig. 42 it is described as relevant / not relevant) | # The parameter ''keepsOrientation'' of AssociateNetElement is "1=true" if the orientation of the AssociateNetElement is the same as the PositionedNetElement. It is "0=false" if the orientation is reverse. (Model says in Fig. 42 it is described as relevant / not relevant) | ||
Revision as of 22:08, 11 September 2016
Assumptions and Questions
- ElementPart is a class needed for splitting and fusioning NetElements for creating a new Network level. It has no specific role for positioning. Here, AssociatedNetElement is used, as described in the model
- Each AssociatedNetElement in my understanding refers to one and only one PositionedNetElement. If this is so, then the association netElements of Linearlocation is somehow redundant, since it is covered by the netElements relation of AssociatedNetElement (see class diagram OrderedAssociatedNetElement on the wiki page). The model allows one ore more PositionedNetElement, but in case of more than one, where do the intrinsic coordinates or the parameter keepsOrientation refer to?
- The applicationDirection of a SpotLocation refers to the orientation of the netElement of the SpotLocation. In the model it is defined with repect to the "LinearLocation" - might be an error.
- The parameter keepsOrientation of AssociateNetElement is "1=true" if the orientation of the AssociateNetElement is the same as the PositionedNetElement. It is "0=false" if the orientation is reverse. (Model says in Fig. 42 it is described as relevant / not relevant)
Insights
- Each PositioningNetElement has an orientation which means it has a beginning and an end, denoted by intrinsicCoordinates 0 and 1. Those are defined by the PositionedRelations referring to this PositioningNetElement.
- The PositionedRelations are crucial for building LinearLocations, including routes, since they define the navigability and orientation of the NetElements along the sequence