Release Notes¶
Enhancements¶
Resolving¶
and to try.
Enabled resolver mapping files to contain rules calling a forge method #323 (issue #316)
More properties (e.g. altLabel, definition, isPartOf, …) are retrieved when resolving an ontology term (#337)
alternateName property can be used to resolve agent in AgentResolver #404
OntologyResolver: Added an ontology resolver target ‘Strain’ #405
Querying¶
to try the enhancements.
BlueBrainNexus store: An elasticsearch or sparql view id can be provided using a view argument when calling forge.sparql, forge.elastic or forge.search (#373) If a view id is provided, only data accessible from that view will be searched and retrieved.
forge.elastic can now return results as list of dict instead of a list of Resource when as_resource is set to False #382
Forge¶
to try the enhancements.
Bumped JSON-LD context version from 1.0 to 1.1 to enable expanding a JSON-LD prefix mapping ending with a non IRI-delimiting character such as ‘_’ or any character not present in rdflib.plugins.shared.jsonld.context.URI_GEN_DELIMS #387 (issue #386) See also RDFLib/rdflib#2606
Modeling¶
to try the enhancements.
RdfModel: Added support for importing ontologies from SHACL schemas using owl:imports. Added support for inference. Use forge.validate(resource, inference=”inference_value”, type_=’AType’) with inference_value as in pyshacl. inference_value=”rdfs” is enough to extend the resource to validate with the transitive closures of type subClassOf and/or property subPropertyOf relations. Validation will fail when a type not in the resource to validate is provided as value of the type_ argument unless inference is enabled (with inference=’rdfs’ for example) and the resource type is a subClassOf of the value of type_ #396 (issue #369)
Dataset¶
to try the enhancements.