[tei-council] <licence>

[Martin Holmes]

On 11-08-22 04:14 AM, Sebastian Rahtz wrote:
>
> On 22 Aug 2011, at 12:02, Gabriel Bodard wrote:
>
>> 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.
>
>
> not sure what you are arguing for, then? the choice is
>
>     <availability>
>       <licence target="…">…blah blah .</licence>
>    </availability>
>
> or
>
>     <availability>
>       <p>Blah blah<licence target="…">….</licence></p>
>    </availability>
>
> I am arguing in favour of the latter, and believe it is perfectly amenable
> to entirely automated processing (availability//licence[1])

But doesn't this make <licence> available in all sorts of places we 
hadn't anticipated?

Cheers,
Martin


> --
> Sebastian Rahtz
> Head of Information and Support Group
> Oxford University Computing Services
> 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
>
> Sólo le pido a Dios
> que el futuro no me sea indiferente
>
> _______________________________________________
> tei-council mailing list
> tei-council at lists.village.Virginia.EDU
> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
>
> PLEASE NOTE: postings to this list are publicly archived
>

-- 
Martin Holmes
University of Victoria Humanities Computing and Media Centre
(mholmes at uvic.ca)