At 03:33 05/04/29, Alexey Melnikov wrote: >>The file can be obtained via >>http://www.ietf.org/internet-drafts/draft-ietf-atompub-format-08.txt
> >3.1.1.1 Text
> > If the value is "text", the content of the Text construct MUST NOT
> > contain child elements. Such text is intended to be presented to
> > humans in a readable fashion. Thus, Atom Processors MAY collapse
> > white-space (including line-breaks),
>
>Ok, maybe it is just me, but what does it mean to "collapse white-space"? Does this mean to replace FWS (in RFC 2822 sense) with a single space?
Making this more precise is definitely desirable. But there is also an i18n issue: This works fine for languages that use spaces between words. It doesn't work for languages that don't have spaces between words (Chinese, Japanese, Thai,...). If Text elements are only used for short things such as names or titles, that's not a big issue, the text in question can just be put on a single line. However, when the texts in question are long, it's a serious issue, and should be fixed.
> > and display the text using > > typographic techniques such as justification and proportional fonts. > > > >4.1.3.3 Processing Model >... > > 2. If the value of "type" is "html", the content of atom:content > > MUST NOT contain child elements, and SHOULD be suitable for > > handling as HTML [HTML]. The HTML markup must be escaped; for > >Should the "must" be changed to MUST here?
Yes, please!
> >6.3 Software Processing of Foreign Markup
> >
>...
> > When unknown foreign markup is encountered in a Text Contruct or
> > atom:content element, software SHOULD ignore the markup and process
> > any text content of foreign elements as though the surrounding markup
> > were not present.
>
>I reread this paragraph few times and I am still not quite sure what the paragraph is trying to say. Is it trying to say "if the content of a foreign element looks like XML with unrecognized schema - just strip the markup and process the text"?
Reading this, I got confused because we have both "Text Construct" and "Text" as subtitles. I suggest to change the subtitle "Text" to something like "Text Construct with type='text'" or so. Also, starting a section with just an example looks weird. Please add an introductory sentence. Same of course for the parallel subsections.
Regards, Martin.
