[tei-council] <licence>

[Martin Holmes]

On 11-08-22 04:02 AM, 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.

I'm coming round to this view. If someone, for instance, had written 
their own idiosyncratic licence, which was not reliably available at a 
specific URL, they would need to include the whole text of it; so I 
think <p> and friends should be available inside <licence>.

However, I don't believe that we should be making <licence> available 
inside <p>; that would make it available almost anywhere in the 
document, which will inevitably lead to its appearing in unexpected 
places, and make automated processing of it less practical.

Cheers,
Martin

>
> 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
>>
>

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