[tei-council] MD chapter revised: namespace rules

[Laurent Romary]

I would support the idea to have translated elements in another  
namespace: they really represent a different "vocabulary" and as such  
should not interfere with the reference TEI one.
Laurent

Le 10 avr. 07 à 16:09, Arianna Ciula a écrit :

>
>
> Laurent Romary wrote:
>> 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 agree with these points as well (2 and 3).
> I am not sure what to say about the translated element names  
> though. It probably makes sense to have other TEI namespaces for  
> those for pragmatical reasons as Lou suggested, even if,  
> conceptually, I still think they are a sort of a priori approved  
> renaming and therefore shouldn't be perceived as different from  
> what is in the TEI namespace.
>
> Arianna
>
>> 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.
>> _______________________________________________
>> tei-council mailing list
>> tei-council at lists.village.Virginia.EDU
>> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
>
> -- 
> Dr Arianna Ciula
> Research Associate
> Centre for Computing in the Humanities
> King's College London
> Strand
> London WC2R 2LS (UK)
> Tel: +44 (0)20 78481945
> http://www.kcl.ac.uk/cch
> _______________________________________________
> tei-council mailing list
> tei-council at lists.village.Virginia.EDU
> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council