IS:additionalName propOther: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[unchecked revision][unchecked revision]
mNo edit summary
(Updated to current version using scheman contents and new templates)
Line 1: Line 1:
{{elementDocu|
{{ElementDocu|
elementName = additionalName
elementName = additionalName
|parent = {{DocIS|propOther}}
 
|parent = {{IS:Tag|propOther}}
 
|semantics =
{{Depr|2.1}} use {{IS:Tag|additionalName|ocp}} instead
 
The element {{IS:Tag|additionalName}} encloses a secondary name for an {{IS:Doc|ocp}}. Thus, multiple names for an {{IS:Doc|ocp}} can be provided for e. g. different languages, different meanings or different character sets.


|ownAttributes =
|ownAttributes =
* {{attr|value}}: the additional name of the OCP ({{xsdType|string}}, required)
* {{Attr|value}}: This is the additional name of the {{IS:Doc|ocp}}
* {{attr|type}}: the meaning of the additional name ({{xsdType|string}}, optional), in particular:
** ''operationalName'': the OCPs name under operational aspects
** ''trafficName'': the OCPs name under traffic aspects
** ''localName'': an additional name in the local language
* {{attr|lang}}: the language used for the name; 2 character abbrevation according to ISO 639-1 (xml:lang, optional)


|semantics =
* {{Attr|type}}: This is the meaning of the additional name. Possible values are:
The element {{IS:Tag|additionalName}} encloses a secondary name for an {{DocIS|ocp}}. Thus, multiple names for an OCP can be provided for e. g. different languages, different meanings or different character sets. One OCP can have an unlimited number of {{IS:Tag|additionalName}}-elements.
:* {{Enum|operationalName}} the {{IS:Doc|ocp}}s name under operational aspects
:* {{Enum|trafficName}} the {{IS:Doc|ocp}}s name under traffic aspects
:* {{Enum|localName}} an additional name in the local language
:* {{OtherEnum
|notes_en =
|notes_de =
}}
 
{{InheritLang
|notes_en =
|notes_de =
}}
 
|constraints =
* {{Attr|value}} {{XsdType|string}}, mandatory
 
* {{Attr|type}} optional
 
{{InheritLangConstraints}}
 
One {{IS:Doc|ocp}} can have an unlimited number of {{IS:Tag|additionalName}} elements.


|notes =
|notes =
* The primary name of an OCP will always be the values provided in the {{attr|name}} of {{DocIS|ocp}}. The usage of {{IS:Tag|additionalName}} is optional.
The primary name of an {{IS:Doc|ocp}} will always be the values provided in the {{Attr|name}} of {{IS:Tag|ocp}}. The usage of {{IS:Tag|additionalName}} is optional.
* A list of language abbrevations according to ISO 639-1 can be found [http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes here]
 
|backHome = IS:elements
}}
}}

Revision as of 14:03, 8 December 2011


additionalName
 


Scheme description / Schemenbeschreibung

Position of additionalName in the XML-Tree / Position von additionalName im XML-Baum

  • Parent: <propOther>
  • Children: Not yet described. / Noch nicht beschrieben.

Multiplicity / Anzahl

[1..1]

Semantics / Bedeutung

(deprecated with version 2.1) use <additionalName> instead

The element <additionalName> encloses a secondary name for an ocp. Thus, multiple names for an ocp can be provided for e. g. different languages, different meanings or different character sets.

Attributes of additionalName / Attribute von additionalName

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


  • xml:lang (introduced with version 2.1): This is a unique identifier of language. It uses basically the language standard IETF BCP 47 (external link) which may be different to ISO 639-1 (external link) or ISO 639-2 (external link). For mapping hints see relation to other standards (external link).

Syntactic Constraints / Syntaktische Beschränkungen

  • type optional

One ocp can have an unlimited number of <additionalName> elements.

Best practice & Examples / Empfohlene Anwendung & Beispiele

Not yet described. / Noch nicht beschrieben.

Notes / Anmerkungen

The primary name of an ocp will always be the values provided in the name of <ocp>. The usage of <additionalName> is optional.

Open issues / Offene Punkte/Pendenzen

Not yet described. / Noch nicht beschrieben.

Retrieved from "https://wiki2.railml.org/index.php?title=IS:additionalName_propOther&oldid=2957"