Accessing "Editor's Choice" field from RDF dumps

Hi,

I noticed that some of the listings on the dmoz site have a little "star" next to them - check http://search.dmoz.org/cgi-bin/search?search=yahoo for an example. Is this data (whether a specific title/description listing is marked as "editor's choice" or not) available in the RDF dumps?

Any guidance is appreciated!

Thanks!

See http://rdf.dmoz.org/rdf/tags.html

The content elements ending with the digit 1 are the cool-marked sites. That is link1, pdf1 and rss1.

Be careful about reading it as "editors choice". Often the implied message is "official site" about the topic of the category, like a city, author or whatever.

Does that imply that this value is tied to the url and not the title/description. Put another way, is it accurate to say that if a specific url (say www.yahoo.com) is listed under multiple categories and has several titles/descriptions depending on category, either ALL of those listings will be "cool-marked" or NONE of them will be "cool-marked"?

Thanks.

This may help explain cool sites better: http://dmoz.org/guidelines/describing.html#cool

The cooling of the URL is based on the value it brings to the category it is listed. Which is why it is typically only used on "official" sites. It has nothing to do with the title/description or how they are written (if I understood the question correctly ) it only means that the editor felt that the site was the most definitive in its category.

<add>The "cooling" only applies (as far as I know) to the category in which the site was "cooled".</add>

So hopefully that helps, explain it.

Does that imply that this value is tied to the url and not the title/description.

Click to expand...

Neither. It is tied to the combination of URL and category. Basically, it can be understood as an extention of the title/description. Or... shadow575 is right

In other words, the "<link r:resource=" and matching "<ExternalPage about=" elements are "local" to the block of elements started by each "<Topic r:id=", representing listings in one category. As you can see, a tree-based parsing of the content file cannot work properly.