/**
 * If set true, the query reformulation will use region partitions according
 * to their relations to potentially reduce the size of the reformulation.
 * This potentially improves query execution at the cost, however, of
 * completeness (I believe :)). So if your queries run fast enough with the
 * standard setting, don't worry. If they are slow, try to set this option
 * 'true'.
 * 
 * Default: false
 */
public static boolean USE_REGION_PARTITIONS = false;

/**
 * This is Pellet specific. If this is set true, for every region an axiom
 * is added that states that every region must contain all of its interior
 * points (see
 * RCCRelationTranslatorPellet.RCCRelationVisitorPellet.prepare()). This
 * seems to be a required axiom that I have either overlooked or it is
 * missing in the theory PelletSpatial bases on.
 * 
 * Default: true
 */
public static boolean ADD_INTERIOR_POINTS_OF_REGION_AXIOM = true;

/**
 * If set true, instead of DL reasoning, the RCC composition table based
 * reasoner is used.
 * 
 * Default: true
 */
public static boolean USE_COMPOSITION_TABLE_REASONER = true;

/**
 * The dual stage query engine executes (SPARQL) queries in two stages. The
 * first stage executes RCC relations over the network. The bindings are
 * then passed to the second stage where Pellet is used to answer the
 * remaining RDF patterns. If this is set true, then
 * USE_COMPOSITION_TABLE_REASONER should also be true.
 * 
 * Default: true
 */
public static boolean USE_DUAL_STAGE_QUERY_ENGINE = true;

/**
 * If true, the progress of composition table reasoning is displayed
 * 
 * Default: false
 */
public static boolean SHOW_COMPOSITION_TABLE_REASONER_PROGRESS = false;