write_owl

write_owl(mappings: Iterable[SemanticMapping], file: str | Path | TextIO | None = None, *, converter: Converter, mode: Literal['bridge', 'inline'] | None = None, metadata: MappingSet | None = None, minimum_confidence: float | None = None, mapping_annotations: bool = False, declarations: bool = False, allow_arbitrary: bool = False, generation_comment: bool = True, iri: str | None = None, negation_workflow: bool = False, **kwargs: Any) → None

Write OWL bridge axioms as an OWL file.

Parameters:

• mappings – semantic mappings

• file – path to file or a file-like object. If none given, prints to stdout

• converter – a converter

• mode –

  Which kinds of axioms should be produced?

  • inline produces annotation properties as is

  • bridge applies transformation on SKOS matches to upgrade them to logical axioms, where possible, based on https://github.com/INCATools/ontology-development-kit/issues/626#issuecomment-3285032670. Note, this will automatically invert skos:narrowMatch mappings

• metadata – metadata to annotate to the “ontology”

• minimum_confidence – minimum confidence level to keep for exporting as a bridge

• mapping_annotations – whether to include annotations (extra metadata like mapping type, confidence, etc.) on the produced axioms, defaults to false :param

• declarations – whether to include declarations (and labels, if available)

• allow_arbitrary – When in inline mode, if set to true, skip mappings with predicates that aren’t in curies.vocabulary.extended_match_typedefs

• generation_comment – if true, include an ontology-level annotation for the date when this was generated

• iri – the IRI for the resulting ontology. if not given, reuses the metadata’s ID, if available.

• negation_workflow – Whether to assume that the curation of a negative exact match or equivalence mapping should be used to imply a disjointness axiom.

• kwargs – keyword arguments to pass to functional_owl.write_ontology().