[tei-council] MD chapter revised: namespace rules

[Laurent Romary]

Hi all,
I have kept track of the discussion fo a while and could not see how  
to enter it... now I have it.
I am completely in line with James on his arguments related to points  
2 and 3. The requirements that adding an attribute too an element  
(especially an existing TEI attribute by the way) should force the  
element to change namespace is slightly too strong.
I am thinking of people who may want to add a simple type attribute  
to an element and would not want to bother about namespaces though.
Laurent

Le 10 avr. 07 à 14:13, James Cummings a écrit :

> Lou Burnard wrote:
>> 2. If new attributes are added to a TEI element, the resulting  
>> element
>> must be moved out of the TEI namespace.
>
> I'm not convinced by that.  If I add a new attribute to a TEI  
> element, the
> TEI element is still a TEI element.  It just has a new attribute  
> and that
> attribute is signalled as not being part of the TEI by itself being  
> in a
> different namespace.  my:newAtt="foo".  I don't see that the  
> element is now
> so changed that it is no longer the TEI element.
>
>> 3. Only modified elements which have undergone a clean  
>> modification [1]
>> may remain in the TEI namespace.
>
> Agreed, but I think adding an attribute which is in a different  
> namespace
> is a clean modification.  You are right that changed content  
> models, etc.
> are dirty changes.  However, if the change is to remove an element  
> from
> some classes, or limit an open attribute value list, or anything  
> similar
> which constrains it, then that is a clean modification because the TEI
> content still validates against tei_all.