TopBraid EDG lets you export metadata and data to JSON-LD, RDF/XML, N-Triples, Turtle, TriG, JSON, CSV, TSV and XML through pre-built functions, SPARQL endpoint and GraphQL endpoint.

Export of subsets of an asset collection’s data according to custom criteria and sorting is available in the EDG’s Search and SPARQL Results panels in the editor. These panels provide fine-grained control over the data to be selected. Menus in these panels offer several choices to export the results into spreadsheet-compatible formats (e.g., for Excel) as well as other formats. See Actions in the Search Panel and  SPARQL Results Panel sections in the Editor in EDG

Export page (tab) for an asset collection or a workflow (working copy) of an asset collection offers several pre-built export options. These options are described below.

Additional exporters can be configured using Export modules that are part of TopBraid EDG’s platform. If your organization configures a new custom export to appear on the Export page, you will see it listed as one of the available options alongside with the pre-built exporters.

Your organization may also deactivate some or all of the Export page options. This decision can be made on a per collection basis on the Manage page (tab). In this case, you will see less export operations than described here.

In addition to being available on the Export page, all export operations can be executed as services.

You can also export data directly from the pages that let you view and edit asset collections through:

Bulk export to AWS S3 can be done through the EDG Basket.


Export Data as a Graph


These operations let you export collection’s data in a standard RDF serialization format.


TriG with inferences and Include inferred statements from SHACL rules options will add a dedicated graph named urn:x-topbraid:inferences, which has any triples inferred via SHACL or SPIN rules; note that this computes on-the-fly and might be very slow.

Browser interactions might vary: displaying the data directly or via a kind of view source command. Alternatively, instead of directly clicking a format link, the browser might provide (on the link) a right-click menu option to save the link target to a file (i.e., without explicitly displaying the link result in the browser). A dialog box will prompt for the file location and name.

You can also queue the export of one or more asset collections by placing them into the Basket and then selecting Export to S3 option.

This requires that at least one S3 bucket is configured by the EDG Administrator. Once set up, you must select a bucket using Manage tab > Select S3 Bucket for Exports. Export will run in the background and, once exported, files will be saved to the S3 bucket. This option lets you specify if you want the exported files to be compressed.

Publish for Explorer Users


On an EDG server that is paired with a TopBraid Explorer server (for read-only access), managers can publish it to the Explorer for viewing. Note that the working copies of all published asset collections might or might not be viewable, depending on the Explorer’s administrative configuration.

Any manager of an asset collection can control its Explorer publication status by selecting Export > Publish Glossary for Explorer Users. The view shows a Status drop-down for the asset collection, which indicates whether the asset collection was ever Published or not (Unpublished).

It also lists any included asset collections that might also require publication.

Ensure that all included graphs are either already present on the Explorer server or published along with the asset collection. 

Changing the status causes the following action.


Current Status Chosen Option Result
Unpublished Published Sends a copy of the asset collection and selected includes to the Explorer server. Changes the source collection’s status to Published.
Published Update Published Copy Re-sends a current copy and selected includes to the Explorer server, overwriting the previous version(s). Keeps the source collection’s status as Published.
Published Unpublished Deletes the asset collection on the Explorer server. Changes the source collection’s status to Unpublished.


GraphQL Queries

This options allows users of the collection to retrieve and modify asset collection data using new or saved GraphQL queries.

TopBraid EDG generates GraphQL Schemas from the underlying ontology models. Each time an ontology changes, its GraphQL Schema will be regenerated. The generated schemas are “enhanced” to make it possible to filter data as detailed on the following page: page

In addition to the main GraphQL Queries link you will be able to select alternative GraphQL Schemas- these will depend on the type of asset collection. The main link GraphQL Queries will use the default schema for the collection type.

As Metashapes link will let you query the schema itself – classes and properties. It is the default option for ontologies.

As Teamwork Graph link will let you query change history.

If a property of an asset has a dash:reifiableBy shape set for it as described in the Ontologies guide, then when formulating a query, you should see an additional GraphQL field ending with _reif such as:

 cities {
   areaKM_reif {

For users unfamiliar with GraphQL, GraphQL in TopBraid Tutorial link will display an interactive tutorial inside TopBraid EDG.

For more information on GraphQL visit or the TopQuadrant GraphQL page

Asset Collection Specific Exports

These exports are only available for specific collection types

Export Hierarchy Spreadsheet

This export is available for Taxonomies. It outputs an entire taxonomy tree in a spreadsheet compatible format.

Export Concept Overview Spreadsheet

This export is available for Taxonomies. It outputs all taxonomy concepts in a spreadsheet compatible format. For each concept, this output includes every available property as a spreadsheet column.

Export Ontology as RDF Schema File

This export is available for Ontologies. It produces a simple, approximated RDF Schema version of the current ontology in SHACL.  The output in in Turtle format. 

Export Ontology as OWL File

This export is available for Ontologies. It produces a simple, approximated OWL version of the current ontology in SHACL.  The output in in Turtle format. 

Export Crosswalk as Spreadsheet

This export is available for Crosswalks. It creates a comma-separated spreadsheet containing one row for each mapping in a Crosswalk.

Export Avro JSON

This export is available for Data Asset collections. It creates one or more Avro files in JSON format for database tables. Users get to select tables to export.

Normalized Concepts

This export is available for Content Tagsets. It generates a normalized version of the Tagging vocabulary used in a Content Tag Set, as it would be seen by AutoClassifier.  Useful for troubleshooting. The output is in Turtle format.