an xml:lang
declaration on atom:updated?
Robert Sayre
of the predefined locations, it could be discarded,
because it's outside the Atom model.
Robert Sayre
Tim Bray wrote:
-0
I could live with this, but I think PaceMustUnderstandElement buys 80%
of the benefit with 20% of the cost/apparatus. -Tim
-1. I suspect everyone else giving PaceMustUnderstand -1s will feel the
same.
Robert Sayre
Tim Bray wrote:
-1
I think this issue has been discussed to death and the current
consensus around atom:id and atom:updated will meet users' needs
simply and elegantly. Trying to achieve consensus on a generalized
abstract model of versioning is doomed to failure. -Tim
-1 as well.
Robert
will deal
with it eventually (Safari 2.0 does...) and/or we'll get a playlist type
thing. That's the only way it will work reliably.
Robert Sayre
directly. For example,
SafariRSS parses feeds with an XQuery script. They also store entries
forever, but maybe they don't version feed properties. What happens to
their implementation if a feed intermittently contains these mU
declarations? I'm confused by it.
Robert Sayre
[0] http
want to prohibit them?
I think we should drop that sentence.
Robert Sayre
I never finished this Pace, and it can be considered withdrawn.
Robert Sayre
Antone Roundy wrote:
http://www.intertwingly.net/wiki/pie/PacePropertyDesign
* Simple
The content of the element MUST be CDATA, and have no attributes.
Perhaps character data instead of CDATA would be better
of putting in there is FOAF, but that works just as well as a
child of entry.
I don't think 9.1.1 or 9.1.2 are necessary.
We should also mention what it means to add markup elsewhere. I think we
should allow it, make it mustIgnore, and make its meaning undefined.
Robert Sayre
contributors.
Right, what's the use case? FOAF doesn't need to be contained by
atom:person. Again, I'm not up for banning it, just making it undefined.
Robert Sayre
points at a
web page that vaguely relates to the origin of the feed. That seems ok
to me, in the absence of a better alternate.
Remember folks, this is about feed-level links, not entries. Links in
entries are allowed to be omitted if there's atom:content
(PaceContentOrLink, format-04).
Robert
could work
against it.
Robert Sayre
Henry Story wrote:
On 7 Jan 2005, at 21:56, Robert Sayre wrote:
Henry Story wrote:
The question is exactly how should the interesting discovery that
an Atom document is an RDF document [Ø] be used to fulfill the
charter requirements on extensibility?
Have you figured out a way to deal
of the Atom model?
The arbitrary extension that RDF allows is not what we need--there's a
reason almost no one syndicates complex objects in dc:subject statements.
Robert Sayre
[0] http://www.imc.org/atom-syntax/mail-archive/msg11935.html
[1] http://www.imc.org/atom-syntax/mail-archive/msg11936
501 - 514 of 514 matches
Mail list logo
