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 like the new viewpoint, but I'm not sure about 'included/inclusion'
Maybe something like:

Best Practice 24: Storing 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>

Yes. Well, at least they do the next good thing: they indicate the content needs some kind of special process (type="html").

-ys