Re: new issues in draft -06, was: Updated issues list

[Robert Sayre]

Thanks for the close reading. Comments inline.
Julian Reschke wrote:
This has been mentioned before...: as far as I can tell, it's far easier 
for recipients to process "xhtml" compared to "html" (no tag-soup parser 
needed), thus *any* kind of change that encourages "xhtml" would be 
appreciated.
I've heard client and server implementors take every possible position 
on the matter. I'm not sure why this issue must be raised over and over.

06-C02, 3.1.1 "type" Attribute
<http://atompub.org/2005/03/12/draft-ietf-atompub-format-06.html#rfc.section.3.1.1> 

Here's a question. Is this...:
<summary type="html">
  overlapping &lt;b>markup &lt;>is&lt;/b> bad&lt;/i>.
</summary>
legal Atom? As far as I can tell, here we have a SHOULD level 
requirement to only transport well-formed HTML4 content, right?

Seems like overspecification to me. What's the benefit of going into 
detail here?

06-C03, 3.3 Date Constructs
<http://atompub.org/2005/03/12/draft-ietf-atompub-format-06.html#rfc.section.3.3> 

As others have pointed out, the regexp is incorrect ("-" characters in 
full-date part are missing). Also, I'm not sure whether it requires the 
timezone information; if it doesn't, this isn't what RFC3339 defines. In 
general, I find RFC3339 much easier to read:

Noted.


06-E01, 1.2 Example
<http://atompub.org/2005/03/12/draft-ietf-atompub-format-06.html#rfc.section.1.2> 

Is it intentional that the example is inconsistently indented?
Noted. A shorter namespace would help.


06-E02, 1.3 Notational Conventions
<http://atompub.org/2005/03/12/draft-ietf-atompub-format-06.html#rfc.section.1.3> 

...speaks about namespace prefixe*s* being defined; but then only 
defines a single one.
noted.


06-E03, 5.1 Digital Signatures
<http://atompub.org/2005/03/12/draft-ietf-atompub-format-06.html#rfc.section.5.1> 

s/namespace IRI/namespace URI/ (or "namespace name")
namespace URI, I think.


06-E04, 6.2 Extensions To the Atom Vocabulary
<http://atompub.org/2005/03/12/draft-ietf-atompub-format-06.html#rfc.section.6.2> 

--snip--
considered "foreign "markup".
--snip--
(quoting).
noted.


06-E05, 8.1 HTML and XHTML Content
<http://atompub.org/2005/03/12/draft-ietf-atompub-format-06.html#rfc.section.8.1> 

"See the security sections of RFC 2854 and HTML 4.01 for guidance."
(use proper references)
Will do.
Robert Sayre