lou.burnard at retired.ox.ac.uk
Sat Aug 20 13:04:35 EDT 2011
[opening this discussion up to rest of council]
But this is just one example. Do we definitely not envisage anyone
wanting to use this element to wrap round a bunch of text actually
defining a licence rather than citing one?
On 20/08/11 18:01, Sebastian Rahtz wrote:
> On 20 Aug 2011, at 17:47, Lou Burnard wrote:
>> As there hasn't been any past practice, this is not helpful. What we
>> need to decide is whether we think<licence> is a special kind of<p> or
>> whether it's something you'd expect to find inside a<p>. If the former,
>> then the method Sebastian proposes is fine (at the expense of requiring
>> us to define another model class as well). If the latter, we could
>> probably add<licence> to one of the existing phrase level classes.
> the past practice I am thinking of is the choice in some parts of the header between
> _either_ structured data _or_ a set of<p>s. I was thinking of<licence> as "a special kind
> of<p>" in your parlance.
>> I think I was hesitating between the two, which is why I wanted
>> clarification as to what sort of content people would expect to see
>> inside a<licence>.
> I think Martin's example
> <licence target="http://www.nzetc.org/tm/scholarly/tei-NZETC-Help.html#licensing">
> Licence: Creative Commons Attribution-Share Alike 3.0 New Zealand Licence
> actually makes it a special form of<ref>.
> so arguably we add<licence> to model.ptrLike, and change MH's example to have
> wrapper<p>, and we're done
> 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
More information about the tei-council