> > Also, for the record, I should express again my preference for using > attributes rather than elements for at least the primary fields. If you need > justification: > > 1. It's a more compact representation, which helps counter the arguments of > people that think tombstones shouldn't be clogging up a regular feed or > should require clients to issue special headers requesting them. > 2. It requires less state information to parse (other client developers may > disagree, but this makes a significant difference to me). > 3. I suspect people are a lot more likely to get your field names wrong when > using elements rather than attributes (using "author" instead of "by", > "updated" instead of "when"), especially now that you're proposing putting > this in the Atom namespace.
I would argue that attributes block internationalization (e.g., ruby, gaiji, and bidi), since attribute values cannot contain subordinate elements or attributes. Cheers, -- MURATA Makoto (FAMILY Given) <[EMAIL PROTECTED]>
