Versions Compared

Old Version 2

changes.mady.by.user admin

Saved on

compared with

New Version Current

changes.mady.by.user admin

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Update format selector to all four W3C RDF formats now shipping in 10.1.5 GA; rename Export Tags ? Export UNS

...

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

Technical Reference → Solution → Designer → Settings and Tools → Export → UNS as RDF/OWL Graph

...

Tip

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

...

UNS format selector

  1. In Designer, open the Unified Namespace → Tags page Solution → Export.
  2. Click Export TagsUNS on the toolbar.
  3. In the Format dropdown pick one of:
    • JSON. The standard FX tag export (no graph expansion)FrameworX-native multi-file dump (UnsUserTypes.json, UnsTags.json, etc.). Round-trips with the FrameworX importer; not a graph format.
    • RDF/JSON (.rj, application/rdf+json). W3C RDF/JSON. Default for graph round-tripNiche but stable; loaded by dotNetRDF, GraphDB, Stardog, Fuseki.
    • JSON-LD (.jsonld, application/ld+json). Falls back to RDF/JSON in 10.1.5 with a warning. Native emitter ships in 10.1.6.
  4. Pick a policy if you imported with one (same file as the importer).
    • JSON-LD 1.1 flattened form with @context and @graph. Mainstream modern format — schema.org, every major triple store, every LD client library.
    • Turtle (.ttl, text/turtle). The most-used RDF format in industrial-ontology workflows (IOF, ISA-88). Most readable for humans.
    • N-Triples (.nt, application/n-triples). One fully-expanded triple per line. Most universally accepted; best for diff and audit.
  6. Click Export UNS. The output Click Export. The file lands in the solution's Exchange folder as under <SolutionName>_UNS_Graph<TAG>/UnsExport.rj (or .jsonld)<ext> (folder tags: RDF, JSONLD, TTL, NT; the plain JSON choice writes to <SolutionName>_UNS/ as multiple per-table files).
Note

Round-trip is currently RDF/JSON-only. All four W3C formats are fully implemented on the export side. The importer in 10.1.5 reads RDF/JSON only; JSON-LD, Turtle, and N-Triples readers ship in a follow-up release. If you need to re-import what you exported, use RDF/JSON end-to-end. Publishing to a triple store, sharing with an ontology team, or archiving — pick whichever format your destination accepts.

Alternative path: AI-driven via the MCP tool

Code Block
languagenone
export_graph_model(format="rj", policy="iof")
# Aliases accepted: jsonld | json-ld | turtle | ttl | ntriples | n-triples | nt

See skill Skill Export UNS as RDF.

...

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 a future roadmap.

...

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

...

Children Display
depth1