[tei-council] Deleting an attribute from its class, but reinstating it on an element

[Sebastian Rahtz]

On 27 Feb 2014, at 13:21, Lou Burnard <lou.burnard at retired.ox.ac.uk> wrote:
>> 
>>> The reason <attRef> is not very well documented is that neither
>>> Sebastian nor I can ever remember what it's actually for.
>>> 
>> It is used extensively internally to get at components of attribute classes.
> 
> Fine, but I  have to point to the oxymoron of "extensively internally" -- unless I missed it, we are still waiting for a definitive statement about the "internal" behaviour of an ODD processor.

ok, think instead that <attRef> is used extensively if you save the results of an ODD customisation as a new ODD, for chaining purposes.

> Can we think of a user-facing application for <attRef> ? <elementRef> is a useful way of pulling  elements into a schema irrespective of their class membership,

no, thats not true. irrespective of their _module_ membership. very different thing!

> but I don't think the same trick will work for <attRef>.

why not? thats kind of what it does. whether <attRef> should trigger an implicit <classRef>, I am unsure. is that what you
are suggesting?

How was your ODD class in France?

--
Sebastian Rahtz      
Director (Research) of Academic IT
University of Oxford IT Services
13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431

Não sou nada.
Nunca serei nada.
Não posso querer ser nada.
À parte isso, tenho em mim todos os sonhos do mundo.