A. Pagaltzis wrote:
>[snip]
> Maybe we can think of other ways to expose this information so
> that it fits the Atom extension model? Are those attributes
> really the only possible approach to this issue?
>
> Regards,
Maybe, but given that WG messed up in not making the link element
formally extensible, it's not likely to be pretty. Also, keep in mind
that the uglier and more complicated the "correct" approach looks, the
more implementors are going to gravitate towards less-than-correct
approaches that meet their immediate needs.
So, with that, let's catalog the options.
a. Status quo. Leave things the way they are in the current draft
with a firm warning to implementors that not all atom impls
will be capable of supporting them.
b. Drop thr:count and thr:when from the spec.
c. Create a new replies extension element
<thr:replies href="..."
type="..."
hreflang="..."
title="..."
count="..."
when="..." />
d. Create a supplemental extension element
d1:
<link rel="replies" href="..." />
<thr:replies ref="..." count="..." when="..." />
Where the ref attribute in <thr:replies /> is a
unique identifier that can be matched to the
resource linked by the replies link. If only a
single replies link is specified, ref can be
omitted. There could be one thr:replies for
each replies link.
d2:
<link rel="replies" href="..." />
<thr:replies count="..." when="..." />
only one thr:replies would be specified regardless
of the number of replies links. count would be
reflective of the total number of known replies
across all links.
Of the options above, I'm fine with (a) and (b) ...in that order
IMHO (c) is not a viable option, (d1) is ugly as hell and (d2)
sacrifices the use case for a cleaner implementation.
Please suggest additional options and/or arguments in-favor/against the
options above.
- James
