[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: I-D ACTION:draft-ietf-atompub-format-09.txt


4.1.1:
    o  atom:feed elements MUST NOT contain more than one atom:image
      element.
Should be "atom:logo".

4.1.2 says: 
   o  atom:entry elements MUST NOT contain more than one atom:link
      element with a rel attribute value of "alternate" that has the
      same combination of type and hreflang attribute values.
4.1.1 says: 
   o  atom:feed elements MUST NOT contain more than one atom:link
      element with a rel attribute value of "alternate" that has the
      same type attribute value.
Should 4.1.1 also mention hreflang?

4.1.2 puts this in a separate bullet, but 4.1.1 does not: 
   o  atom:entry elements MAY contain additional atom:link elements
      beyond those described above.

Nit pick: 4.1.2 says:
o atom:entry elements MUST have exactly one "atom:title" element.

o atom:entry elements MUST contain exactly one atom:updated element.
Do we want to be consistent in saying "contain" i/o "have"?

4.1.3.2 The "src" attribute

atom:content MAY have a "src" attribute, whose value MUST be an IRI
reference [RFC3987]. If the "src" attribute is present, atom:content
MUST be empty. Atom Processors MAY use the IRI to retrieve the
content, and MAY NOT process or present remote content in the same
manner as local content.
It took me a second to realize that MAY NOT means "don't have to" rather than "aren't allowed to". The technical meaning of the terms is perfectly clear, but it's quite different from the usual meaning of those words, and may be misunderstood. It might be better to say "Atom Processors MAY use the IRI to retrieve the content, and MAY process or present remote content in a different manner from local content."

Appendix A. Contributors doesn't appear to have been updated to add more names.