IS:additionalName propOther: Difference between revisions
Jump to navigation
Jump to search
| [unchecked revision] | [unchecked revision] |
(Die Seite wurde neu angelegt: {{elementDocu| elementName = additionalName |parent = {{DocIS|propOther}} |ownAttributes = * {{attr|value}}: the additional name of the OCP ({{xsdType|string}}, requir...) |
mNo edit summary |
||
| Line 16: | Line 16: | ||
|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 OCP will always be the values provided in the {{attr|name}} of {{DocIS|ocp}}. The usage of {{IS:Tag|additionalName}} is optional. | ||
* A list of language abbrevations according to ISO 639-1 can be found | * 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] | ||
}} | }} | ||
Revision as of 22:08, 12 October 2009
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
Semantics / Bedeutung
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. One OCP can have an unlimited number of <additionalName>-elements.
Attributes of additionalName / Attribute von additionalName
- value: the additional name of the OCP (xs:string, required)
- type: the meaning of the additional name (xs: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
- lang: the language used for the name; 2 character abbrevation according to ISO 639-1 (xml:lang, optional)
Syntactic Constraints / Syntaktische Beschränkungen
Not yet described. / Noch nicht beschrieben.
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.
- A list of language abbrevations according to ISO 639-1 can be found here
Open issues / Offene Punkte/Pendenzen
Not yet described. / Noch nicht beschrieben.