[tei-council] namespaces and customization
lou.burnard at retired.ox.ac.uk
Thu Jan 5 14:44:30 EST 2012
On 04/01/12 12:08, Sebastian Rahtz wrote:
> On 4 Jan 2012, at 11:16, Lou Burnard wrote:
>> However, it leaves us with an outstanding requirement: how do I say
>> "this new element in this name space is cloned from an existing TEI
>> element but has these modifications"? This is not an unreasonable
>> requirement. We could say "tough, you have to copy the existing spec and
>> tweak it" but that won't win us any friends.
> ah, now if we had a requirements document for ODD,
> we'd be in a lot stronger position.
I dont think you need much of a reqts doc to understand that people
might reasonably want to use the TEI class system in this way
But lets make what we've got now
> internally consistent. If you agree with my interpretation of elementSpec/@ns,
> then the Gidlines example is very very misleading (not _wrong_, exactly...)
Agree on that. But it *is* misleading -- unless you now also claim that
the flopsy example (in #MDNS) is wrong, we have a situation where @ns
means one thing when @mode="add" and another, quite different, thing
when it doesnt.
> which of us wrote that passage which confused Kevin? it talks
> about how to add an element to att.typed as an example, but
> fails to point out that this makes the doc non-TEI (or so some
> of us claim).
Who knows. Probably me, sigh, but I bet you had a hand in it too.
More information about the tei-council