Export your UNS to RDF/OWL/GraphDB

New for 10.1.5 (draft preview). This page previews a feature shipping in FrameworX 10.1.5 (planned April 2026). The feature is not available in 10.1.4 or earlier. Content under review.

Serialize the UNS back to an RDF/OWL graph file for diff, archive, or upload to a triple store.

Standards Compliance How-to → Industrial Ontology → Export

Primary path: the Export Tags format selector

In Designer, open the Unified Namespace → Tags page.
Click Export Tags on the toolbar.
In the Format dropdown pick one of:
- JSON. The standard FX tag export (no graph expansion).
- RDF / JSON (.rj). W3C RDF/JSON. Default for graph round-trip.
- JSON-LD (.jsonld). Falls back to RDF/JSON in 10.1.5 with a warning. Native emitter ships in 10.1.6.
Pick a policy if you imported with one (same file as the importer).
Click Export. The file lands in the solution's Exchange folder as <SolutionName>_UNS_Graph.rj (or .jsonld).

Alternative path: AI-driven via the MCP tool

export_graph_model(format="rj", policy="iof")

See skill Skill Export UNS as RDF.

Round-trip fidelity

Faithful round-trip at the UserType / Tag / member-def level. Columns expand back to triples:

FrameworX column	OWL emission
`SourceIri`	Subject IRI (class, individual, or predicate). `/Attr` tail stripped on export.
`Description`	`rdfs:comment`
`DisplayText`	`rdfs:label`
`Labels` (semicolon-delimited)	`skos:altLabel` per entry
`BaseUserType` (UDT only)	`rdfs:subClassOf` → parent UDT's registered IRI
`Attributes` (parsed JSON)	Individual triples keyed by `prefix:localName`. `@lang`-suffixed keys emit language-tagged literals.

What does NOT round-trip

owl:Restriction flavor (someValuesFrom / allValuesFrom / cardinality). FX captures target type, not restriction style.
owl:unionOf / owl:intersectionOf anonymous classes. Flattened at import.
Blank nodes outside RDF list structure. Collapsed at import.

Ontology stewards who need full OWL axiom fidelity should keep their source ontology as the truth and use FrameworX for operational data.

Runtime modifications and determinism

The exporter reads cold-start .dbsln values so the same solution produces the same graph every time. Runtime modifications to @Tag.X.Attributes made by scripts do NOT round-trip automatically. If you want runtime updates in the next export, run the promote_retentive_attributes MCP tool first. It copies the retentive overlay back into the cold-start columns.

No SPARQL push (10.1.5)

Direct POST-to-SPARQL-endpoint is not in 10.1.5. Upload the exported file to GraphDB / Stardog / Fuseki manually. Direct push is on the 10.1.6 roadmap.

Page tree