AI skill: import an RDF/OWL/ISA-88/ISA-95/IOF ontology file into the FrameworX Unified Namespace using the import_graph_model MCP tool.

AI Integration → Platform Skills Library → Import Industrial Ontology

When to invoke

• “Here's an IOF biopharma ontology. Build me the UDTs and tags”
• “I have a Turtle file from our corporate PIM. Import it”
• “Pull the ISA-88 master recipe from our GraphDB and materialize it”

Preconditions

1. Solution open in Designer (check via get_state).
2. User has AllowEditTags permission.
3. Source file reachable from Designer, OR an inline RDF/JSON string, OR a SPARQL endpoint URL.

Steps

1. Confirm the solution is the right target. If not, offer to create_solution or open_solution.
2. Pick a policy: iof for IOF ontologies, isa88 for batch hierarchies, custom-starter for unknown schemas. Ask the user if unsure.
3. Run dry-run first:

   import_graph_model(source="file", file_path="C:/.../file.rj", policy="iof", dry_run=true)

4. Summarize the dry-run to the user: class count, instance count, warnings[]. Flag cycles and multi-parent cases.
5. On user approval, re-run with dry_run=false.
6. Call generate_uns_visual(scope="full") to verify the imported structure visually.

Gotchas to surface

• Do NOT fabricate class or policy names. If the user describes an ontology without providing the file, ask for the path or the triples. Fabricated policy files are the #1 misuse mode.
• /Attr convention. Typed individuals become tags at <path>/<name>/Attr. Folders auto-create. Explain if the user is surprised by the trailing /Attr.
• Re-import collision. Default is skip (user edits win). Ask before switching to overwrite.
• Runtime Attributes do not round-trip automatically. Run promote_retentive_attributes first if the user expects them to.

See also

• Import an OWL/RDF ontology into your UNS. Human walkthrough for the Designer wizard path.
• Skill Export UNS as RDF. Reverse direction.
• Skill Generate UNS Visual. Verify the result.