updated blog
authorLuc Moreau <l.moreau@ecs.soton.ac.uk>
Mon, 10 Sep 2012 15:54:17 +0100
changeset 4449 89c2cff9176b
parent 4447 7b321dfba2c1
child 4450 f780a5605200
updated blog
--- a/model/blog/constraints-blog.html	Mon Sep 10 15:21:35 2012 +0100
+++ b/model/blog/constraints-blog.html	Mon Sep 10 15:54:17 2012 +0100
@@ -81,7 +81,9 @@
 <p>This example was simple and may not have required an automated validator to detect invalidation. However, when graph patterns become more complex, an automated validator turns out to be an essential component for provenance users, whether they intend to publish provenance, or whether they intend to consume it. The prov-constraints document defines a set of constraints that validators are expected to implement.</p>
+<p>We encourage developers to implement these constraints. Several
+people are already working on validators and we encourage you to do so
+as well.</p>