[tei-council] Implementing att.sortable

Sebastian Rahtz sebastian.rahtz at oucs.ox.ac.uk
Sun Nov 6 08:04:33 EST 2011

On 6 Nov 2011, at 12:54, Martin Holmes wrote:

> Q1: Is it possible to make a model a member of an attribute class?

No. This dual-purpose modelling used to exist in old ODD, but
we explicitly broke the connection during the Class War.  Hard
to reconstruct the thinking now, and you could certainly
bring that into a melting pot for ODD^3

> so I 
> concluded that this was not allowed or not implemented, and settled for 
> making each individual elementSpec a member of att.sortable.
I agree, its sub-optimal, but that is what you have to do at present

> Q2: list, listPerson, listxx et al are all members of model.listLike, 
> except for listChange and listRef. listChange, like the other members of 
> model.listLike, can nest; I don't see why it's not a member of 
> model.listLike. Is this just an omission?

perhaps not. do you want listChange to appear all over the shop,
which would be the result? well, possibly, but i don't think its simply
an omission.

> listRef also looks like a 
> candidate, except that it can't nest inside itself. Why can't it, when 
> other lists can?
thats a fair point, for symmettry I suppose it should

Jenkins seems to have liked your changes.

don't order the gesiers at dinner
Stormageddon 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 mailing list