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

#234 Review possible values for @status on <availability>

AMBER
closed-fixed
nobody
None
5
2011-04-24
2010-08-13
Anonymous
No

At present @status only allows "free" "restricted" or "unknown". It would be more useful (now that they have done the work) to suggest codes corresponding with the range of Creative Commons licences now available, either as possible values for @status [but that breaks compatibility] or by defining a new attribute @licen{sc}e with values such as CCSA CCBYND etc.

Discussion

  • stuart yeates
    stuart yeates
    2010-08-16

    CCSA CCBYND are insufficient for this, since the licenses have both localisations and version numbers. A full URL is the standard way of referring to them

     
  • Lou Burnard
    Lou Burnard
    2010-08-17

    As with other TEI elements, I would expect the content of <availability> to give the fulkl details, including URL, localisation, version etc. The attribute value would just give a quick summary of the basic fact that the text is e.g. CCBY or whatever. If we agree that this is worth doiing.

     
  • Lou Burnard
    Lou Burnard
    2010-09-13

    Proposal is to add an attribute @licence supplying the URL at which the relevant CC or other licence may be found.

     
  • We've been using markup like this:

    <availability status="restricted">
    <p>
    <ref type="license" target="http://creativecommons.org/licenses/by-nc-sa/3.0/">
    <graphic url="http://i.creativecommons.org/l/by-nc-sa/3.0/88x31.png"/>
    Distributed by the University of Oxford under a Creative Commons
    Attribution-NonCommercial-ShareAlike 3.0 Unported License</ref>
    </p>
    </availability>

    which seems to do the job, and is typically verbose hard-to-parse TEI.

    since this request does even have an owner, I think it needs more debate

     
  • Kevin Hawkins
    Kevin Hawkins
    2010-09-13

    @license would be optional, not mandatory, right?

    It's not the TEI way to supply a URL but not provide lots of prose describing what's at that URL in case the target disappears. So it seems we should recommend that a prose description of what's at the URL be included in a <p> inside of <availability>.

    In any case, the Oxford encoding method strikes me as just as processable as @license.

     
  • Lou Burnard
    Lou Burnard
    2011-04-24

    Closing this one, as it has been merged with 3086675. Council meeting in April 2011 resolved both by proposing new licence child element.

     
  • Lou Burnard
    Lou Burnard
    2011-04-24

    • status: open --> closed-fixed