On Wednesday, September 21, 2005, at 11:43  PM, James M Snell wrote:
<feed xmlns:i="urn:ranking">
<i:domain>{domain}</i:domain>
I was thinking yesterday of suggesting that feed/id be used the way you're using i:domain. Which is better is probably a matter of whether ranking domains that span multiple feeds will be useful or not. In the movie ratings use case presented below, perhaps rather than a fivestarts scheme and netflix and amazon domains, it might make more sense to do this:

<feed>
<id>urn:my_reviews</id>
<i:order scheme="urn:netflix.com/reviews" label="Netflix rating">descending</i:order> <i:order scheme="urn:amazon.com/reviews" label="Amazon rating">descending</i:order>
<entry>
<id>Movie A</id>
<i:rank scheme="urn:netflix.com/reviews">3</i:rank>
<i:rank scheme="urn:amazon.com/reviews">4</i:rank>
</entry>
<entry>
<id>Movie B</id>
<i:rank scheme="urn:netflix.com/reviews">2</i:rank>
<i:rank scheme="urn:amazon.com/reviews">1</i:rank>
</entry>
</feed>

Notes:
* The i:order element tells the user agent whether higher or lower numbers are considered "better", "higher priority", "first", or whatever. In these cases, higher numbers are better, so would typicially be shown first, so they're considered a "descending" schemes. * i:order/@label indicates a human readable label for the scheme, and could be optional. * Since the urn:(netflix|amazon).com/reviews schemes are feed independent, it is not necessary to indicate a feed (or "domain") in this case. * For a feed-specific scheme, like natural order, the feed ID would be included like this (so that if these entries were aggregated, it would be clear that the i:order elements were relevant to the source feed, not the aggregate feed):

<feed>
<id>urn:my_feed</id>
<i:order scheme="urn:index">ascending</i:order>
<entry>
<id>urn:my_feed/a</id>
<i:rank scheme="urn:index" feed="urn:my_feed">1</i:rank>
</entry>
<entry>
<id>urn:my_feed/b</id>
<i:rank scheme="urn:index" feed="urn:my_feed">2</i:rank>
</entry>
</feed>

If sticking with i:domain, I'd recommend that you recommend that in cases where a ranking domain does not span multiple feeds, the feed/id value be used for the value of i:domain, and that in all cases, the same care be taken to (attempt to) ensure that i:domain's value is unique to what is intended to be a particular domain.

Reply via email to