| Info |
|---|
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. |
Bring an RDF/OWL ontology into FrameworX as UserTypes, Tags, and AssetTree folders.
Technical Reference → Solution → Designer → Settings and Tools → Import Tags → OWL/RDF Ontology
Version 10.1.
...
5+
...
| 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 |
Prerequisites
- A solution open in Designer (new or existing).
- A source file: RDF/JSON (
.rj). JSON-LD and Turtle support arrives in 10.1.6a 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-parentBaseUserTypedoes not model cycles. Neither class getsBaseUserTypeset. 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
Descriptiontext 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 | ||
|---|---|---|
|