[tei-council] @xml:space, whitespace and http://purl.org/tei/bug/3600991

[Martin Holmes]

The text reflects my own understanding of the situation (although I'm as 
cautious as Sebastian with regard to whether I do understand it or not). 
One bit caught my attention, though:

"Treating a structured element as a mixed-content one, or vice versa, 
should be done with care. If it is done, the schema should be customized 
to record the fact."

How would one customize the schema to do this? I can see that you could 
use @xml:space="preserve" to specify that an element with element-only 
content has significant whitespace, but that's in the encoding itself, 
not the schema; and I don't see how you can specify the reverse (since 
"default" won't do it). The text also explains how you can use 
<encodingDesc> to document such things. But I'm not sure how you could 
do it in the schema.

Other than that, I think it's great.

Cheers,
Martin

On 13-01-16 04:30 AM, James Cummings wrote:
>
> Hi there,
>
> John McCaskey believes we introduced new errors and confusion by
> our attempt to clarify the use of the @xml:space attribute and so
> re-opened a ticket about it.  I suggested he rewrite the copy to
> what he believed would express the truth and Sebastian and I have
> both looked at it.
>
> http://purl.org/tei/bug/3600991
>
> Since this is a textual (non-schema affecting) change, could
> Council look at this ASAP and see if you think it represents the
> truth of what we believe @xml:space to do?  A lot of this seems
> to originate from vagueness in the original specification and
> different tool implementations.
>
>
> -James
>
>
>

-- 
Martin Holmes
mholmes at uvic.ca
UVic Humanities Computing and Media Centre