I'm sorry for the long delay in replying, but I've been swamped with work
lately.
James M Snell wrote:
1. It helps us to scope the relevance of an i:rank element within an
entry. For instance, if an entry with an i:rank in the urn:foo domain is
aggregated into a synthetic feed that either a) does not specify a
ranking domain or b) specifies a different ranking domain, consumers can
safely ignore the urn:foo i:rank.
i:domain is not used as a key of determining which rankings to use; it's a
key that is used to correlate rankings.
The correlating part I get - I think that's a great idea. It's part 1
(quoted above) that I don't understand. You explicitly say a consumer can
safely ignore the rank based on what domain it sees in a feed. How is that
not a determination of which rankings to use?
Regarding filtering, we should not rely on aggregators filtering out
unused ranks. Consider the case of digitally signed entries; filtering
out a rank covered by the digital signature would invalidate the
signature.
I haven't been following the digital signature proposals, but I would have
expected they would attempt to sign a particular content entry rather than
trying to include all the metadata that went with it. Is it really safe to
assume that an item aggregated into a synthetic feed or one that has passed
through a caching/forwarding system will not have had metadata tags added,
removed or reordered? I guess this is offtopic though and I see your point.
There are couple of problems though. The atom:updated element has to be
identical for all items on a particular day. Also the atom:updated
element can't be changed when an actual update occurs (say a spelling
correction, or an update on a story) without breaking the ordering. The
problem is we're abusing the atom:updated element so as to use it for
something that's it's not.
The updated elements would not need to be identical. Aggregators can
easily determine whether or not entries with different updated values
occured on the same day / same hour / etc. In other words, I could sort
by Day+Priority, Hour+Priority, Minute+Priority, whatever, without any
difficulty. There is no abuse of atom:updated here.
The problem is knowing what to sort on. Unless you provide that information
somewhere in the feed there's no way for the aggregator to perform the sort
automatically. Say BBC updates its ranks every 6 hours, how is the
aggregator to know that it should sort by halfday+priority? Or maybe it
updates at 8am and 2pm every day - how would an aggregator deal with that?
With my proposal they would set rank-date to 8am (of the current day) for
every item updated between 8am and 2pm. And items updated from 2pm to 8am
the following day would have a rank-date of 2pm. The aggregator sorts on
rankdate+priority and it all just lines up automatically. No guessing
required.
I'll give this some thought, but my initial gut reaction is that it is not
necessary. Let me see if I can convince myself otherwise ;-)
You could be right. It's not exactly a critical need. I just thought it
wouldn't harm at least having it there as an option for those people that
might want that level of control.
Regards
James