On 15-02-06 08:42 AM, Sebastian Rahtz wrote:
>> On 6 Feb 2015, at 16:33, Martin Holmes <[log in to unmask]> wrote:
>> Thanks indeed for this, Louis. I had no idea this would work; I always think of attribute specification as being entirely separate from content specification, and resort to Schematron for this sort of thing.
>> Now the obvious question is: is this possible in PureODD, and if not, should it be, and how?
> it’s an interesting question. TEI has always kept a distinction between attributes and element content,
> so the PureODD stuff hasn’t gone back to examine attributes enough.
> I’d be interested to hear if anyone else wants this form of power in their attributes. Personally, I think
> its angels dancing on pinheads :-}
Actually, I would love this, and I'd use it all the time; imagine
different content models for different types of <bibl> entry, for
instance, or different datatypes for different types of <geo>. But it's
perfectly straightforward to do it with Schematron, and there are so
many other things you can do with Schematron that are close to this but
not the same (different content constraints depending on the parent
element, for instance), so I think it makes more sense to do it with
> Sebastian Rahtz
> Chief Data Architect
> University of Oxford IT Services
> 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431