triggers & rules
From: =?ISO-8859-1?Q?Robert_Goen=E9?=
Subject: triggers & rules
Date: Sun, 1 Jun 2008 21:55:26 +0200
Hi Guys,
I use erdf a lot as a flexible way of defining structures for simple =20
websites. The flexibility is great, but needs to be constrained in =20
many situations. I would like to make certain values mandatory, =20
define a maximum, ect. The rules discussion in the rdf world is an =20
ongoing one, but I was wondering how you guys think about constraints =20=
in a library like ARC. At first sight, the triggers seem the way to =20
go, but unfortunately, they are not implemented as postconditions. Do =20=
you think it would be useful to have something like postconditions =20
that can be used to make certain types mandatory in documents of a =20
certain type?
I was thinking of rules like the following:
http://xmlns.com/foaf/0.1/ log:implies foaf:name
which could be read like: a FOAF documents implies a foaf:name. If a =20
FOAF document is parsed and this rule is checked, it should be true =20
in order to accept the document. or something like that.
more complex expressions would be needed, of course. The sparql-in-=20
rdf thing would be very useful for this.
What do you think? Is it worth a try?
Regards, Robert Goen=E9=
