Author: rvesse
Date: Tue Sep 17 22:35:06 2013
New Revision: 1524245
URL: http://svn.apache.org/r1524245
Log:
Remove apparent copy paste error
Modified:
jena/site/trunk/content/documentation/security/index.mdtext
Modified: jena/site/trunk/content/documentation/security/index.mdtext
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/security/index.mdtext?rev=1524245&r1=1524244&r2=1524245&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/security/index.mdtext (original)
+++ jena/site/trunk/content/documentation/security/index.mdtext Tue Sep 17
22:35:06 2013
@@ -145,22 +145,6 @@ that have subject X and predicate Y.
The `SecNode.VARIABLE` may occur multiple times and may occur with the
`SecNode.ANY` node.
#### SecNode.FUTURE
-
-This node indicates a variable in the triple. This differs from `SecNode.ANY`
in that the system is asking
-"if there are any prohibitions" not "if the user may perform". Thus queries
with the `SecNode.VARIABLE` type
-node should return `true` where `SecNode.ANY` returns `false`. In general
this type is used in the query to
-determine if triple level filtering of results must be performed.
-
-- `SecNode.VARIABLE, X, Y>` - Asks if there are any prohibitions against the
user seeing all subjects
-that have property X and object Y.
-
-- `<X, SecNode.VARIABLE, Y>` - Asks if there are any prohibitions against the
user seeing all predicates
-that have subject X and object Y.
-
-- `<X, Y, SecNode.VARIABLE>` - Asks if there are any prohibitions against the
user seeing all objects
-that have subject X and predicate Y.
-
-The `SecNode.VARIABLE` may occur multiple times and may occur with the
`SecNode.ANY` node.
Insertions pose a different set of problems in that in some cases the system
does not know what value will be
inserted. For example when concatenating one RDFList with another
(`rdfList.concatenate( rdfList2 )`) the system
