TT:dc:source

From railML 2 Wiki
Revision as of 12:44, 5 March 2012 by RailML Superseded Users (talk | contribs) (New template "InheritDCsource" applied)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search


dc:source
 


Schema description / Schemenbeschreibung

Position of dc:source in the XML-Tree / Position von dc:source im XML-Baum

Multiplicity / Anzahl

[1..1]

Semantics / Bedeutung

Dublin Core definition
"A related resource from which the described resource is derived."
Dublin Core description
"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."
railML® semantics
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
  • to identify the writing software in a unique matter,
  • optionally to name the data source (source database or source files)

Attributes of dc:source / Attribute von dc:source

  • xml:lang (introduced with version 2.1): This is a unique identifier of language. It uses basically the language standard IETF BCP 47 (external link) which may be different to ISO 639-1 (external link) or ISO 639-2 (external link). For mapping hints see relation to other standards (external link).
    The usage of xml:lang does not make any sense in the context of a software identification.

Syntactic Constraints / Syntaktische Beschränkungen

The Element <dc:source> may occur several times with different xml:lang attributes.
If independent software tools are needed for creating the resource multiple <dc:source> elements should be used for identifying each component separately.

Best practice & Examples / Empfohlene Anwendung & Beispiele

  <dc:source>SoftTimetables 1.0-4711</dc:source>
  <dc:source>WareInfrastructure 0.9-815</dc:source>

see also railML® recommendation and example for usage of DC elements (external link, 2012-05-23, pdf, German and English, visited on 2018-03-27; by Dirk Bräuer, iRFP Dresden)

Notes / Anmerkungen

None.

Open issues / Offene Punkte/Pendenzen

Not yet described. / Noch nicht beschrieben.