Template:InheritDCsource: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[checked revision][checked revision]
No edit summary
(railML→{{rml}})
 
(7 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<includeonly>{{InheritDCelement
<includeonly>{{InheritDCelement
|elementName = dc:source
|elementName = dc:source
Line 10: Line 11:
|DCdescription = The described resource may be derived from the related resource in whole or in part. Recommended best practice is to identify the related resource by means of a string conforming to a formal identification system.
|DCdescription = The described resource may be derived from the related resource in whole or in part. Recommended best practice is to identify the related resource by means of a string conforming to a formal identification system.


|railSemantics = This may be used for identifying the software system which was used for creating the data set (railML file). Additional internal software system version strings may be integrated. It may be used{{ref}}http://www.irfp.de/files/iRFP/Downloads/railml_beispiel_dc.pdf p.15f}}
|railSemantics = This may be used for identifying the software system which was used for creating the data set ({{rml}} file). Additional internal software system version strings may be integrated. It may be used<!--{{ref|iRFP: railml_beispiel_dc.pdf p.15f}}-->
* to identify the writing software in a unique matter,
* to identify the writing software in a unique matter,
* optionally to name the data source (source database or source files)  
* optionally to name the data source (source database or source files)  
Line 33: Line 34:
</syntaxhighlight>
</syntaxhighlight>


see also [http://www.irfp.de/download/railml_beispiel_dc.pdf RailML recommendation and example for usage of DC elements (German, English), PDF, 151 kByte]
see also {{external|https://www.irfp.de/download/railml_beispiel_dc.pdf|{{rml}} recommendation and example for usage of DC elements|type=pdf|lang=German and English|comment=by Dirk Bräuer, iRFP Dresden|visited=2018-03-27|date=2012-05-23}}


|back = {{{back|FIXME}}}
|back = {{{back|FIXME}}}
}}</includeonly><noinclude>{{TemplateDocu}}</noinclude>
}}</includeonly><noinclude>{{TemplateDocu}}</noinclude>

Latest revision as of 21:53, 22 January 2024


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.