James M Snell wrote:
Or it is generally allowed by the spec but there are a number of subtle
and not-so-subtle issues that could impact interoperability. I
understand the need for simplicity, but I think it is equally important
to educate implementors about the various subtleties inherent in the
spec.
While the subtleties of a wine's bouquet are important to a proper wine
connoisseur, they often are lost on the typical frat student.
I encourage you to either subscribe to, or simply review the recent
posts made to, the feedvalidator-users mailing list:
http://groups.google.com/group/feedvalidator-users
The message that will be produced when dir attributes are encountered
will simply state that this attribute is defined by a draft document and
is therefore subject to change. Not very subtle, but effective...
wouldn't you agree?
A dir attribute with a value of "upside down" will summarily be flagged
as an error. Again, not very subtle, but it will have the desired
result, and will enable future I-D's to define new values without
worrying about adversely affecting existing client's behavior. I will
also note that such values are not allowed by the non-normative RELAX NG
Compact schema either.
- Sam Ruby
