There is this project called SPIN (spingrdf.org) which lets you add
constraints that are checked when you insert new data into the store. In
this way, as I see it, you're not "blocking the data-flow". Whatever gets
into the store is "valid", and the inferences are done in the same way
(there's no difference after you inserted the instances).
Enforcing constraints in the application layer requires, in this particular
case at least, a lot of code and overhead (latency!).
In case Virtuoso doesn't support data integrity for RDF I think I'm going
to use the stack TDB+Jena+SPIN+Virtuoso (I still didn't try to integrate
them all).
On Wed, Apr 24, 2013 at 12:12 PM, Alexey Zakhlestin <indey...@gmail.com>wrote:
>
> On 24.04.2013, at 19:04, Matías Parodi <mparodil...@gmail.com> wrote:
>
> > Any idea about forcing constraints in Virtuoso?
>
> well… my personal belief is, that constraints should be enforced on
> application level
> RDF is good because it allows you to store and exchange
> opaque-but-introspectable data
>
> Application, on the other hand, can use RDFs/OWL/whatever rules to fit it
> into some system, but this shouldn't block data-flow on storage level.
> So, this way you can let your application to comfortably work with a
> subset of RDF, ignoring other pieces which fly by
------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
_______________________________________________
Virtuoso-users mailing list
Virtuoso-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/virtuoso-users
