TT:metadata: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[checked revision][checked revision]
(Expansion)
No edit summary
Line 4: Line 4:
|parent = {{TT:Tag|timetable}}
|parent = {{TT:Tag|timetable}}


|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}}, {{Intro|2.2}} {{TT:Tag|organizationalUnits}}
|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}}, {{Intro|2.2}} {{TT:Tag|organizationalUnits}} {{depVers|deprecated with version {{{1}}}}}


|semantics =
|semantics =

Revision as of 10:12, 24 May 2017


metadata
 


Scheme description / Schemenbeschreibung

Position of metadata in the XML-Tree / Position von metadata im XML-Baum

Multiplicity / Anzahl

[1..1]

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.