GraphDB Constraint Validation

compared with
Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (3)

View Page History
|| Predicate | *sys:addRuleset* ||
|| Description | Adds a custom ruleset from the specified .pie file. The ruleset is named after the filename, without the .pie extension. ||
|| Example | INSERT DATA \{ \_:b sys:addRuleset <{nolink:file:c:/graphdb/test-data/test.pie}> \} \\
This creates a new ruleset "test". If the absolute path to the file resides on e.g. /opt/rules/test.pie then it can be specified as<file:/opt/rules/test.pie>, <file://opt/rules/test.pie>, as<{nolink:file:/opt/rules/test.pie}>, <{nolink:file://opt/rules/test.pie}>, or <{nolink:file:///opt/rules/test.pie}>, i. e. with 1, 2, or 3 slashes.Relative paths are specified without the slashes or with dot between the slashes: <file:opt/rules/test.pie>, <file:/./opt/rules/test.pie>, <file://./opt/rules/test.pie>, <{nolink:file:opt/rules/test.pie}>, <{nolink:file:/./opt/rules/test.pie}>, <{nolink:file://./opt/rules/test.pie}>, or even <{nolink:file:./opt/rules/test.pie}> (with dot in front of the path). Relative paths can be used in case we know the work directory of the Java process in which GraphDB runs. Because colon means specifying a port number after the host, if we want to specify the drive letter on a Windows machine, we should NOT use slashes after 'file:', like in the example above. ||
\\

|| Predicate | *sys:addRuleset* ||
|| Description | Adds a custom ruleset from the specified .pie file. The ruleset is named after the filename, without the .pie extension. ||
|| Example | INSERT DATA \{ <:custom> sys:addRuleset "Prefices \{ a : \[http://a/\n\n\]} Axioms \{\} Rules \{\nId: custom\na b c\na <a:custom1> c\n-----------------------\nb <a:custom1> a\n\}"\} \\
This creates a new ruleset "custom". ||
\\