Search Mailing List Archives
[protege-dev] WebProtégé - update object property frame inverses
matthew.horridge at stanford.edu
Tue May 5 11:31:50 PDT 2015
I think we considered showing inverses in the simple UI (which is what the frames are intended for) but then decided against this. The inverses should probably be removed from the frame rather than being added to the frame translator. If you want to clean this up please feel free to do so and issue a pull request.
> On 5 May 2015, at 05:14, Karl Hammar <karl at karlhammar.com> wrote:
> I'm looking into how to in WebProtégé update object properties using the Dispatch service with UpdateObjectActions and ObjectPropertyFrame objects.
> I've noted that the corresponding translator, ObjectPropertyFrameTranslator, that from such frame objects generates axioms for storage in the ontology, does not generate or parse owl:inverseOf statements. The ObjectPropertyFrame class itself however has an "inverses" member variable of the expected type (a Set of OWLObjectProperty:s).
> Is there a reason for this mismatch between the frame class and its translator class, and would you like for me to try and fix it? That would enable object property inverses to be modified using the dispatch service, just as ranges, domains, and annotations currently can be modified.
> protege-dev mailing list
> protege-dev at lists.stanford.edu
More information about the protege-dev