embabel realm import owl|skos|ossie|okf --out [--name ] [--mode auto|schema|terminology] [--sparql-endpoint ] [--data-url-base ] [--term-label ] [--ontology ] [--mapping ] [--jdbc-url ]
An ontology as a realm draft, with no appliance running. An OWL or RDFS file (Turtle, RDF/XML,
N-Triples or JSON-LD; a path, or an http(s) URL) becomes realm.ts, DERIVE rule sets under
rules/, ontology/alignment.yml recording which IRI every name came from, and IMPORT-REPORT.md,
in which every class, property and axiom lands as exact, inferred, noted or refused by name. The
contract is realm-spec’s OPEN_STANDARDS.md; the converter is the one in this appliance’s own
server image, beside realm-validate, so what it writes is what the server loads.
embabel realm import owl retail.ttl --out ./realm-retail --sparql-endpoint http://host.docker.internal:7878/queryembabel realm import owl https://current.geneontology.org/ontology/go-basic.owl --out ./realm-gene-ontology \ --term-label GoTerm --data-url-base https://raw.githubusercontent.com/me/realm-gene-ontology/main/embabel realm import owl schemaorg-current-https.ttl --out ./realm-catalogue \ --root Product --root Offer --root Organization # a subset of a wide vocabularyembabel realm validate ./realm-retail- A domain ontology (
--mode schema, the default for a few dozen classes): classes are types, properties are properties and edges, defining axioms are rules. Instances are not copied: each producer is a SPARQL query keyed by IRI against--sparql-endpoint, or a placeholder the report names. - A vocabulary (
--mode terminology, the default past a thousand classes): one type whose rows are the terms,IS_Aand the ontology’s relationships as edges both ways, served from CSV files under the draft’sdata/at--data-url-base. The Gene Ontology imports in seconds. owl:importsare followed, transitively: from--catalog(a directory of ontology files, or a Protégécatalog-v001.xml, which must be the file’s own directory) first, then fetched by IRI. Terms an ontology reuses from another vocabulary without importing it (PKO names PROV-O and Dublin Core terms this way; FIBO names OMG Commons) are defined from that vocabulary’s document, and only those terms.--imports catalognever fetches;--imports nonereads the file as it is. Every document resolved, and every one that was not, is a row in the report.- A class’s restrictions (
Party ⊑ ∃hasName.Name), which is how FIBO and most Protégé-written OWL declare their schema, are read as the edge or property they declare on the class, never as a rule. --root CLASS(repeatable; a local name or an IRI) imports a subset of a vocabulary too wide to want whole: each root, its subclasses and its ancestors, so a Schema.orgProductis still aThingand inheritsname. An edge whose range falls outside the subset is refused by name with the--rootthat would keep it, so the report is the list of what to add. Schema.org whole is a thousand classes and imports as a terminology; cut atProduct,OfferandOrganizationit is 207 types.schema:domainIncludesand Dublin Core’sdcam:domainIncludescount as domains.skos: a concept scheme (a Collibra or Atlan glossary, EuroVoc) is always a terminology: one type of terms withBROADER,RELATEDand the mapping relations as edges.ossie: an Apache Ossie semantic model, or its mapping document (which brings the ontology and the model it references, from the same directory), or a semantic model with--ontologyand--mappingbeside it. Datasets are types read bysqlproducers from a datasource the draft declares with a placeholderjdbcUrl(or--jdbc-url); relationships are edges both ways; metrics andderived_byaggregates become views with SQL’s null semantics.ai_contextlands inontology/ai-context.yml, never in a description.okf: an Open Knowledge Format bundle (Google’s context-set format: a directory of Markdown with YAML frontmatter, as Knowledge Studio exports). Table concepts with a# Schemabecome types read bysqlproducers from the bundle’s warehouse (--jdbc-url); join references become edges; every concept (metric, policy, computation, skill) is a queryableOkfConceptrecord with its trust tier, status and links; an Attested Computation is kept verbatim, never rewritten as a view.- A large realm is written in the YAML layout. Past 512 KiB of
realm.ts(FIBO Business Entities is 1.7 MB of it) the draft isrealm.ymlwithtypes/,producers/andviews/beside it, which the server reads file by file with no evaluation cap. A small realm stays onerealm.ts. - The source travels with the realm. Whatever was imported is copied, byte for byte, under
ontology/source/(the ontology, eachowl:importsdocument, the Ossie files, the bundle), andontology/SOURCE.mdsays what it is: its own title, version, licence and publisher as it declares them, the hash and size of each document, the import closure, and the command that regenerates the realm. A document over 32 MB is described rather than copied. - Exit status:
0done,1done with refusals (read the report),2could not run.

