Versions Compared

Old Version 2

changes.mady.by.user admin

Saved on

compared with

New Version 3

changes.mady.by.user admin

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Relocated under Solution Export Reference: update breadcrumb, add N-Triples mental-model callout, expand Related to include main ontology reference page.

...

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 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 10.1.6a 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).

...

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 · Industrial Ontology Demo

...

Children Display
depth1