[tei-council] namespaces and customization

[Lou Burnard]

On 04/01/12 10:53, Sebastian Rahtz wrote:
>
> On 4 Jan 2012, at 10:49, Sebastian Rahtz wrote:
>
>> I looked at 33.2.1 today, and see that the relevant example is
>>
>> <elementSpec
>>   ident="eg"
>>   module="tagdocs"
>>   mode="change"
>>   ns="http://example.com/ns">
>> <classes mode="change">
>>   <memberOf key="att.typed"/>
>> </classes>
>> </elementSpec>
>
>
>
> this is not, I now understand, doing what it might appear. I claim
> it says that "the element<eg>  which is in the namespace http://example.com/ns
> is to changed". NOT " the element<eg>  is to be changed to appear in the
> namespace http://example.com/ns". Big difference.
>
> Do others agree that this is how that @ns should be read? its now
> I have implemented it at least.
>

Yes, I can see the logic of this, and I think you are probably right. 
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.