Versions Compared

Key

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

...

Bring an RDF/OWL ontology into FrameworX as UserTypes, Tags, and AssetTree folders.Standards Compliance How-toIndustrial Ontology → Import

Technical ReferenceSolutionDesignerSettings and ToolsImport Tags → OWL/RDF Ontology

...

Tip

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

Prerequisites

  • A solution open in Designer (new or existing).
  • A source file: RDF/JSON (.rj). JSON-LD and Turtle support arrives in 10.1.6.a future release.
  • (Optional) a policy template. Pick iof, isa88, or write your own JSON. Defaults work for generic OWL files.

...

  • Base-class cycles (A subClassOf B, B subClassOf A). FX single-parent BaseUserType does not model cycles. Neither class gets BaseUserType set. Duck-typed member copy-down still flattens members from both ancestors. Look for "cycle detected" in the warnings.
  • Multi-parent inheritance. OWL allows multiple parents. FX picks the first named parent for BaseUserType, the rest get warning-logged. All ancestors' members are still copied down.
  • Re-import collision. By default, user-authored Description text is preserved (descriptionCollisionPolicy: "skip"). Change to "overwrite" if the ontology is the source of truth.

...

Related: Industrial Ontology Integration How-to · Export your UNS to RDF/OWL/GraphDB · Generate a visual report of your UNS · Local AI Ontology Demo

...

Children Display
depth1