Search Mailing List Archives
[protege-dev] WebProtégé - deprecation of EntityData class
matthew.horridge at stanford.edu
Thu May 21 13:30:26 PDT 2015
Please don’t use any EntityData related structures at all. They will be removed at some point.
The mechanism for selection has also changed (you’ll find the changes in master) and it’s likely to evolve further. It’s possible that we could broaden the scope, but the selection mechanism is only really meant to apply to entities.
I suppose what you could do with is the ability to inject an arbitrary object into a portlet when it’s constructed. Unfortunately, this isn’t possible with the current infrastructure (it is actually possible in an incubator version of webprotege, but this is ages away from seeing the light of day). I’ll have a think of a way around this. Can you elaborate on your use case? Do you need a common object per project, per application or both?
> On 21 May 2015, at 06:58, Karl Hammar <karl at karlhammar.com> wrote:
> I'm a bit curious as to the future plans for the EntityData and Selectable interfaces in WebProtégé. In some of the work I'm doing I need to pass around things between portlets (e.g., employing the Selectable interfaces) which aren't necessarily OWL constructs, but rather URIs and strings, among other things for search engine integration purposes. I've so far been using EntityData objects, as supported by Selectable, for this. That is perhaps not ideal given the naming/purpose of the EntityData class, but it works all the same. However, the deprecation warnings on EntityData scare me a little.. so any comments on what's going to happen here in the future?
> protege-dev mailing list
> protege-dev at lists.stanford.edu
More information about the protege-dev