Template:InheritAdditionalName: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[checked revision][checked revision]
No edit summary
(Updated description of @name, @description and @xml:lang to match Template:InheritIdName)
Line 10: Line 10:
|inheritedAttributes={{#if:{{{inheritedAttributes|}}}|{{{inheritedAttributes}}}|''None''}}
|inheritedAttributes={{#if:{{{inheritedAttributes|}}}|{{{inheritedAttributes}}}|''None''}}
|ownAttributes =
|ownAttributes =
* {{Attr|name}}: This should be interpreted in its elements' context. {{AddAnn|{{{name|}}}|{{{name_de|}}} }}
* {{Attr|name}}: Established, human-readable short string, giving the {{{parentLink|FIXME}}} object a name. Not intended for machine interpretation, please see our [[Dev:identities#Differentiation_from_other_indications|notice on human interpretable data fields]].<br>{{deu|Etablierte, menschenlesbare kurze Zeichenkette, die das {{{parentLink|FIXME}}} Objekt benennt. Nicht zur maschinellen Interpretation bestimmt, siehe [[Dev:identities#Differentiation_from_other_indications|Hinweise zu menschenlesbaren Datenfeldern]].}}{{AddAnn|{{{name|}}}|{{{name_de|}}} }}
 
* {{Attr|description}}: Human-readable, more detailed description as addition to the name. It should give additional explanations or hints to the contents of the this {{{parentLink|FIXME}}} element. Not intended for machine interpretation, please see our [[Dev:identities#Differentiation_from_other_indications|notice on human interpretable data fields]].<br>{{deu|Menschenlesbare, detailliertere Beschreibung als Ergänzung zu {{Attr|name}}. Sie soll zusätzliche Erläuterungen oder Hinweise auf den Inhalt dieses {{{parentLink|FIXME}}} Elements geben. Nicht zur maschinellen Interpretation bestimmt, siehe [[Dev:identities#Differentiation_from_other_indications|Hinweise zu menschenlesbaren Datenfeldern]].}}{{AddAnn|{{{description|}}}|{{{description_de|}}}}}
* {{Attr|description}}: This should be interpreted in its elements' context, it substantiates the {{Attr|name}}. {{AddAnn|{{{description|}}}|{{{description_de|}}} }}
 
{{InheritLang
{{InheritLang
|notes_en =Examples for the usage of xml:lang in the context of additionalName elements can be found on page '''[[IS:additionalName_ocp#Best_practice_.26_Examples_.2F_Empfohlene_Anwendung_.26_Beispiele_.2F_Bonnes_pratiques_.26_exemples|IS:additionalName ocp]]'''.
|notes_en = This defines the language used for {{Attr|name}} and {{Attr|description}}. Examples for the usage of {{Attr|xml:lang}} in {{{selfLink|<additionalName>}}} elements can be found in '''[[IS:additionalName_ocp#Best_practice_.26_Examples_.2F_Empfohlene_Anwendung_.26_Beispiele_.2F_Bonnes_pratiques_.26_exemples|the Best practice section of IS:additionalName ocp]]'''.}}
|notes_de =
}}


{{AddAnn|{{{attributes_en|}}}|{{{attributes_de|}}} }}
{{AddAnn|{{{attributes_en|}}}|{{{attributes_de|}}} }}

Revision as of 18:04, 27 May 2019

Usage

This is an Element Template. Element templates are intended to avoid routine work in railML® element documentation. These templates are very specific and are therefore documented uniformely by Template:TemplateDocu. They are collected in Category:Element Template and are based on Template:ElementDocu. They represent Template:ElementDoku with specific values and hand all other parameters through to Template:ElementDoku. If you want to use or handle an Element Template, you have to examine the code to find out, which arguments are set, and you have to be careful, because occationally arguments will be renamed, so that the use of argument names of Template ElementDoku may cause errors.

Arguments

As this is a bulk documentation, we do not explain the specific arguments of element templates.

Dependencies

As this is a bulk documentation, we do not explain the specific dependencies of element templates. You can find out, which other templates the current template supports by following this link. You can find out easily, which other templates the current template employs, as templates are included via {{doubble braces}}.

Example

As this is a bulk documentation, we do not offer specific examples of element templates. You can find in the field examples by following this link.