I have a very non-technical team that would like to build an RDF vocabulary. So I thought a little about what I learned about RDF, which is mainly that RDF triples are made out of URIs. Google Sites offers the ability of creating Pages and Sub-Pages that generate URIs such as
Would this be a good way to start building a vocabulary without any extra programming or development, or am I missing something? I imagine my team would simply create a page for each of the vocabulary terms we have.
Eventually I want this vocabulary to be used with RDF. Any ideas? What would happen if I wanted to build relationships such as the ones defined in OWL and RDFS?
In a very brief nutshell: RDF triples represent graphs of structured or semi-structured data. The URI is used to provide a unique naming scheme for classes and play a part in constructing triples, but only a part. You should have a domain unique to your organization for URIs. URIs should be persistent as well, this will give you an idea of how that works. Google sites, unless using your own domain name, aren't appropriate.
Read the W3 primer for RDF, it's a good place to start. You might want to hire or contract in help if this is beyond your team's technical ability, taken that an RDF vocabulary is really what you need.
The approach you've chosen for building a vocabulary is a very elegant idea, however this will not result you an RDF graph by default (assuming your team will create human content on these URLs). The URLs would be the nodes, but you need edges too. There are two options to build it up to a graph:
You will need either a triplestore or one should be able to dereference your URLs to download RDF about the resource. The ideal solution is both, but you need to make sure to keep these synchronized. You can check out how the dbpedia was built out: http://wiki.dbpedia.org/Architecture
If you consider this image, here the box "HTML" would be equivalent to your handmade pages:
In dbpedia the HTML representation is automatically generated from the database. As you can see, you will need a lot more in order to serve up RDF. Having your own domain (and not leveraging the google URL) has also some benefits, so you should consider some equivalent solution running on your domain.
answered 02 Feb '13, 14:24