TT:metadata: Difference between revisions
Jump to navigation
Jump to search
[checked revision] | [unchecked revision] |
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
{{ElementDocu| | {{ElementDocu| | ||
elementName = metadata | elementName = metadata | ||
Line 6: | Line 7: | ||
|childs = {{TT:Tag|dc:creator}}, {{TT:Tag|dc:date}}, {{TT:Tag|dc:format}}, {{TT:Tag|dc:identifier}}, {{TT:Tag|dc:language}}, {{TT:Tag|dc:source}}, {{TT:Tag|dc:title}} | |childs = {{TT:Tag|dc:creator}}, {{TT:Tag|dc:date}}, {{TT:Tag|dc:format}}, {{TT:Tag|dc:identifier}}, {{TT:Tag|dc:language}}, {{TT:Tag|dc:source}}, {{TT:Tag|dc:title}} | ||
|semantics = | |semantics = | ||
The element {{TT:Tag|metadata}} provides a flexible collection of {{external| | The element {{TT:Tag|metadata}} provides a flexible collection of {{external|https://dublincore.org|Dublin Core metadata}} based on {{Attr|xs:any}}. | ||
|constraints = | |constraints = | ||
The element {{TT:Tag|metadata}} may be ommitted or used once.<br/> | The element {{TT:Tag|metadata}} may be ommitted or used once.<br/> | ||
Line 12: | Line 13: | ||
|example = | |example = | ||
see {{external| | see {{external|https://www.irfp.de/download/railml_beispiel_dc.pdf|{{rml}} recommendation and example for usage of DC elements|type=pdf|comment=by Dirk Bräuer, iRFP Dresden|lang=German and English|date=2015-05-08|visited=2018-03-27}} | ||
}} | }} |
Revision as of 17:24, 15 February 2021
metadata
Scheme description / Schemenbeschreibung
Position of metadata in the XML-Tree / Position von metadata im XML-Baum
- Parent: <timetable>
- Children: <dc:creator>, <dc:date>, <dc:format>, <dc:identifier>, <dc:language>, <dc:source>, <dc:title>
Multiplicity / Anzahl
Semantics / Bedeutung
The element <metadata> provides a flexible collection of Dublin Core metadata (external link) based on xs:any.
Attributes of metadata / Attribute von metadata
Not yet described. / Noch nicht beschrieben.
Syntactic Constraints / Syntaktische Beschränkungen
The element <metadata> may be ommitted or used once.
Dublin Core elements (with 'dc:' prefix) may occur in any order and any count. The railML element <organizationalUnits> should come last, or may be omitted.
Best practice & Examples / Empfohlene Anwendung & Beispiele
see railML® recommendation and example for usage of DC elements (external link, 2015-05-08, pdf, German and English, visited on 2018-03-27; by Dirk Bräuer, iRFP Dresden)
Notes / Anmerkungen
Not yet described. / Noch nicht beschrieben.
Open issues / Offene Punkte/Pendenzen
Not yet described. / Noch nicht beschrieben.