IS:objectVis: Difference between revisions
Jump to navigation
Jump to search
| [checked revision] | [checked revision] |
(Duplikat) |
(added notes) |
||
| Line 11: | Line 11: | ||
|constraints= | |constraints= | ||
*{{attr|ref}}: {{railMLType|tGenericRef}}; required | *{{attr|ref}}: {{railMLType|tGenericRef}}; required | ||
|notes= | |||
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. | |||
}} | }} | ||
Revision as of 13:06, 20 April 2023
|
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
Not yet described. / Noch nicht beschrieben.
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.