A tweak suggestion re. the resource:
<http://data.nytimes.com/colbert_stephen_per> that will apply to similar
.rdf resources (the triple containers).
<http://data.nytimes.com/sample/N66220017142656459133.rdf> needs to be
connected to entity/resource descriptions that it hosts.
One pattern (of course there are others) would be:
foaf:primarytopic <http://data.nytimes.com/colbert_stephen_per> .
The above can be expressed via HTML+RDFa or even just as an entry in
<link/>, if adding at source is in any way problematic.
Examples to show implications of not establishing this vital relationship:
1. http://tr.im/EeV4 - Page that attempts to describe the resource
2. http://tr.im/EeUR -- A Browser Page that explores the contents of
Just a quick +1 from me on Kingsley's proposal below: Assuming you have
then it's a nice thing to add the following triple:
</foo.rdf> foaf:primaryTopic </foo> .
This makes it easier for clients that happen to get hold of just the </
foo.rdf> URI to identify the “primary resource” of the file. This
helps browsers and visualizers to show the right stuff to users.
Several linked data browsers (at least OpenLink Data Explorer,
Tabulator and Disco) will deliver better user experience if this
triple is present.
It's a bit unfortunate that the primaryTopic predicate is in the FOAF
namespace -- it really doesn't have anything to do with personal
profiles or social networking, but it somehow has emerged as the quasi-
standard way of doing this.