This is not a bug, but a small change in the P5 schema. xml:space is no longer
predefined as a component of att.global -- This was a late decision following
some debate in the TEI Council as to whether anyone was actually using
xml:space. You should be able to add it using Roma (your previous customization
would have assumed that it was already there)


In message <000001c826d5$52ea8590$9b64a8c0@DFCWORKSTATION>
<stephen@dataformat.com> writes:
> Hello,
> 
>  
> 
> I am wondering if the Oct. 27 release of Roma has changed how classSpec is
> read, since a customization that worked for me prior to that date now seems
> to not work. I wish to have @xml:space included in att.global (changing the
> default value to 'preserve'), and have the customization defined as:
> 
>  
> 
> . . .
> 
>                 <classSpec module="tei" xml:id="GLOBAL" type="atts"
> ident="att.global" mode="change">
> 
>                     <desc>provides a set of attributes common to all
> elements in the <name>tei_drama</name>
> 
>                         customization of the TEI encoding scheme.</desc>
> 
>                     <classes>
> 
>                         <memberOf key="att.global.linking"/>
> 
>                         <memberOf key="att.global.analytic"/>
> 
>                     </classes>
> 
>                     <attList>
> 
>                         <attDef ident="xml:space" usage="opt" mode="change">
> 
>                             <defaultVal>preserve</defaultVal>
> 
>                         </attDef>
> 
>                         <attDef ident="xml:base" usage="opt" mode="delete"/>
> 
>                     </attList>
> 
>                 </classSpec>
> 
> . . .
> 
>  
> 
> Previous to the Oct. 27 release, when this customization (attached) was
> loaded into Roma, and a W3C schema generated, the attributeGroup
> att.global.attribute.xmlspace would be defined, and referenced by extensions
> that included global attributes. Now, the att.global.attribute.xmlspace
> attributeGroup does not appear in the generated schema, and is not reference
> by those extensions. Nothing has changed in the customization.
> 
>  
> 
> Is this a bug in the current release? Or is there something I have done
> wrong?
> 
>  
> 
> Thanks for looking at this, and point me to another source if this is the
> incorrect place to make such a query.
> 
>  
> 
> Regards,
> 
> Stephen
> 
>  
> 
> Stephen Perkins
> 
> dataformat.com, LLC
> 
>  
> 
>  
> 
>  
>