Version
9.4

TopQuadrant Data Foundation 9.4

9.4 puts AI help throughout the product, gives administrators a built-in scheduler, and makes governance reviews accountable. TQ Copilot is now available across the whole application, the MCP server is ready for production use, and SHACL 1.2 support keeps tracking the W3C working group.

Overview

9.4 puts AI help throughout the product, gives administrators a built-in scheduler, and makes governance reviews accountable. TQ Copilot is now available across the whole application, the MCP server is ready for production use, and workflow reviewers have to give a reason when they reject something. SHACL 1.2 support keeps tracking the W3C working group, and TQ Studio brings the new interface to a single-user desktop edition.

Bug fixes, including those that shipped in the 9.3.1 through 9.3.3 patch releases, are listed in the change logs.

AI and Copilot

One conversational assistant, available wherever you're working, plus a production-ready way to connect outside AI agents.

  • TQ Copilot, everywhere. Copilot is now TQ Copilot and is available from any page in the application, not just the editor. It shows which collection or workflow you're working in and marks the point in the conversation where that context changes, so you always know what an answer refers to.
  • Placement and size. Choose where the panel docks and how large it is.
  • Skills, history and SPARQL. Pick a skill from a menu, go back to earlier conversations, and move a natural-language SPARQL request into the SPARQL editor.
  • Slash actions. Type / to start many of the application's own operations from Copilot. Each one opens the same dialog you'd use anyway, so you still review and confirm before anything changes.
  • Connect your own AI tools with the MCP server. Use the MCP server to let AI assistants and agents, such as Claude, work with your collections, for example by asking questions about your data and running queries. People sign in with OAuth. Setup and administration are covered in the MCP server documentation.
Governance

Workflow reviews now leave a clear trail. Reviewers explain their decisions, owners know who's reviewing, and nobody is surprised by what a transition did.

  • Reasons for rejections. Rejecting a workflow or requesting changes now requires a reason, and the workflow owner can see it.
  • Choose the reviewer. When you freeze a workflow for review, you can pick the reviewer for that specific workflow instead of relying only on the template default.
  • Problems before you submit. If required fields or validation rules aren't met, you're told what's missing and why when you try to move the workflow forward, instead of the transition quietly not happening.
  • What a transition changed. When a transition fills in or changes values for you, you're told what it did.
  • Show Affected Workflows. This feature has been rebuilt for the new interface.
SHACL 1.2

The SHACL engine keeps pace with the W3C SHACL 1.2 working group, and this release concentrates on rules.

  • Rules. Global rules and runOnce are supported, sh:TripleRule support is updated, and sh:tempTriple and sh:entailment for specific rule sets are now available.
  • Incomplete data. sh:incomplete and sh:incompleteURIStart are supported.
  • Custom SPARQL functions. You can define SPARQL functions based on node expressions.
  • Inferences. Metadata about an inference graph is now stored and shown, and the Inferences panel can apply sh:defaultValue and sh:values inferences.
  • Malformed sh:in constraints. They're detected and reported more reliably.
Scheduled jobs
  • Built into the product. A scheduler lets Power Users and Administrators automate recurring work from one place, with no external scripts or cron jobs to build and maintain. You can schedule backups, file imports and exports (from or to the workspace or S3), publishing to Explorer, and Problems and Suggestions reports, and set how often each one runs.
  • See what ran. A table shows scheduled, running, completed and failed runs with timestamps and a link to the output where there is one. Failed runs show an error status and code, so you can work out what went wrong without opening a support ticket. You can preview and clean up old run history.
  • What it covers. The scheduler handles timing for those defined job types only. The JDBC importer keeps its own scheduler.
Importing, exporting and integrations

Bringing external ontologies in is easier, and ADS scripts can now work with YAML.

  • Several files at once. Import SHACL Ontology from OWL/RDFS File now accepts multiple files in one import.
  • Whole zip files. Importing RDF from a zip now includes every graph in the archive instead of only the first file.
  • Newer FIBO. The FIBO ontology bundled with the product is updated to the 2026 Q2 release.
  • RDF/XML export. RDF/XML export is re-enabled for collections that use RDF 1.2 reifiers.
  • Batch Edit. You can now clear a property across all selected assets in one step, even when each asset has a different value.
  • OWL to SHACL. The list of graphs to include has a filter, which helps when an ontology has many includes.
  • YAML in ADS scripts. ADS scripts can now read YAML files and turn them into JSON, so you can process YAML on demand with graph services or convert it however you like.
TQ Studio

A single-user desktop edition of TQ Data Foundation.

  • The same interface as the hosted product. TQ Studio mirrors the TQ Data Foundation interface. Capabilities that depend on server or cloud services, such as Copilot, Marketplace and the AI features, appear greyed out with a short explanation instead of disappearing, so you can see what's available in the hosted product.
  • macOS. Studio now has its own Dock icon and app name.
Interface improvements

Changes you'll notice across the application.

  • Row details in a side panel. Table rows open in a side panel for viewing and editing, replacing expandable rows and inline edit buttons.
  • Collections. Collection type icons have distinct colors on the Collections page and in the mega menu, and long Subject Area values are truncated consistently. The Create Collection dialog suggests a valid prefix automatically and keeps the prefix you edit.
  • Accessibility. Form field errors are announced properly to screen readers.
  • Documentation in context. Plugin dialogs link to their documentation.
  • SPARQL Query panel. The Reset button has been improved.
Diagrams

Simple diagrams are easier to work with.

  • Direct manipulation. Drag nodes to rearrange them, and new nodes are created with a placeholder label. Long edge labels are handled gracefully.
  • Clearer wording and layout. Diagram types are recognizable from their tabs, wording and button placement are friendlier, and deletion options sit in a compact action menu.
  • Read-only diagrams. They show relationship names on edges and offer only the Hand tool.
Marketplace
  • Refreshed interface. The Marketplace has been updated to the new design.
  • Ontologies stay current. Installing the latest version of a dataset now brings in the ontology from that distribution, rather than silently keeping the old one. Installing an older version leaves your installed ontology alone, so an install can't downgrade it. When you upload a distribution file, the ontology is replaced only if you turn on the new Replace existing ontology option, which is off by default. The ontology keeps its URI, so collections that import it keep resolving.
  • Checked before publishing. New dataset versions go through validation before they're published, so a version that leaves constraint violations doesn't go live.

For more details see:

Change Log:
TopBraid Suite Change Log 9.4.0

‍Migrations and Upgrades:
Migrations