#291 @version in examples


There are a very few uses of the @version attribute in the guidelines. If I understand correctly they should be the same and correspond to the current version of the guidelines. They don't, see: http://www.tei-c.org/release/doc/tei-p5-doc/en/html/examples-TEI.html

Since the version number changes every release, maybe a check on this could be added to the release checklist?


  • Sebastian Rahtz

    Sebastian Rahtz - 2011-08-21

    The use of @version is entirely confused and contradictory, I am afraid. The Guidelines source says
    <TEI version="5.0">
    which seems mildly meaningless, compared to the one you cite at http://www.tei-c.org/release/doc/tei-p5-doc/en/html/examples-TEI.html which says <TEI version="1.2.0">
    We also have
    Source/Specs/teiCorpus.xml: <teiCorpus version="5.2">

    But these are only _examples_, so should they be updated automagically?

    All the other uses of @version are dates on translations, I think?

  • Lou Burnard

    Lou Burnard - 2011-08-21

    See lengthy discussion on ticket 2932853.

  • Lou Burnard

    Lou Burnard - 2011-11-02
    • milestone: --> 871212
  • Kevin Hawkins

    Kevin Hawkins - 2012-03-25

    The discussion on this ticket seems to have become an extension of https://sourceforge.net/tracker/?func=detail&aid=2932853&group_id=106328&atid=644062 . That ticket is closed, though I'm not sure why because it appears we never acted upon it. Stuart's comment here indicates to me that that ticket should be re-opened.

    The original ticket was for adding something to the release checklist. It appears that this has already been added to http://www.tei-c.org/Activities/Council/Working/tcw22.xml .

    In his comment, Sebastian points out contradictory practice in the Guidelines. <TEI version="5.0"> and <teiCorpus version="5.2"> should be changed to use the data.version datatype defined for @version on these elements. I'm not so concerned about updating examples that use an old version number all the time.

  • Lou Burnard

    Lou Burnard - 2012-04-18
    • milestone: 871212 --> GREEN
    • assigned_to: nobody --> rahtz
  • Lou Burnard

    Lou Burnard - 2012-04-18

    Agreed to rename @version in att.translatable as @versionDate and give it a date datatype. We dont want all the possibilities of att.datable.

  • Sebastian Rahtz

    Sebastian Rahtz - 2012-04-18

    I have changed @version in att.translatable into @versionDate, with a date datatype; and changed all the *Spec accordingly.

    It seems clear that @version on <TEI> is a different kettle of fish, and refers to the TEI's Proposal number (ie 1, 2, 3, 4 and currently 5). It is not used by anything, and is unrelated to releases of the current Proposal.

  • Sebastian Rahtz

    Sebastian Rahtz - 2012-04-18
    • status: open --> closed-accepted
  • Kevin Hawkins

    Kevin Hawkins - 2012-05-16

    I agree that TEI@version is a different kettle of fish. Still, I disagree with Sebastian's assessment. The example of TEI@version given at http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-TEI.html gives:


    which is not a proposal number. It's not clear to me that TEI@version has been defined so narrowly.

  • stuart yeates

    stuart yeates - 2012-05-16

    I think it would useful to add a note about the correspondence between @version and the directories http://www.tei-c.org/Vault/P5/

  • Sebastian Rahtz

    Sebastian Rahtz - 2012-05-16

    suggests to me that the example for TEI@version should be changed, then ... i still claim this is nothing to do with the numbering as used in the Vault

  • Kevin Hawkins

    Kevin Hawkins - 2012-07-17

    For the record, on 2012-04-18 the definition of TEI@version was revised by Lou to specify that it refers to TEI proposal number, and the example therein was also revised to use


    Therefore the latest three comments on this ticket no longer apply.