conceptual hierarchy (even if it's a single- level hierarchy). • The aim is to make it easy for consumers to discover and use your data, which rich descriptions and links make possible. Implications
the canonical item URIs at close to the top level as is reasonable. • You might wish to think about organising these hierarchies around conceptual classes: e.g., /articles, /books, /places.
which describe the sets. • Include information about URI patterns, endpoints, and links to example resources and subsets. • The document is the dataset: e.g., /items is an instance of void:Dataset. Implications
at your site root and at /.well-‐known/void. • Within your sets, include descriptions of your text search and SPARQL endpoints, if you have them. • Describe any data dumps that you make available. • Arrange your sets so that clients can traverse them and retrieve their contents. Implications
each of the items within the set using rdfs:seeAlso. • To paginate, link to the first, next, previous and last pages in the set using the XHV terms (e.g., xhv:first). • Order your data by most-recently-modified first to prioritise updates when consumers iterate the set.
to them with void:DataDump. • Include a description of the dump (the target of that link) detailing the creation/ modification dates and MIME type of the dump resource.
single-file RDF/XML (amongst other formats). • Within .zip files, put an RDF/XML file named index.rdf at the root which describes the resources in the dump using relative paths.
them using void:classPartition and void:class if you can. • Otherwise, use void:subset to reference them. • In subsets, link back to the parent using void:inDataSet.
the items in the sets which contain them. • There’s little sense in including all of the information about something — consider what you would typically present in a browsing interface. Implications
in the dataset descriptions. • Publish rights information for both the data in the documents and (where applicable) the things described by those documents. • The DMCI Metadata Terms schema includes predicates to aid this, and for many sets the Creative Commons ontology may also be useful.
of linked and linkable data. • Don’t assume all consumers will want to only use your data, nor ingest it all into their own triple-stores in order to process or run queries upon it. Implications
really useful features which enable a variety of interesting applications and they’re worth providing if you can — but not at the cost of data you can link to.
• http://vocab.deri.ie/void/autodiscovery • VoID Autodiscovery via a RFC5785 .well-‐known resource. • http://purl.org/NET/mediatypes • Linked data for MIME types (for use with dct:format)
nevali
masaru_b_cl
3110
taokiuhuru
.jpg){kind=avatar}
kotomin_m
stefafafan
zilmina
bicstone
sksat
n0bisuke2
watany
contents
isaka1022
marcelosomers
bryan
reverentgeek
michaelherold
3n
holman
kevinliebholz
samlambert
swwweet
jacobian
keithpitt
brad_frost
