#157 <idno> coverage


<idno> should be revised to:
- with a note making it explicit that the notion of identifier is not restricted to numbers and that URI, etc. can be put there. Maybe an explicit example with a DOI and/or an ISBN would be great.
- extend its scope so that it can treat unique identifiers for core components of a bibliographical reference, in particular, authors (it should thus be part of the content model of <author> among others


<< < 1 2 (Page 2 of 2)
  • Kevin Hawkins

    Kevin Hawkins - 2011-11-26

    My notes from Chicago meeting say that I was supposed to add examples of uses of <idno> for author identifiers to various places in the Guidelines, but I'm not sure this is an appropriate path forward now that we've been discussing use of @ref to give a URI or URN instead of a @key or <idno>. See http://purl.org/TEI/fr/3437509 and http://www.purl.org/TEI/FR/2919640 .

  • Martin Holmes

    Martin Holmes - 2011-11-26

    I think we need a little subcommittee to work on this whole mess -- <idno>, <ident>, <ref>, and <ptr>. I volunteer. Who else fancies working on this, and having a full proposal to bring to Ann Arbor in April?

  • Kevin Hawkins

    Kevin Hawkins - 2012-05-20

    Per FR 3437509, we are still allowing @key but encouraging use of tag URIs in @ref instead. The long comment below by pboot shows that if you want to associate more than one identifier with an <author> or <editor>, you can't do this with @key or @ref; instead, you need multiple <idno>s inside <author> or <editor>. And <ident> is unrelated. So the documentation on identifiers can be added.

    I've added examples of authors at revision 10377:


    Further suggestions welcome.

  • Kevin Hawkins

    Kevin Hawkins - 2012-05-20
    • status: open-postponed --> closed-fixed
<< < 1 2 (Page 2 of 2)

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

Sign up for the SourceForge newsletter:

No, thanks