On 9 Nov 2004, at 1:57 pm, Paul Hoffman / IMC wrote:
Please list the specific "to be revisited" that you think are important for the core of Atom. If there is agreement in the WG, we will definitely work on them.
A quick glance through the current spec shows:
- atom:updated is currently required. I think this will lead to it being polluted with general "Last Modified" dates, severely limiting its usefulness. Seeing as it is not possible to make an element optional after v1.0, but it is possible to do the reverse, this one seems urgent.
- The discredited atom:id canonicalization nonsense still stands
- The use of terminology is very poor. For example, several elements define whether they can "change" or not. How can a server ever change something after it has been transmitted? What we mean to say is whether or not all instances of an entry should have the same value.
- ditto "permanent, universally unique identifier"
- No discussion on how xml:space applies to content types
- type="TEXT" does not define handling of line breaks
- No discussion on whether whitespace or parameters are allowed in @type
- Section 6 "Managing Feed State" could be a key differentiator between Atom and RSS if it were written rather than dropped
I'll admit to not being familiar with the process. Should the WG have taken a moment to fully vet their spec before asking the rest of the IETF to?
Graham
smime.p7s
Description: S/MIME cryptographic signature
