IS:additionalName propOther: Difference between revisions
Jump to navigation
Jump to search
| [unchecked revision] | [checked revision] |
(Updated to current version using scheman contents and new templates) |
(multiplicity) |
||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 3: | Line 3: | ||
|parent = {{IS:Tag|propOther}} | |parent = {{IS:Tag|propOther}} | ||
|childs=''None'' | |||
|minocc=0 | |||
|inheritedAttributes=''None'' | |||
|semantics = | |semantics = | ||
{{Depr|2.1}} use {{IS:Tag|additionalName|ocp}} instead | {{Depr|2.1}} use {{IS:Tag|additionalName|ocp}} of {{IS:Tag|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. | The element {{IS:Tag|additionalName|propOther}} 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}}: This is the additional name of the {{IS:Doc|ocp}} | * {{Attr|value}}: This is the additional name of the {{IS:Doc|ocp}} | ||
{{InheritOcpNameType | |||
|type = | |||
|type_de = | |||
| | |||
}} | }} | ||
| Line 29: | Line 27: | ||
* {{Attr|value}} {{XsdType|string}}, mandatory | * {{Attr|value}} {{XsdType|string}}, mandatory | ||
{{InheritOcpNameTypeConstraints | |||
|type = | |||
|type_de = | |||
}} | |||
{{InheritLangConstraints}} | {{InheritLangConstraints}} | ||
One {{IS:Doc|ocp}} can have an unlimited number of {{IS:Tag|additionalName}} elements. | One {{IS:Doc|ocp}} can have an unlimited number of {{IS:Tag|additionalName|propOther}} elements. | ||
|notes = | |notes = | ||
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. | 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|propOther}} is optional. | ||
}} | }} | ||
Latest revision as of 19:28, 25 November 2018
additionalName
Scheme description / Schemenbeschreibung
Position of additionalName in the XML-Tree / Position von additionalName im XML-Baum
- Parent: <propOther>
- Children: None
Multiplicity / Anzahl
Semantics / Bedeutung
(deprecated with version 2.1) use <additionalName> of <ocp> 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 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.
- 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
- value xs:string, mandatory
- type: union of (restriction of xs:string, tOtherEnumerationValue); tOtherEnumerationValue is an arbitrary string starting with 'other:' followed by at minimum two characters, white space not allowed for extending railML® enumeration lists; optional
- xml:lang: xs:language, language identification, 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.