Template:InheritOcpNameType: Difference between revisions

[unchecked revision]

Revision as of 11:21, 24 January 2013

type: This is the meaning of the name. Possible values are:
- operationalName the ocps name under operational aspects
- trafficName the ocps name under traffic aspects
- localName an name in the local language
- 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.

@@ Line 1: / Line 1: @@
-* {{Attr|type}}: This is the meaning of the name. Possible values are:
+<ul>
-:* {{Enum|operationalName}} the {{IS:Doc|ocp}}s name under operational aspects
+<li>{{Attr|type}}: This is the meaning of the name. Possible values are:
-:* {{Enum|trafficName}} the {{IS:Doc|ocp}}s name under traffic aspects
+* {{Enum|operationalName}} the {{IS:Doc|ocp}}s name under operational aspects
-:* {{Enum|localName}} an name in the local language
+* {{Enum|trafficName}} the {{IS:Doc|ocp}}s name under traffic aspects
-:* {{OtherEnum
+* {{Enum|localName}} an name in the local language
+* {{OtherEnum
 |notes_en =
 |notes_de =
 }}
-: {{AddAnn|{{{type|}}}|{{{type_de|}}} }}<noinclude>[[Category:AttributeTemplate]]</noinclude>
+{{AddAnn|{{{type|}}}|{{{type_de|}}} }}</li></ul><noinclude>[[Category:AttributeTemplate]]</noinclude>