Template:InheritDClanguage: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[checked revision][checked revision]
No edit summary
(template:external)
Line 8: Line 8:
|DCdefinition = A language of the resource.
|DCdefinition = A language of the resource.


|DCdescription = Recommended best practice is to use a controlled vocabulary such as [http://www.ietf.org/rfc/rfc4646.txt RFC 4646].
|DCdescription = Recommended best practice is to use a controlled vocabulary such as {{external|http://www.ietf.org/rfc/rfc4646.txt|RFC 4646}}.


|railSemantics = This may be used for identifying the default language and/or script of all {{Attr|name}} and {{Attr|description}} attributes in the children elements of {{{contextLink|FIXME}}}.
|railSemantics = This may be used for identifying the default language and/or script of all {{Attr|name}} and {{Attr|description}} attributes in the children elements of {{{contextLink|FIXME}}}.
Line 40: Line 40:
|lang_de = {{{lang_de|}}}
|lang_de = {{{lang_de|}}}


|constraints =  The controlled vocabulary for the element {{{selfLink|FIXME}}} is the same as for the {{Attr|xml:lang}} attributes: [http://tools.ietf.org/html/bcp47 IETF BCP 47]. Just in case a language is being scripted in different ways, or to address a certain script, add the script identifier (see [http://en.wikipedia.org/wiki/ISO_15924 ISO 15924] for the four-letter alphanumeric code) {{{constraints|}}}
|constraints =  The controlled vocabulary for the element {{{selfLink|FIXME}}} is the same as for the {{Attr|xml:lang}} attributes: {{external|http://tools.ietf.org/html/bcp47|IETF BCP 47}}. Just in case a language is being scripted in different ways, or to address a certain script, add the script identifier (see {{external|http://en.wikipedia.org/wiki/ISO_15924|ISO 15924}} for the four-letter alphanumeric code) {{{constraints|}}}


|constraints_de = {{{constraints_de|}}}
|constraints_de = {{{constraints_de|}}}

Revision as of 13:53, 15 January 2018

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.