From 7981b8fed915557831ad95d942f653003b57bd31 Mon Sep 17 00:00:00 2001 From: hudajkhan Date: Wed, 30 Jul 2014 14:32:25 -0400 Subject: [PATCH] adding example of where model change preprocessors can be defined in the n3 --- .../everytime/n3ModelChangePreprocessors.n3 | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 rdf/display/everytime/n3ModelChangePreprocessors.n3 diff --git a/rdf/display/everytime/n3ModelChangePreprocessors.n3 b/rdf/display/everytime/n3ModelChangePreprocessors.n3 new file mode 100644 index 00000000..3d9afdf4 --- /dev/null +++ b/rdf/display/everytime/n3ModelChangePreprocessors.n3 @@ -0,0 +1,17 @@ +# $This file is distributed under the terms of the license in /doc/license.txt$ + +@prefix owl: . +@prefix display: . +@prefix rdf: . +@prefix rdfs: . + +## The example below demonstrates how you can associate particular ModelChangePreprocessors +## with the application as a whole. These preprocessors will be run with +## every edit/addition in N3EditUtils.preprocessModels(changes, configuration, vreq); + +## Defines the preprocessor class +## Can extend this to define what the constructor arguments should be if required, and then N3EditUtils.java should be modified +## to know it can pull out parameters based on what is defined in the display model + +## +## a . \ No newline at end of file