On the other hand, the original plan was to publish both specs at
the same time, which I still think is a good idea.
Do we think there will be any dependencies in the other direction?
That is, when we work on the protocol, will we need to add things
to feed or entry? If there is a reasonable chance of that, then
Atom 1.0 is a temporary thing, and Atom 1.1 will be the real one.
If that is the case, we should leave in the dependency and
publish them together.
wunder
--On Tuesday, February 01, 2005 09:40:38 PM -0800 Paul Hoffman <[EMAIL
PROTECTED]> wrote:
At 10:05 PM +0100 2/1/05, Julian Reschke wrote:
As far as I understand the IETF publication process, this means that
draft-ietf-atompub-format can't be published until the protocol spec
is ready as well.
Others have said we can and should remove the dependency, which is fine.
Wearing my nitpicky-IETF-geek hat, I would point out that specs with dangling
dependencies can be made standards without clearing the dependencies; they
simply can't be published as RFCs with them. There are dozens (possibly over a
hundred) IETF standards-track documents that have not yet been published as
RFCs for a variety of reasons, many of them quite lame.
--Paul Hoffman, Director
--Internet Mail Consortium
--
Walter Underwood
Principal Architect
Verity Ultraseek
