Interface HasApplyChanges

All Known Subinterfaces:
OWLMutableOntology, OWLOntology, OWLOntologyManager
All Known Implementing Classes:
ConcurrentOWLOntologyImpl, OWLImmutableOntologyImpl, OWLOntologyImpl, OWLOntologyManagerImpl

public interface HasApplyChanges
Since:
3.5
Author:
Matthew Horridge, Stanford University, Bio-Medical Informatics Research Group
  • Method Details

    • applyChanges

      default ChangeApplied applyChanges(List<? extends OWLOntologyChange> changes)
      Applies a list ontology changes to a collection of ontologies. When this method is used through an OWLOntologyManager implementation, the instance used should be the one that the ontology returns through the getOWLOntologyManager() call. The reason is that some changes, e.g., change of ontology id and change of imports directives, affect data that only that manager instance knows about, such as the imports closure; changes of ontology id through the wrong manager will make the ontology unreachable through its new id in the manager associated with the ontology. Configuration for loading and saving parameters is also held by the manager, if not explicitly specified for the ontology. While the change might be successful, other bugs might be made apparent later.
      Parameters:
      changes - The changes to be applied.
      Returns:
      ChangeApplied.SUCCESSFULLY if the axiom is added, ChangeApplied.UNSUCCESSFULLY otherwise.
      Throws:
      OWLOntologyChangeException - If one or more of the changes could not be applied.
    • applyChanges

      default ChangeApplied applyChanges(OWLOntologyChange... changes)
      Applies a list ontology changes to a collection of ontologies. When this method is used through an OWLOntologyManager implementation, the instance used should be the one that the ontology returns through the getOWLOntologyManager() call. The reason is that some changes, e.g., change of ontology id and change of imports directives, affect data that only that manager instance knows about, such as the imports closure; changes of ontology id through the wrong manager will make the ontology unreachable through its new id in the manager associated with the ontology. Configuration for loading and saving parameters is also held by the manager, if not explicitly specified for the ontology. While the change might be successful, other bugs might be made apparent later.
      Parameters:
      changes - The changes to be applied.
      Returns:
      ChangeApplied.SUCCESSFULLY if the axiom is added, ChangeApplied.UNSUCCESSFULLY otherwise.
      Throws:
      OWLOntologyChangeException - If one or more of the changes could not be applied.
    • applyChangesAndGetDetails

      ChangeDetails applyChangesAndGetDetails(List<? extends OWLOntologyChange> changes)
      Applies a list ontology changes to a collection of ontologies. When this method is used through an OWLOntologyManager implementation, the instance used should be the one that the ontology returns through the getOWLOntologyManager() call. The reason is that some changes, e.g., change of ontology id and change of imports directives, affect data that only that manager instance knows about, such as the imports closure; changes of ontology id through the wrong manager will make the ontology unreachable through its new id in the manager associated with the ontology. Configuration for loading and saving parameters is also held by the manager, if not explicitly specified for the ontology. While the change might be successful, other bugs might be made apparent later.
      Parameters:
      changes - The changes to be applied.
      Returns:
      ChangeApplied.SUCCESSFULLY if the axiom is added, ChangeApplied.UNSUCCESSFULLY otherwise.
      Throws:
      OWLOntologyChangeException - If one or more of the changes could not be applied.
    • applyChangesAndGetDetails

      default ChangeDetails applyChangesAndGetDetails(OWLOntologyChange... changes)
      Applies a list ontology changes to a collection of ontologies. When this method is used through an OWLOntologyManager implementation, the instance used should be the one that the ontology returns through the getOWLOntologyManager() call. The reason is that some changes, e.g., change of ontology id and change of imports directives, affect data that only that manager instance knows about, such as the imports closure; changes of ontology id through the wrong manager will make the ontology unreachable through its new id in the manager associated with the ontology. Configuration for loading and saving parameters is also held by the manager, if not explicitly specified for the ontology. While the change might be successful, other bugs might be made apparent later.
      Parameters:
      changes - The changes to be applied.
      Returns:
      ChangeApplied.SUCCESSFULLY if the axiom is added, ChangeApplied.UNSUCCESSFULLY otherwise.
      Throws:
      OWLOntologyChangeException - If one or more of the changes could not be applied.