|
|
| Line 8: |
Line 8: |
| {{robot|subschema=IS|element=netElement|parent=}} | | {{robot|subschema=IS|element=netElement|parent=}} |
| ==={{semantics}}=== | | ==={{semantics}}=== |
| | |
| | {{semcon|Aggregation of net elements should follow the tree data structure. See figure below. |
| | This means that no two (mesoscopic) net elements can aggregate same (microscopic) net element. |
| | In other words, (microscopic) net element can be aggregated by at most one (mesoscopic) net element. |
| | |
| | Compare {{ticket|xxx}} |
| | |status=proposed|proposed=2021-02-26|forum={{ticket|xxx}} |
| | |id=IS:008}} |
| | |
| | |
| | |
| | {{semcon|Linear (geometric) coordinates (explicit or implicit, e.g. calculated as a sum of the coordinate of beginning and the lent of the net element) of the same place represented at different levels of aggregation should have the same value. In the figure below (linear) coordinate the coordinate of e.g. end of ne1 should be same as one of ne1.2. |
| | |
| | Compare {{ticket|xxx}} |
| | |status=proposed|proposed=2021-02-26|forum={{ticket|xxx}} |
| | |id=IS:009}} |
| | |
| | |
| | ┌──────────────────────────────────────────────────────────┐ ┌───────────────────────────────────────────────────────┐ |
| | │ │ │ │ |
| | │ net element 1 │ │ net element │ |
| | │ │ │ │ |
| | │ │ │ │ |
| | └──────────────────────────────────────────────────────────┘ └───────────────────────────────────────────────────────┘ |
| | disjoint set disjoint set |
| | ┌───────────────────────────────────────────────────────────────┐ ┌────────────────────────────────────────────────────────────┐ |
| | │ │ │ │ |
| | ┌──────────────────────────┐ ┌──────────────────────────┐ ┌──────────────────────────┐ ┌──────────────────────────┐ |
| | │ │ │ │ │ │ │ │ |
| | │ net element 1.1 │ │ net element 1.2 │ │ net element │ │ net element │ |
| | │ │ │ │ │ │ │ │ |
| | │ │ │ │ │ │ │ │ |
| | └──────────────────────────┘ └──────────────────────────┘ └──────────────────────────┘ └──────────────────────────┘ |
| | ┌───────────┐ ┌───────────┐ ┌───────────┐ ┌───────────┐ ┌───────────┐ ┌───────────┐ ┌───────────┐ ┌───────────┐ |
| | │ net │ │ net │ │ │ │ │ │ │ │ │ │ │ │ │ |
| | │ element │ │ element │ │ net │ │ net │ │ net │ │ net │ │ net │ │ net │ |
| | │ 1.1.1 │ │ 1.1.1 │ │ element │ │ element │ │ element │ │ element │ │ element │ │ element │ |
| | └───────────┘ └───────────┘ └───────────┘ └───────────┘ └───────────┘ └───────────┘ └───────────┘ └───────────┘ |
| | │ │ │ │ │ │ |
| | └────────────────────────────┘ └─────────────────────────────┘ └───────────────────────────┘ |
| | disjoint set disjoint set disjoint set |
| | |
| | |
| | |
| {{importComment}} | | {{importComment}} |
| =={{examples}}== | | =={{examples}}== |
Introduction
Documentation
Syntax
Autoexport from the XML-Schema for element IS:netElement of railML ® version 3.2 |
| Documentation
|
The NetElement type is derived from the RailTopoModel class PositioningNetElement.
|
| Subschema
|
infrastructure
|
| Parents*
|
netElements
|
| Children
|
associatedPositioningSystem (1..*), designator (0..*), elementCollectionOrdered (0..*), elementCollectionUnordered (0..*), isValid (0..*), name (0..*), relation (0..*)
|
Attributes:
- length: length of the NetElement in metres (optional;
xs:decimal),
- id: the identifier of the object; this can be either of type xs:ID or UUID (obligatory;
xs:string; patterns: (urn:uuid:)?[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}|{[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}}); compare: Dev:Identities
|
*Notice:
Elements may have different parent elements. As a consequence they may be used in different contexts.
Please, consider this as well as a user of this wiki as when developing this documentation further.
Aspects that are only relevant with respect to one of several parents should be explained exclusively in the documentation of the respective parent element.
|
Autoexport from the XML-Schema for element IS:netElement of railML ® version 3.1 |
| Documentation
|
The NetElement type is derived from the RailTopoModel class PositioningNetElement.
|
| Subschema
|
infrastructure
|
| Parents*
|
netElements
|
| Children
|
associatedPositioningSystem (1..*), elementCollectionOrdered (0..*), elementCollectionUnordered (0..*), isValid (0..*), name (0..*), relation (0..*)
|
Attributes:
- length: length of the NetElement in metres (optional;
xs:decimal),
- id: the identifier of the object; this can be either of type xs:ID or UUID (obligatory;
xs:ID; patterns: (urn:uuid:)?[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}|{[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}}); compare: Dev:Identities
|
*Notice:
Elements may have different parent elements. As a consequence they may be used in different contexts.
Please, consider this as well as a user of this wiki as when developing this documentation further.
Aspects that are only relevant with respect to one of several parents should be explained exclusively in the documentation of the respective parent element.
|
Changes 3.1→3.2
The children have changed.
The attributes have been changed.
Semantics
|
Proposed Semantic Constraint "IS:008":
Aggregation of net elements should follow the tree data structure. See figure below.
This means that no two (mesoscopic) net elements can aggregate same (microscopic) net element.
In other words, (microscopic) net element can be aggregated by at most one (mesoscopic) net element.
Compare #xxx
Proposed on February 26th 2021
Discuss this semantic constraint
Please, recognize our guidelines on semantic constraints
|
|
|
|
Proposed Semantic Constraint "IS:009":
Linear (geometric) coordinates (explicit or implicit, e.g. calculated as a sum of the coordinate of beginning and the lent of the net element) of the same place represented at different levels of aggregation should have the same value. In the figure below (linear) coordinate the coordinate of e.g. end of ne1 should be same as one of ne1.2.
Compare #xxx
Proposed on February 26th 2021
Discuss this semantic constraint
Please, recognize our guidelines on semantic constraints
|
|
┌──────────────────────────────────────────────────────────┐ ┌───────────────────────────────────────────────────────┐
│ │ │ │
│ net element 1 │ │ net element │
│ │ │ │
│ │ │ │
└──────────────────────────────────────────────────────────┘ └───────────────────────────────────────────────────────┘
disjoint set disjoint set
┌───────────────────────────────────────────────────────────────┐ ┌────────────────────────────────────────────────────────────┐
│ │ │ │
┌──────────────────────────┐ ┌──────────────────────────┐ ┌──────────────────────────┐ ┌──────────────────────────┐
│ │ │ │ │ │ │ │
│ net element 1.1 │ │ net element 1.2 │ │ net element │ │ net element │
│ │ │ │ │ │ │ │
│ │ │ │ │ │ │ │
└──────────────────────────┘ └──────────────────────────┘ └──────────────────────────┘ └──────────────────────────┘
┌───────────┐ ┌───────────┐ ┌───────────┐ ┌───────────┐ ┌───────────┐ ┌───────────┐ ┌───────────┐ ┌───────────┐
│ net │ │ net │ │ │ │ │ │ │ │ │ │ │ │ │
│ element │ │ element │ │ net │ │ net │ │ net │ │ net │ │ net │ │ net │
│ 1.1.1 │ │ 1.1.1 │ │ element │ │ element │ │ element │ │ element │ │ element │ │ element │
└───────────┘ └───────────┘ └───────────┘ └───────────┘ └───────────┘ └───────────┘ └───────────┘ └───────────┘
│ │ │ │ │ │
└────────────────────────────┘ └─────────────────────────────┘ └───────────────────────────┘
disjoint set disjoint set disjoint set
Best Practice / Examples
Additional Information
Notes
Open Issues
