[tei-council] <licence>

[Gabriel Bodard]

And it's usual practice (at least with some licenses) to include both a 
pointer to the official license text or code, and some text explaining 
the nature of the license as it applies to the current publication. 
(With a CC-BY-* license, for example, we both point to the CC license 
code, and say to whom or what institution any copy or adaptation of the 
content should be attributed, any exceptions to the license, etc.)

Some license text, of the kind that you might want to reproduce/compose 
in the teiHeader, would naturally be multiparagraph, so my feeling is it 
would be artificial to shoehorn it into a single paragraph-like block.

On 2011-08-20 20:47, James Cummings wrote:
> On 20/08/11 19:07, Martin Holmes wrote:
>> I think you might be wrong; I think its job is to do both (point and
>> contain). Its main function is to provide an easily-identifiable
>> location where a mechanical processor can retrieve the detailed
>> information about the licence(s) to be applied to a document, whether
>> through following @target, or through retrieving the text content of the
>> element (or both).
>
> I think I agree with Martin here. We can have multiple<license>  in a
> single<availability>  right? One might just be a pointer out to a CC
> license as per his example, but one might be a prose statement.  Is that
> prose statement made up of multiple paragraphs or is our assumption that
> it is just the equivalent of a single paragraph?
>
>
>
> -James
>

-- 
Dr Gabriel BODARD
(Research Associate in Digital Epigraphy)

Department of Digital Humanities
King's College London
26-29 Drury Lane
London WC2B 5RL

Email: gabriel.bodard at kcl.ac.uk
Tel: +44 (0)20 7848 1388
Fax: +44 (0)20 7848 2980

http://www.digitalclassicist.org/
http://www.currentepigraphy.org/