RE: AI-46: Make an explanation of the BP 24 issue

I think this is a lot clearer now, in the Why do this section. I'm still
worried about the title and blue text, though.  It also seems to me that the
issue only really arises when you are including markup in *a different*
format (ie. namespace) into your (container) format.  Otherwise you wouldn't
have to escape anything, right?  (Although, i suppose that theoretically
this could relate to fragments of markup in the same namespace if they
weren't normally allowed in that particular location.)

So I'm wondering whether we can use the following:


Best Practice 24: Storing included markup from another format

Avoid escaping markup to enable inclusion of markup.



I think, btw, that I came across another example of this while reading the
Atom spec this week.  In Atom, HTML has to be stored in escaped form, eg.

<?xml version="1.0" encoding="utf-8"?>
   <feed xmlns="http://www.w3.org/2005/Atom">
     <title type="text">dive into mark</title>
     <subtitle type="html">
       A &lt;em&gt;lot&lt;/em&gt; of effort
       went into making this effortless
     </subtitle>
     <updated>2005-07-31T12:29:29Z</updated>
	...
   </feed>

Seems we missed the boat for that one though.

RI



============
Richard Ishida
Internationalization Lead
W3C (World Wide Web Consortium)
 
http://www.w3.org/International/
http://rishida.net/blog/
http://rishida.net/

 
 

> -----Original Message-----
> From: public-i18n-its-request@w3.org 
> [mailto:public-i18n-its-request@w3.org] On Behalf Of Martin Duerst
> Sent: 06 December 2007 04:31
> To: Yves Savourel; public-i18n-its@w3.org
> Subject: Re: AI-46: Make an explanation of the BP 24 issue
> 
> 
> At 05:20 07/12/06, Yves Savourel wrote:
> >
> >Hi everyone,
> >
> >Here is a first try for some extra explanations for BP 24:
> >
> >
> >Why do this:
> >
> >Some XML documents are used to store different types of data for the 
> >purpose such as exchange or export. In some cases such data 
> is itself 
> >XML data. For example, some XHTML content stored in a 
> database can be 
> >exported to an XML container file for localization and 
> re-imported back 
> >into the database.
> >
> >Storing such XML data inside XML elements as text content (i.e. with 
> >its markup tags escaped), has several drawbacks:
> >
> >- Any handling of the data is made difficult by the impossibility to 
> >separate text from markup without extra processing.
> >
> >- Often, such content is put in CDATA sections, which has 
> its own set 
> >of issues. See Best Practice 20: Avoiding CDATA sections
> 
> Some more points:
> 
> - If there is a process turning markup into escaping,
>   there is the danger of double escaping.
> 
> - Escaped markup obviously doesn't get checked for well-formedness
>   (or validity).
> 
> I think namespaces should be mentioned, as one possible solution.
> And we should clearly note that the use of escaping for 
> literal examples of markup is an exception to this BP.
> 
> Regards,     Martin.
> 
> 
> #-#-#  Martin J. Du"rst, Assoc. Professor, Aoyama Gakuin University
> #-#-#  http://www.sw.it.aoyama.ac.jp       
> mailto:duerst@it.aoyama.ac.jp     
> 
>

Received on Friday, 21 December 2007 16:58:12 UTC