You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

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.

Technical ReferenceSolutionDesignerSettings and ToolsExport → UNS as RDF/OWL Graph


N-Triples as the mental model. The Unified Namespace is a triple store by construction. Every UserType, Tag, AssetTree folder, and member corresponds to one or more RDF triples of the form <subject> <predicate> <object> . — the W3C N-Triples textual form. The export here is a serialization step onto that underlying triple model. See Industrial Ontology Integration How-to for the full standards map.

Primary path: the Export Tags format selector

  1. In Designer, open the Unified Namespace → Tags page.
  2. Click Export Tags on the toolbar.
  3. 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 a future release.
  4. Pick a policy if you imported with one (same file as the importer).
  5. 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 a future roadmap.


Related: Industrial Ontology Integration How-to · Import an OWL/RDF ontology into your UNS · Generate a visual report of your UNS · Industrial Ontology Demo


  • No labels