voiD Specification | voiD Guide | About
LiDRC logo

NUIG logo

ve2 - the voiD editor is developed and maintained by Michael Hausenblas at the Linked Data Research Centre, DERI, NUI Galway. It is written with jQuery on the browser-side and PHP on the server and depends on the following (external) services:

The ve2 Web application is powered by the ve2 voiD editor reference implementation as described below, last updated on 2010-01-08.

ve2 is maintained at http://code.google.com/p/void-impl/, release version 0.0 (2010-01-08), The source code is available via the voiD implementation Google code.

In case you have a feature request or want to file a bug, please visit the issue tracker. If you want to discuss general usefulness or other, voiD-related stuff, please post it to the public-lod@w3.org mailing list (and mention ve or ve2 there ;)

Kudos to Richard Cyganiak, Lin Clark, and Jeni Tennison for early feedback and lots of good suggestions how to improve the usability! Further I'd like to thank Keith Alexander for his support re the Talis voiD store and Hugh Glaser as well as Ian Millard for their support re the RKB voiD store.

Valid XHTML + RDFa

ve2 - the voiD editor

Create Inspect Announce
close
URI of the voiD file
announce

The URI of the voiD file you enter will be submitted to the following services: Sindice, the RKB voiD store, the Talis voiD store, and to PingtheSemanticWeb.com.

busy

This is ve2, the voiD editor. It allows you to generate a voiD file in RDF Turtle format. On the left you'll find a collection of forms where you can define the characteristics of your linked dataset, such as categories, interlinking, technical features, licensing and the like. On the right hand, the respective voiD file is generated on-the-fly (or manually, hitting the 'Create' button).

At any time you can inspect your voiD file via the Sindice Web Data inspector using the 'Inspect' button.

Once you have adjusted the voiD file to your needs, put it on your server and you can announce it to the wide world, here as well with the 'Announce' button.

Start ...
Input: dataset characteristics

Define general dataset metadata

Define general metadata about the dataset. For more information see the voiD guide, section 'General Dataset Metadata'.

Dataset URI

You can define a URI for your dataset. If you leave it blank, a default will be used - if the voiD file is deployed at http://example.org/void.ttl the dataset URI is http://example.org/void.ttl#myDS.

Dataset Homepage URI

Define your dataset by specifying its homepage. The homepage of the dataset is a dedicated document that talks about the dataset.

Dataset Name
Dataset Description
+ Example Resource
validate

Select topics

Select one or more topics your dataset talks about. In general, we use DBpedia resources in voiD to unambiguously represent the topic. For more information see the voiD guide, section 'Categorise Datasets'.

Dataset Topic
x

The term you enter will be used to perform a look-up in DBpedia, resulting in a list of potential URIs you can select of.

Provided Dataset Topics

Interlink to other datasets

Define one or more datasets, so called target dataset(s), you link to. For more information see the voiD guide, section 'Describing Dataset Interlinking'.

+ Interlinking Target Description
add cancel
Target Dataset Homepage
x preview

Define the target dataset by specifying its homepage. The homepage of the dataset is a dedicated document that talks about the dataset. Use the 'preview' button to preview known datasets from voiD stores (currently Talis and RKB).

Interlinking Type
lookup

State how you link to the target, that is, provide an RDF property such as http://www.w3.org/2002/07/owl#sameAs. You can also just type prefixes such as owl and then use the 'lookup' button to replace it with the fully qualified namespace URI. It's also o.k. to use the 'short form', for the interlinking type, such as owl:sameAs, which will be replaced automatically.

more >>
Target Dataset Name
Target Dataset Description
Example Resource
Provided Interlinking Targets

List used vocabularies

List the vocabularies that are used in the dataset. For more information see the voiD guide, section 'Vocabularies used in a dataset'.

+ Vocabulary URI

You can type prefixes such as owl or foaf and then use the 'lookup' button to replace it with the fully qualified namespace URI from prefix.cc.

Tell about provenance and licensing

State who publishes the data and what the usage conditions are. If you don't want to provide any of this information, just leave it empty - it's optional, but it is advised to provide it. For more information see the voiD guide, section 'General Dataset Metadata' and 'Announcing the license of a dataset'.

Publisher

Provide a URI (Web ID) identifying the person or organisation that actually provides the dataset in RDF (for example: http://example.org/me)

Source

The source is the URI of the original data source, such as an XML document, a database, a Web service, etc. (like: http://example.org/source.xml).

License

The license should be specified via an URI representing the license under which the dataset can be used, for example http://www.opendatacommons.org/licenses/pddl/1.0/.

Specify access methods (SPARQL endpoint, etc.)

Specify (alternative) access methods for the dataset. If you don't want to provide any of this information, just leave it empty - it's optional, but it is advised to provide it. For more information see the voiD guide, section 'SPARQL endpoints, URI lookup, and RDF data dumps'.

SPARQL endpoint

The URI of the SPARQL endpoint for the dataset, for example http://dbpedia.org/sparql.

URI look-up endpoint

The URI of the look-up service for the dataset, such as http://lookup.dbpedia.org/.

RDF data dump

The URI of the data dump for the dataset, e.g., http://example.org/dump.rdf.

Output: voiD Description

Please go to http://sindice.com/developers/inspector and paste the voiD file manually. This feature will be available soon!
Ready