7.0 – TopQuadrant

EDG 7.0 Release

TopBraid EDG version 7.0 delivers a modernized architecture and deployment process. This change in architecture allows for support of Tomcat 9 and Java 11. EDG 7.0 has added support for working with files and developing scripts directly from the EDG UI.

TopBraid EDG 7.0 also delivers a number of improvements to ontology development, editing of data, support for making changes across asset collections, localization and other capabilities. A new browser plugin for Chrome is being offered in this release with the goal to enable semantically enriched web browsing. These new features are described in more detail below. Additional improvements and their associated ticket numbers can be found in the change-log to the right.

The migration and new deployment instructions need to be followed for this release – see details in the Migration and Upgrades on the right.

Key Improvements of 7.0

Modernized architecture and deployment process

Removed dependency on Equinox making it possible to deploy TopBraid EDG on Tomcat 9 in addition to Tomcat 8.5
Required Java version changed from Java 8 to Java 11
New simplified installation process that supports both interactive setup via a UI and setup via configuration files for scripted deployment
Active Data Shapes have matured from the experimental stage and are now a fully supported option for defining server-side scripts and customizations in JavaScript.
JavaScript support is upgraded from Nashorn to GraalVM.
Library updates: Bootstrap 4.5, React-select 3.1.0 and jQuery 3.5.1
A new Power User role has been added to EDG to allow for separation of control for administrative features. The Power User role has access to limited features of server administration but will have access to all collections in the EDG workspace. The Administrator role will continue to have full access to everything.

Support for Files As an Asset Collection Type

Users of EDG can now open and modify files directly with EDG using the “files” collection type. File editing is only available to administrators.
Div-like utility displays comparison of the opened edited version in progress and the file as stored on disk.

Ontology Development Improvements

Customization of forms for classes, shapes and other system resources is now much easier and no longer relies on modifying metash file. Constraint checks on system classes are performed as part of the usual SHACL validation.
Property pair constraints are now included on the editor form for ontologies.
sh:order has been added to the Create Property dialog.
The property path is now navigable when expanding the view of a property shape.
OWL restriction display has been improved for better clarity.
Managers of the Ontology asset collections can turn on ability to create instances within an Ontology. They can also allow users to to edit all fields of the instances in an Ontology – previously only label and comment were available for on the Form editing. Note that while this option is now available, the best practice remains to keep classes/shapes separate from instances and use other, non Ontology types of asset collections to store instances. Turning on this option is generally discouraged as it may significantly slow down the system after each edit.

Support for Making Changes Across Asset Collections

Users can now delete property values across graphs. We recommend using this option prior to deleting a property shape – to make sure not instance data remains.
Users can now update data across asset collections by replacing one predicate by another. With this, values for a selected property will be copied as values of another property. Original values are deleted. This is another option to use prior to deleting a property shape.
Users can now change a datatype of values for a selected property – across graphs. We recommend using this option prior to changing a datatype definition for a property shape.

General Usability Improvements

All required (min count = 1) properties are now displayed in the Create New dialog for instances.
The Editor form has a new option to show values of undeclared properties. Undeclared properties are properties not defined by the property shapes. If they have values, they will be shown on the form. This is read-only display, update of such values using the form is not supported.
New Local Assets panel to show only the resources that are declared in the current asset collection (i.e., local as opposed to included assets). Two other newly added panels are NeighborGram and Inferences.
Managers of a collection now have the ability to control default settings for all users in the editor application. This option can be found in the Settings menu on the Editor application’s header bar.
Improved default layout for Crosswalk asset collections.
Ontology developers can now define enriched asset summaries to be displayed on the mouse over – as described in http://datashapes.org/propertyroles.html. If no definition is available, EDG will continue to simply display asset’s label and description on the mouse over.
Users can now change the “Welcome to TopBraid EDG” heading text on the home page through the governance model collection.
Search the EDG index can now be rebuilt or removed from the server administration page for Search the EDG indexes.
A cache has been implemented for user permission throughout EDG which will improve performance of the UI for non-administrators.

Improved Support for Localization

New feature to set the default language on the Manage tab of a collection. All new values with lang option will have this language pre-set.
“Hide values in non-preferred languages” setting is available in the main header. This will be used by forms and nested forms to further enhance multi-lingual support.

Report for Imports

