IS:metadata: Difference between revisions
Jump to navigation
Jump to search
| [checked revision] | [checked revision] |
(Created using new template (Vorlage:InheritMetadata)) |
(Expansion) |
||
| Line 1: | Line 1: | ||
{{ | {{ElementDocu| | ||
| | elementName = metadata | ||
| | |||
| | |parent = {{IS:Tag|infrastructure}} | ||
|childs = {{IS:Tag|dc:creator}}, {{IS:Tag|dc:date}}, {{IS:Tag|dc:format}}, {{IS:Tag|dc:identifier}}, {{IS:Tag|dc:language}}, {{IS:Tag|dc:source}}, {{IS:Tag|dc:title}}, {{Intro|2.2}} {{IS:Tag|organizationalUnits}} | |||
|semantics = | |||
The element {{IS:Tag|metadata}} provides a flexible collection of [http://dublincore.org/ Dublin Core metadata] based on {{Attr|xs:any}}.<br/> | |||
{{Intro|2.2}} Furthermore some basic, export specific organizational bindings may be predefined. | |||
|constraints = | |||
The element {{IS:Tag|metadata}} may be ommitted or used once.<br/> | |||
Dublin Core elements (with 'dc:' prefix) may occur in any order and any count. The railML element {{IS:Tag|organizationalUnits}} should come last, or may be omitted. | |||
|example = | |||
see [http://www.irfp.de/download/railml_beispiel_dc.pdf RailML recommendation and example for usage of DC elements (German, English), PDF, 151 kByte] | |||
}} | }} | ||
Revision as of 15:33, 3 January 2017
metadata
Schema description / Schemenbeschreibung
Position of metadata in the XML-Tree / Position von metadata im XML-Baum
- Parent: <infrastructure>
- Children: <dc:creator>, <dc:date>, <dc:format>, <dc:identifier>, <dc:language>, <dc:source>, <dc:title>, (introduced with version 2.2) <organizationalUnits>
Multiplicity / Anzahl
Semantics / Bedeutung
The element <metadata> provides a flexible collection of Dublin Core metadata based on xs:any.
(introduced with version 2.2) Furthermore some basic, export specific organizational bindings may be predefined.
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 (German, English), PDF, 151 kByte
Notes / Anmerkungen
Not yet described. / Noch nicht beschrieben.
Open issues / Offene Punkte/Pendenzen
Not yet described. / Noch nicht beschrieben.