Page History

Bring RDF/OWL ontologies into FrameworX as UserTypes, Tags, and AssetTree folders; round-trip the full Unified Namespace back to a graph file for diff, archive, or upload to a triple store.

How-to Guides → Compliance → Industrial Ontology

Standards Supported

The following W3C standards have first-class implementations in 10.1.5. Every row is backed by real parsing or emitting code in the graph import/export engine, not by marketing claim. Predicates listed here are consumed by the importer and restored by the exporter on round-trip.

Related and planned standards

Other standards that the ontology feature interacts with, or that are on the roadmap. These are documented here for context, not as first-class supported formats.

• Dublin Core Terms (dcterms:*, dc:*) — annotation predicates are round-tripped through the Attributes JSON column keyed as prefix:localName. No term-specific handling; every dcterms:* predicate is preserved uniformly as an opaque annotation.
• JSON-LD, Turtle, RDF/XML, and the .nt file form of N-Triples , RDF/XML — planned for a future release. Not supported in 10.1.5 as on-disk formats. The file dialog currently lists these filters; picking a non-.rj file results in an error or a silent fallback to RDF/JSON output. Use .rj for reliable file-based import and export. (Note: this concerns the on-disk wire formats only — the N-Triples conceptual model of the UNS is always available; see above.)
• SPARQL — the exporter can wrap its output in a SPARQL INSERT DATA {…} envelope for upload to a triple store. SELECT queries are the caller's job; the engine does not parse or evaluate SPARQL queries. Fetch query results through WebData and pass the response to the importer as inline content.
• SHACL, PROV-O, QUDT — not implemented. Shape validation, provenance tracking, and unit quantification are not performed by the import engine. If your source graph includes these vocabularies, their triples are either skipped or preserved as opaque annotations depending on predicate shape.

Policy templates shipped with the product

Two starter policy templates ship in 10.1.5 to simplify onboarding from well-known industrial vocabularies. Both are JSON configuration files consumed by the generic import engine — they set prefix mappings, module routing, typed-container predicates, and containment predicates, but do not introduce standard-specific code paths. Pick one as a starting point and edit the JSON to fit your ontology.

• IOF (Industrial Ontologies Foundry) — policy-iof.json. Real IOF IRIs: BFO_0000051 for containment, module routing for IOF_Core, IOF_Biopharma, IOF_SupplyChain, IOF_Construct, and the IOF_ prefix. Suitable as a starter for any IOF-derived ontology.
• ISA-88 (IEC 61512, batch control) — policy-isa88.json. s88: prefix, containment mappings (hasSite, hasArea, hasProcessCell, hasUnit, hasEquipmentModule), and a typeToUserType map covering the ISA-88 physical and procedural models. The Industrial Ontology Demo uses this template end-to-end.

FrameworX architecture and ontology alignment

The UNS is a triple store by construction. Every row in the Unified Namespace — every UserType, Tag, AssetTree folder, UDT member, and metadata value — corresponds to one or more RDF triples. N-Triples, the W3C line-based textual form of a triple (<subject> <predicate> <object> .), is the canonical way to read, reason about, and talk about UNS content. The triples are always present, stored directly in the UNS configuration; you do not need to export a file to see them. Parsing and emitting the .nt file on disk is a separate roadmap item — the underlying triple model, and its N-Triples textual form, is foundational and always available.

The Unified Namespace is the landing surface for imported ontology content. The mapping is intentionally small, so that graph files stay readable and round-trips stay symmetric:

• UserTypes hold class-level metadata. Every owl:Class becomes one row; rdfs:subClassOf sets BaseUserType; cycle detection prevents infinite loops; multi-parent OWL graphs pick the first named parent and duck-type the rest.
• Tags hold instance-level metadata. Every owl:NamedIndividual becomes one Tag at path <containmentPath>/<entityName>/Attr. The /Attr convention is enforced on import and stripped on export so that OWL entity IRIs reflect identity, not storage layout.
• AssetTree folders are materialized automatically from the slashed paths. The importer never writes folder rows directly.
• UDT members hold property-level metadata. Each owl:ObjectProperty or owl:DatatypeProperty on a class becomes one member; on export, the original predicate IRI is restored from the SourceIri column.
• Metadata columns preserve annotations. DisplayText, Labels, SourceIri, Description, and the Attributes JSON blob together hold everything a round-trip needs.

Related pages

• Import an OWL/RDF ontology into your UNS. Designer wizard and MCP reference for the import step, including the full OWL-to-FrameworX predicate mapping table.
• Export your UNS to RDF/OWL/GraphDB. Format selector, round-trip guarantees, and SPARQL INSERT DATA envelope details.
• Generate a visual report of your UNS. Relationship Graph button and Mermaid output reference.
• Industrial Ontology Demo. Reference solution shipping with 10.1.5 — a hand-authored ISA-88 mini-ontology that exercises every column in the 10.1.5 schema additions.

In this section...