IS:propOther: Difference between revisions
Jump to navigation
Jump to search
[checked revision] | [checked revision] |
(Mehrere Attribute entfernt) |
(Undocumented enumeration items) |
||
Line 10: | Line 10: | ||
|inheritedAttributes=''None'' | |inheritedAttributes=''None'' | ||
|ownAttributes = | |ownAttributes = | ||
{{missing information|user=[[User:Ferri Leberl|Ferri Leberl]] ([[User talk:Ferri Leberl|talk]]) 15:40, 25 April 2018 (CEST)|topic=the semantics of the attributes}} | |||
* {{Attr|frontier}}: | * {{Attr|frontier}}: | ||
Revision as of 15:40, 25 April 2018
propOther
Scheme description / Schemenbeschreibung
Position of propOther in the XML-Tree / Position von propOther im XML-Baum
- Parent: <ocp>
- Children: <additionalName> (deprecated with version 2.1) <states>
Multiplicity / Anzahl
Semantics / Bedeutung
<propOperational> contains attributes which define additional properties of an <ocp>.
Attributes of propOther / Attribute von propOther
|
- frontier:
- chargeFrontier:
- status Possible values are:
- planned
- operational
- disabled
- closed
- other:anything: Any value that does not fit any value from the previous enumeration list, fulfilling the constraint: at minimum two characters, whitespace is not allowed. Please, apply Dev:usingAny accordingly.
Syntactic Constraints / Syntaktische Beschränkungen
- frontier xs:boolean, default: false, optional
- chargeFrontier xs:boolean, default: false, optional
- status default: operational, optional
Best practice & Examples / Empfohlene Anwendung & Beispiele
Not yet described. / Noch nicht beschrieben.
Notes / Anmerkungen
(introduced with version 2.0): use child element <additionalName> of <ocp> instead of <additionalName>.
Open issues / Offene Punkte/Pendenzen
Not yet described. / Noch nicht beschrieben.