IS:ocpVis: Difference between revisions
Jump to navigation
Jump to search
| [checked revision] | [checked revision] |
(Added explanation for the repeated deprecation of the element in rml 2.5) |
No edit summary |
||
| Line 7: | Line 7: | ||
|intro=2.4 | |intro=2.4 | ||
|depr=2.1 and 2.5 | |depr=2.1 and 2.5 | ||
|semantics=This Element has been deprecated with {{rml}} 2.1 but reintroduced with {{rml}} 2.4. Its purpose is to visualize {{Tag|IS|ocp}} elements. In {{rml|2.5}} it has been replaced with {{tag|IS|objectVis}}. | |semantics=This Element has been deprecated with {{rml}} 2.1 but reintroduced with {{rml}} 2.4. Its purpose is to visualize {{Tag|IS|ocp}} elements. In {{rml|2.5}} it has been replaced with {{tag|IS|objectVis}}.<br> The reason for this was that {{tag|IS|objectVis}} allows specifying coordinates for not just {{IS:Tag|ocp}}, but also other infrastructure elements that do not belong to a line or track, e.g. {{IS:Tag|controller}}; | ||
|ownAttributes= | |ownAttributes= | ||
*{{attr|ref}}: reference is required because it's the purpose of the element | *{{attr|ref}}: reference is required because it's the purpose of the element | ||
Revision as of 14:19, 22 November 2022
<ocpVis>
|
Scheme description / Schemenbeschreibung
Position of <ocpVis> in the XML-Tree / Position von <ocpVis> im XML-Baum
- Parent: <visualization>
- Children: <position>, <size>
Multiplicity / Anzahl
Semantics / Bedeutung
This Element has been deprecated with railML® 2.1 but reintroduced with railML® 2.4. Its purpose is to visualize <ocp> elements. In railML® 2.5 it has been replaced with <objectVis>.
The reason for this was that <objectVis> allows specifying coordinates for not just <ocp>, but also other infrastructure elements that do not belong to a line or track, e.g. <controller>;(introduced with version 2.4) (deprecated with version 2.1 and 2.5)
Attributes of <ocpVis> / Attribute von <ocpVis>
- 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
Not yet described. / Noch nicht beschrieben.
Open issues / Offene Punkte/Pendenzen
Not yet described. / Noch nicht beschrieben.