New detailed report for history of imports, successful or failed. Report shows the user, file that was imported, date/time, and triples added or removed.

Workflow Related Improvements

Workflow name is now auto generated. Can be overwritten.
Basic (default) workflow has been moved making this workflow no longer included when using customized workflow templates.
Change history panel now has filter for workflow to allow reverting an entire workflow.

Semantically Enriched Browsing Powered by TopBraid EDG

The TopBraid Browser Extension allows users to query and use knowledge graphs from any Web site they are currently looking at. In particular, the extension attempts to match terms found on the currently visited page with labels of concepts stored in TopBraid EDG taxonomies, glossaries or other knowledge bases. Matching terms will be highlighted on the Chrome page and backed with a rich popup window with further information taken from the knowledge graph.
Users can then navigate to the definitions of those knowledge assets in a TopBraid EDG browser tab, or establish links from the knowledge asset to the web page. The extension also provides general search features including a path finder that attempts to discover semantic connections from a term on the page to other terms on the page.
More details and a walkthrough can be found in the video: https://archive.topquadrant.com/project/topbraid-browser-extension/.
This new capability requires a knowledge graph hosted by EDG 7.0 and a Chrome browser plugin that you can now download from the Chrome plugin store here: https://chrome.google.com/webstore/detail/topbraid-browser-extensio/lnplheclnnjlekacjclcighklolhbcih.

EDG 7.0.4

Update log4j to version 2.16.0 to fix vulnerability CVE-2021-44228, CVE-2021-45046

Improvements and bug fixes for 7.0.3

Enhanced and extended previously available DDL import functionality for MySQL, Oracle, PostgreSQL, and SQLServer. Added support for DDL imports for Hana, Snowflake, Teradata and Hive.
With this change, a user must select the source system of the DDL statements. Only sources available in the drop down list are supported.
This new feature has been tested only for the previously supported sources: MySQL, Oracle, PostgreSQL, and SQLServer. DDL import for Hana, Snowflake, Teradata and Hive is expected to work and is supported. However, testing for these sources is incomplete.
Fix for importing spreadsheets causing issues with URIs.
Explicitly include prefixes in saved SPARQL library panel to ensure the queries will not error due to unresolved prefixes.
Fix for double encoding on user id with SAML SSO when using email as user id. This requires performing a migration to clean up existing data in EDG. See migration notes for details.
Fix for “show local results only” filter in the collection editor.
Ability to configure reach and breadth for LineageGram. This allows the user to visually limit the scope of the results in the diagram.
Please see the change log at the top right corner of this page for details on these changes and descriptions of a few more minor changes.

Improvements and bug fixes for 7.0.2

Added support to manage a sub-directory for S3 attachments.
Fixed problems in Oracle JDBC import.
Made minor modifications to EDG ontologies.
Added various improvements to GraphQL and Active Data Shapes.
Please see the change log at the top right corner of this page for details on these changes and descriptions of a few more minor changes.

Improvements and bug fixes for 7.0.1

A debugging SPARQLMotion function utility allowed arbitrary execution of operating system commands through custom code or the SPARQL endpoint. The utility has been removed in 7.0.1.
Send log to TopQuadrant support fixed.

Deprecated Features

Support for D2RQ connection files (.d2rq extension) removed from all products
TBCME import wizard removed: “Create Connection for RDBMS Source (using D2RQ)”
Use of the metash namespace for form customization is no longer supported. Customizations for the forms of classes and shapes need to be redesigned.
SPINx has been removed. Please migrate to either SHACL-JS or ADS
SHACL-JS has been changed to use a different engine with actually better capabilities: from Nashorn to GraalVM. This may cause slightly different behavior from SHACL-JS. In general, we recommend upgrading to Active Data Shapes if possible.
The following SparqlMotion modules have been removed from EDG:
– sml:Diff
– sml:CheckSpelling
– sml:AddUserDictionaryWord
– sml:RemoveUserDictionaryWord
– sml:UpdateUserWordDictionary

sml:RequestLock and sml:ReleaseLock were until now marked to be not only a SPARQLMotion module but also an SWP element. Anyone using those as SWP tags, should look for alternatives.

Known issues

Some impact diagrams will not render completely for LineageGram..

‍

Mon Aug 29 2022 19:17:33 GMT+0000 (Coordinated Universal Time)