Robert Sayre wrote:
What happens when it does contain child elements? I think we should
define that for interoperability. (See HTML for what happens when
you don't.) This question also applies to the next section.
No, that's broken. There can be no expectation of interoperability.
I think there should be. Authors will try to do it anyway and defined
error handling is better than reverse engineering the market leader's
error handling.
For white-space significance text I need to use 'html' or 'xhtml'
instead using PRE or xhtml:pre?
I don't understand what you're saying here, but I'm pretty sure every
possible whitespace issue has been debated by Graham, Paul, Martin,
etc. Feel free to try and explain this again if I don't get it.
White-space may be collapsed inside 'text' as currently defined.
* 4.2.2 The "atom:category" Element
Why is significant information hidden in attributes? That is bad
for i18n and prevents people from defining the expansion of an
abbreviation, for example.
Minor flaw. It happens.
I think you are rushing things too fast. It would be much better if we
fixed this.
* Links
I don't understand why we have so many different link constructs.
<atom:link href="iri"/>, <atom:image>iri</atom:image>,
<atom:uri>iri</atom:uri>, <atom:content src="iri"/>.
Can't we name them consistently? I'd suggest 'href' or 'url'.
('url' is used in CSS and extensions of HTML and XHTML 1 made by
the WHATWG.)
Nope. Too late.
And this.
--
Anne van Kesteren
<http://annevankesteren.nl/>
