Robert Sayre wrote: > I realize that text was battled over wrt to accessibility, but I have > some pretty convincing use cases for dropping at least the first one.
At the risk of beating the PaceProfile drum to death, I would think that an Accessibility profile could be used to specify specific requirements for accessible feeds. The core could do exactly as you suggest below -- not require summary.
<?xml ... <entry profile="core"> <title>...</title> <id>...</id> <link ... /> <pub:edit ... /> <updated ... /> </entry>
<?xml ... <entry profile="core accessibility"> <title>...</title> <id>...</id> <summary>...</summary> <link ... /> <pub:edit ... /> <updated ... /> </entry>
The point is that I think removing the requirement for summary to be there when content is not is ok and, in so doing, there are potentially viable mechanisms by which the requirement can be tacked on it situations where it is Very Useful.
- James M Snell
