Mark Nottingham wrote:
For that matter, if Henry's interpretation were correct, the element
could be
fh:history nonsense=1./archives/archive1.atom/fh:history
And Atom processors would magically know that XML Base applies to the
URI therein. It's the magic that I object to; inferring
On 17 Aug 2005, at 00:14, Mark Nottingham wrote:
On 16/08/2005, at 3:05 PM, Robert Sayre wrote:
I suggested writing the next tag like this:
link type=http://purl.org/syndication/history/1.0/next; href=./
archives/archive1.atom
That's what I would do, too. Not my spec, though. Mainly so I
On Aug 17, 2005, at 4:10 AM, Henry Story wrote:
Yes. I agree the problem also exists for complex extensions. My
question is the following:
How can a parser that parses atom and unknown extensions, know when
to apply the xml base to
an extension element automatically?
It can't.
Anyway
This is excellent news! Finally, we have an openly and formally defined
standard for syndication. Wonderful!
bob wyman
The IESG has approved the following document:
- 'The Atom Syndication Format '
draft-ietf-atompub-format-11.txt as a Proposed Standard
This document is the product of the Atom Publishing Format and Protocol
Working Group.
The IESG contact persons are Scott Hollenbeck and Ted Hardie.
A
http://www.ietf.org/internet-drafts/draft-snell-atompub-feed-expires-00.txt
Example:
entry
...
t:expires xmlns:t=...2005-08-16T12:00:00Z/t:expires
...
/entry
or
entry
...
updated2005-08-16T12:00:00Z/updated
t:max-age2/t:max-age
...
/entry
This is not to be used for caching of
