Child pages
  • Migration from TopBraid 6.1 to EDG 6.2
Skip to end of metadata
Go to start of metadata

Overview

Unless otherwise noted, the migration items are cumulative. Thus, beginning with one's current version level, all items from all subsequent sections, i.e., (increasing) version levels, should be checked for possible applicability.

 

Migration from 6.1.x


Ontology Optimizations setting

If you manually disabled Ontology Optimizations, see 6.1 Migration "Collection Optimizations are Enabled", you must re-enable this for version 6.2. 

 

Read-only flag for collections

 

Migration concerns for those who have developed custom extensions (e.g. SWP pages). The new read-only flag SHOULD disable any feature that can make changes to an asset collection's master graph. If you have developed an EDG extension that makes modifications, you should make sure that it gets disabled when the corresponding asset collection has been made read-only. This usually happens automatically with no code changes, as long as your extension checks that the current user has editor permissions, e.g. using teamwork:currentUserHasPrivilege. The only case where you may need to make changes to your extension is if you have checked for manager permissions instead of editing permission: for read-only graphs, the function teamwork:currentUserHasPrivilege (and derived functions) still return true if someone is a manager, and the requested permission is teamwork:manager. In those cases, you should add an extra clause to check !teamwork:isReadOnlyProject(?projectGraph). Please contact TQ support if you have questions.

Search pane on Ontologies and Taxonomies require SHACL

 

The search pane of EDG Ontologies and Taxonomies is now based on SHACL. To migrate a collection's included ontologies to a SHACL basis, see: Ontology Utilities > Convert OWL Axioms to SHACL Constraints on wiki.topquadrant.com. If your ontology contains instances, you need to generate SHACL shapes to fully use search over instances. Otherwise, only free text search is available.

 

Usages in Other Collections

 

Usages in Other Collections section in the detail forms has been removed with the new SHACL based forms. It was only implemented in a limited fashion in previous releases. This will be reimplemented with a more robust solution in a future release.

 

SHACL-based Resource Forms

 

The new implementation of resource forms now the default for all asset collections with the exception of schema elements (classes, properties, etc.) in ontologies. The forms now require models to be defined in SHACL. If you have not been using SHACL in your modeling, you can convert RDFS/OWL into SHACL by going to Transform tab and executing conversion. Note that, if desired, you can keep your RDFS/OWL statements along with the SHACL shapes. You can also change the server setting to keep previous forms as the default choice. However, the new forms are faster and have a number of new features and enhancements. Please see Ontology View or Edit#SHACL-basedInstanceForms for more details. 

 

  • No labels