Antone Roundy a �crit :
If we're going to be using a flavor of XHTML that doesn't support @style, then this example is invalid, but perhaps the concept can be transferred to some other attribute. This example assumes that the XHTML namespace is already bound to the prefix "x":
<content type="XHTML"><x:div style="color:#f00;">Am I red text?</x:div></content>
Should the text be rendered in red or not?
The question is: should the text should be rendered using any publisher-provided style or using the Atom processor's style, or the including web page's style (if I'm publishing someone else's feed on my own website) ?
Is Atom a _news_ syndication format ? And maybe something like NITF/XMLNews-story would be a better choice.
Or is Atom a _web_ syndication format ? And XHTML is a good choice.
Or is Atom a _publication_ format ? And DocBook/XML would be a good choice.
> The div and its style
attribute are not part of the content, so do they have the ability to style the content? When I hand the content off to my XHTML rendering widget, how would I tell it about the red style if I've removed the wrapper div? I haven't worked with such widgets, so for all I know, there may be an obvious answer to that--at least for some widgets. But still, applications are going to have to know more about XHTML than they'd have to know if they could simply discard the wrapper and pass its contents on to their XHTML widget.
...hmm, or maybe we shouldn't have introduced the wrapper and we could simply rollback...
-- Thomas Broyer
