#489 Make teiHeader/@type explicitly map to dc:type by using terms from DCMI

Lou Burnard

Mappings between TEI Header elements and Dublin Core fields have for the most part been stable and well identified for many years. There are however a few cases where we could helpfully provide more guidance, especially as the DCMI concepts are now clearly defined and standardised and even (I believe) mapped to eg DCR concepts.

This is a particularly striking example. We suggest for teiHeader/@type only two possible values "text" and "corpus". It would be more helpful to explicitly refer to http://dublincore.org/documents/dcmi-type-vocabulary/ which proposes and defines "Collection", "Dataset", "Event", etc. We should either simply reference this list from the spec or reproduce it as a suggested vallist.


  • James Cummings

    James Cummings - 2014-05-19

    Assigning to Paul Schaffner to triage and report to council.

  • James Cummings

    James Cummings - 2014-05-19
    • assigned_to: Paul Schaffner
  • Paul Schaffner

    Paul Schaffner - 2014-11-19

    Council at F2F Nov 14 decided that rather than add values to @type on teiHeader, the attribute was no longer needed at all and should be deprecated. Deprecated at revision 13064, and the six examples in the guidelines removed. Files changed: Guidelines/en/CC-LanguageCorpora.xml, Guidelines/en/HD-Header.xml, and Specs/teiHeader.xml.

    Last edit: Paul Schaffner 2014-11-19
  • Paul Schaffner

    Paul Schaffner - 2014-11-19
    • status: open --> closed-fixed
  • Piotr Banski

    Piotr Banski - 2015-04-06

    Most intriguing, this.
    @type on teiHeader helps a lot in any non-primitive system of headers for corpora, whereby we can distinguish between, for example, corpus-level headers and text-level headers.

    See e.g. http://nlp.ipipan.waw.pl/TEI4NKJP/

    Free-standing headers might benefit from being distinguished machine-readably from "regular" headers of any sort.


Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks