Release Notes

TopBraid 6.2


TopBraid EDG version 6.2 has enhancements to the user experience as well as performance and scalability improvements. Users will also see exciting improvements to the underlying SHACL and GraphQL technologies.

Key Improvements of 6.2:

  • Improved User Experience and User Interface for EDG:
    • SHACL/GraphQL based forms are now the default form in all collections except for Ontologies. These forms are faster and offer an option to switch viewpoints between different shapes/perspectives. Different roles can have different views. With 6.2, additional highly desired features have been added to make editing easier, such as:
      • A show properties button that displays all available properties on a form in view mode, even if they have no values. This lets users inline edit values for any property irrespective whether they currently have a value.
      • An option to display property sections as form tabs instead of one continuous list of sections.
      • “Find similar” option which takes the current instance as a “template” and allows users to select which properties they want to match against
      • Constraint violations now appear right under the property that is violated to make it easier to understand what values have issues.
    • Taxonomies, Ontologies and Crosswalks search pane was updated for an improved user experience using SHACL and GraphQL. Users will find this much more flexible and intuitive.
    • New integration with external Knowledge Graphs as described at the mini-tutorial about Wikidata integration.
    • A detailed mouse-over preview page is available for all resources in EDG – similar to a preview in Wikipedia.
    • Other general usability improvements, including:
      • Users can now run Problems and Suggestions report only for instances of a selected class.
      • Includes dialog now uses new improved interface with enhanced search features.
      • Search the EDG now has it’s own index management page with counter for administrators.
      • Users of Crosswalks can now select custom properties for mappings and it can be more than one property per Crosswalk.
      • “Automap” button in Crosswalks is now available directly in the editor to streamline auto-creation of Crosswalks.
      • Users that have a Manager permission can disable certain features for each asset collection e.g., disable certain imports, exports or reports.
  • Data Quality improvements:
    • Users can now run SHACL validation of RDF files prior to importing them.
    • EDG can now learn likely Property Value Rules directly from sample data (requires Maui server).
    • In addition to the ability to select URI generation policy to be used EDG-wide (introduced in 6.1), users can now also select different policies for each asset collection.
    • Newly created collection namespaces now use the collection name/label as default in the URI providing best practices automatically for the user. This can be changed via the EDG configuration parameters.
    • Transform tab now has a feature to copy or move instances from another asset collection, e.g. to split instances from classes.
  • Performance and scalability improvements, including:
    • Working copies now consume less server memory when used by multiple users, and changes become visible to all users without a manual refresh.
    • The home page for each collection type is now a table (instead of a list) with sorting and filtering available. This will provide a better users experience for organizations that have very large number of asset collections of a given type.
    • Asset collections can now be set to ‘read-only’, disabling editing. Desirable for large third-party collections which will not be using workflows or need editing.
    • Lineage diagrams are now faster and scale better while covering more lineage options.
    • New administrative option to count the total number of triples in EDG.
  • EDG governance improvements:
    • Governance roles can now be assigned specific permissions (manager, editor or viewer). A user that has a governance role for a collection will be automatically granted permissions associated with her role.
    • Ability to edit source code can now be controlled based on a user’s  governance role.
  • New capabilities for Ontologies:
    • Ontology editor’s search panel in no-instances mode has a button to search sh:NodeShapes.
    • OWL-to-SHACL conversion can now also convert included subgraphs and has an option to convert without replacing OWL/RDFS triples
    • Ontology editor now makes it easy to derive new Node Shapes from existing ones by offering  “Derive view shape” dialog.
    • Ontology editor now simplifies creation of Property Value Rules by offering a wizard for creating new rules based on (extendable) templates.

Technology Upgrades:

  • Upgrade to Apache Lucene 7.4.0
  • Update to Apache Jena 3.10.0
  • Update Apache Tika library to version 1.19.1.
  • Update jackson core/databind to v 2.9.8

Deprecated Features:

  • Starting with 6.2, new workspaces in TBCME will no longer automatically include samples, This will make download of TBC and its initialization faster. It will also let us provided updated samples between releases. You can use samples from your previous workspaces (use Import Existing Project) OR download the most current samples from our website. Download these from the downloads page, extract them, and use import Existing Project selecting “search for nested”.
  • Faceted search, including the ability to configure and update Solr index for faceted search has been removed. This feature is replaced by EDG search enhancements that now provide equivalent capabilities.
  • Custom configuration parameters page previously available in the Administrative console has been removed. Customers are encouraged to, instead, store their custom config objects as Ontologies or similar graphs.
  • MarkLogic is no longer available as EDG application data storage option.
  • Find Asset Collecton page is scheduled for removal in the next release.
  • With 6.2, the enable ontology optimizations options should not be manually set to false. Remove or set to true.
  • Regex search in the tabular editor has been temporarily removed. A new option will be available in upcoming release.
  • Please see Change-log for more deprecated functions

Known issues:

  • If an ObjectProperty used in a property shape has a URI containing a hyphen it will not appear in the EDG UI. The workaround is that in the generated shapes a graphql:name must be specified. This is being re-worked in the next release to not have this limitation. 
  • Close match property is not available on SHACL based forms. This property will be added to EDG core to resolve this issue. 
  • If your user interface appears to not be loading, please check the developer console on the browser for error messages as they may not get pushed to the UI. We are working to correct this behavior in version 6.3.