APP should use the values as registered. That is, previous, next,
first, last and current. No need to modify the registrations.
Scott Hollenbeck wrote:
-----Original Message-----
From: Andreas Sewe [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 25, 2006 11:37 AM
To: Atom Publishing Protocol
Cc: Atom Syntax
Subject: Re: [Fwd: Approval of Atom LinkRelations Attribute
Value Registrations]
Regarding the following four link relations there seem to be some
inconsistencies with (or maybe only within) the APP 0.7 draft (but
hopefully the editors of 0.8 have caught those already ;-):
Attribute Value: previous
Attribute Value: next
Attribute Value: first
Attribute Value: last
In section 9.1 of draft-ietf-atompub-protocol-07 it is first
stated that
an '[..] Atom feed document MAY contain link elements with "rel"
attribute values of "next", "previous", "start" and "end"
[...]'. There
is a mismatch between the last two values and the ones proposed for
registration: "first" and "last".
Two paragraphs further down section 9.1 starts using "prev"
throughout
-- instead of "previous", as proposed to the IANA.
These inconsistencies should be resolved, IMHO, ideally by
using "prev",
"next", "start", and "end", since at least the first three
values mimic
their functionally similar HTML counterparts. And APP should
follow the
rule of least astonishment here.
There's one minor problem with the suggestion above: the IESG just approved
the registration requests for "previous", "first", and "last" that were
supposedly discussed and agreed-to within the working group. That decision
can be revisited, but if you all decide to make a change the IESG will have
to remove or otherwise obsolete the just-approved values. You'll then need
to go through the approval process again.
-Scott-