Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#336 soft deprecation of @key

GREEN
closed
Lou Burnard
5
2013-06-21
2011-11-13
Kevin Hawkins
No

Per discussion at TEI Council meeting in Paris in November 2011, we agreed that uses of @key can all be handled by @ref, using ref="urn:<NID>:<NSS>". See RFC 2141 for the syntax of a URN and RFC 3406 for how a project might register a NID and thereby avoid collisions with other URNs.

Council's vision is that we would like to deprecate @key some day but that it's too widely used today to do so. As an interim measure, we will modify the Guidelines to make the point that people should switch to @ref wherever @key is mentioned.

Discussion

1 2 > >> (Page 1 of 2)
  • Kevin Hawkins
    Kevin Hawkins
    2011-11-13

    • assigned_to: nobody --> kshawkin
    • status: open --> pending
     
  • Kevin Hawkins
    Kevin Hawkins
    2011-11-13

    • status: pending --> open
     
  • Kevin Hawkins
    Kevin Hawkins
    2011-11-13

    As an alternative to using a URN with a non-registered NID, you could use ref="<scheme>:<hierarchicalpart>", which would effectively be identical to what's in the original ticket except without "urn:". Need to find someone who better understands these things to know which is better.

     
  • Kevin Hawkins
    Kevin Hawkins
    2011-11-13

    Note that if we decide that URN with a non-registered NID, we should consider revising att.readFrom and section 22.5 (#TDbuild) to recommend inserting "urn:" in front of "tei:" to make it a URN.

     
  • Kevin Hawkins
    Kevin Hawkins
    2011-11-20

    Previous comment should read:

    Note that if we decide to recommend a URN with a non-registered NID as an alternative to a URI with an unregistered scheme (ref="<scheme>:<hierarchicalpart>"), we should consider revising att.readFrom and section 22.5 (#TDbuild) to recommend inserting "urn:" in front of "tei:" to make it a URN.

     
  • Kevin Hawkins
    Kevin Hawkins
    2011-11-20

    Sebastian reported on tei-council on 2011-11-13 that "computer sciency types" at Oxford felt that a URI with a non-registered scheme was slightly less abusive.

     
  • Kevin Hawkins
    Kevin Hawkins
    2011-11-26

    For URI vs. URN, also see FR 2919640.

     
  • Kevin Hawkins
    Kevin Hawkins
    2011-12-04

    Kevin asked Michael Sperberg-McQueen to weigh in, and he wrote by email:

    The people I know who have spoken most eloquently on this topic
    (namely former colleagues at W3C) would all say "Why on earth
    not an http URL, so people who need to find out what the thing
    is can dereference the URI and find some useful information? If
    you are concerned about permanence, why not make it a PURL?"
    I'm not sure if they would have a preference as between the two options
    you mention.

    He also suggested contacting Eric Miller (formerly of OCLC and now of Zepheira).

     
  • James Cummings
    James Cummings
    2012-04-13

    I agree with the original ticket, for soft deprecation of @key.

    I'm less certain about whether we should be recommending URIs vs URNs but lean towards unregulated URIs at the moment.

    -James

     
1 2 > >> (Page 1 of 2)