IS:objectVis: Difference between revisions
Jump to navigation
Jump to search
| [checked revision] | [checked revision] |
(added ref for example) |
(railML→{{rml}}) |
||
| Line 15: | Line 15: | ||
please refer to [https://wiki2.railml.org/wiki/IS:infrastructureVisualizations <IS:infrastructureVisualizations>] for the example | please refer to [https://wiki2.railml.org/wiki/IS:infrastructureVisualizations <IS:infrastructureVisualizations>] for the example | ||
|notes= | |notes= | ||
One can find out whether something is visualized by <trackElementVis> or <objectVis> by finding its position in the | One can find out whether something is visualized by <trackElementVis> or <objectVis> by finding its position in the {{rml}} hierarchy. Every child of a <track> element is visualized by <trackElementVis>. In that, operation control points are <objectVis> elements. | ||
}} | }} | ||
Latest revision as of 19:40, 22 January 2024
|
Scheme description / Schemenbeschreibung
Position of <objectVis> in the XML-Tree / Position von <objectVis> im XML-Baum
- Parent: <visualization>
- Children: <position>, <size>
Multiplicity / Anzahl
Semantics / Bedeutung
(introduced with version 2.5) Visualization of an object that is not on a <line>/<track>, e.g. an <ocp> or a <controller>. It generalizes and replaces <ocpVis>.(introduced with version 2.5)
Attributes of <objectVis> / Attribute von <objectVis>
- ref: reference is required because it's the purpose of the element
Syntactic Constraints / Syntaktische Beschränkungen
- ref: xs:IDREF; required
Best practice & Examples / Empfohlene Anwendung & Beispiele
please refer to <IS:infrastructureVisualizations> for the example
Notes / Anmerkungen
One can find out whether something is visualized by <trackElementVis> or <objectVis> by finding its position in the railML® hierarchy. Every child of a <track> element is visualized by <trackElementVis>. In that, operation control points are <objectVis> elements.
Open issues / Offene Punkte/Pendenzen
Not yet described. / Noch nicht beschrieben.