The Transform Tab lets users run various transformation operations that will modify an asset collection they are working with. This view and its operations are only available to users with editor or manager privileges for the collection.
If any SHACL (or SPIN) rules have been defined in the current collection or any of its inclusions, they will be listed here. Editors can select rules for execution to generate inferred triples that are added to the current collection’s graph. Also, one has the option to revisit all previous rules executions to remove results that are no longer valid.
Copy or Move Instances from Other Asset Collection
Copies or moves assets from other asset collections. “Copy” adds instances of selected classes from another asset collection into this Taxonomy. “Move” will also update the source asset collection by removing the instances from it. Executing “Move” requires editing permissions for the source asset collection. This option is useful for separating your instance data from schema.
Delete Sample Data for Data Assets
For Data Asset collections that have sample data imported from data sources , this allows collection editors to remove or reduce the sample rows currently retained by the collection. This does not effect future imports.
Convert OWL Axioms to SHACL Constraints for Ontologies
This scans the ontology, either replacing any OWL restrictions or RDFS domain/range axioms with their corresponding SHACL shapes or simply adding SHACL shapes. This provides a starting point for full SHACL enablement. It is recommended to create a workflow for this operation to verify its results before committing them.
For an explanation of the OWL-to-SHACL mapping, see TQ Blog entry: From OWL to SHACL in an Automated Way. For even more exact and up-to-date details, see the
rdfs:comment items in the
owl2shacl.ttl workspace file (path: