Shexer

Now you can use the parameter instances_cap when building a Shaper object to avoid using EVERY available instance of a class to extract a shape. This parameter will be the maximum number of instances per shape used.

This is relevant in huge computations with many instances/target shapes, as you'l be able to save a lot of memory and tackle big graphs using regular, every-day, normal hardware.

This feature was disabled, but some users find it useful. By default, sheXer won't generate OR constraints including the macro IRI If you want it to do that, set allow_redundant_or=True when building the Shaper object

sheXer could generate incorrect syntax when serializing URIs in ShExc starting with a declared prefix-namespace, but not direct child of such namespace. That's no longer happening.

Fix syntax expressing absolute IRIs in IRI patterns (ShExC)

New feature included. Each shape can be associated with a regex pattern. That pattern expresses the initial part of the IRI that is common to every isntance used to extract a given shape.