RDF is not the be all end all for representing information, so I don't know
if there is a point to defining a validation schema which can also be
represented in RDF since requirements vary from model to model, project to
project. If you were creating RDF/XML, you could enforce complex
validation
I followed the W3C RDF Validation Workshop [1] over the last two days.
The web page has both written papers and slides from each presentation.
The short summary is that a number of users of RDF have found a need to
do traditional style validation (required, one or more, must be
numeric/from a
Ethan, it is true that probably a majority of RDF sets in the cloud
are exports from a non-RDF format. Yet if you look at the page I cited,
you will see that there are major players (including Google) working
with triple-stores and doing validation on them using SPARQL. So
validation of RDF
