Domel wrote:
Perhaps I should have been more specific. What is the use case of styling Atom?
Some people styling feeds. OK, I don't think everybody must styling Atom but when somebody want why not?
Yeah why not? That does not have anything to do with Atom mentioning the xml:id attribute though. Authors can include it themselves if desired. xml:base and xml:lang solve specific Atom problems, xml:id doesn't do that. (Atom uses something else to uniquely identify each entry. It also couldn't reuse xml:id for this by the way.)
Also, what is the use case for this. What should it actually when given to a feed reader.
I meant: "What should it actually [do] when given to a feed reader".
I don't agree.
I'm not sure how you can't agree when I didn't even make a statement.
XPointers give a lot of advantages to feed reader (framework to navigation and other "going" to some part, it allow display field which will be define). It has also advantages to linking to Atom.
So are you saying XPointer should be part of the Atom specification as well..?
OK, another example: 3. DOM tree - getElementByID
Again, what is the use case for Atom?
Atom is a XML application and majority of XML application define id attribute.
Because they need an ID attribute, Atom doesn't.
XML also refer to ID attribute. xml:id is like predefined atributtes should support it. http://www.w3.org/2001/xml.xsd
That does not mean Atom has to include a reference to it in the specification and depend on xml:id to become a rec.
-- Anne van Kesteren <http://annevankesteren.nl/>
