Package org.aksw.jena_sparql_api.data_query.impl
package org.aksw.jena_sparql_api.data_query.impl
-
ClassesClassDescriptionDataQueryImpl<T extends org.apache.jena.rdf.model.RDFNode>Optional paths Given the following graph patterns, are the some algebraic relations that hold between them? (a) { OPTIONAL { X } } (b) { OPTIONAL { X OPTIONAL Y } } (c) { OPTIONAL { X Y } } c: If for some binding of X there is no suitable binding of Y, the whole binding will be dropped Maybe optional should be part of the traversal api? fwd('foo').opt().fwd('bar')FactoryWithModel<T extends org.apache.jena.rdf.model.RDFNode>Scan all nodes of a query for instances of NodePathletPath and add resolve the contained path against a pathletContainerNodeTransformer that detects nodes that are path references, and resolves them to appropriate variables, thereby keeping track of graph patterns that need to be injected into the base query.Stateful mapper that creates SPARQL BinaryRelation objects from paths, thereby ensuring consistent variable naming The mapper does not track changes - such as modifying a path's alias TODO Here is the place for making use of a registry for mapping path elements to binary relations if desired ~ Claus Stadler, Jun 2, 2019A query fragment is construct query with a designated variable.