On Thu, Sep 15, 2011 at 3:52 PM, Rupert Westenthaler <[email protected]> wrote: > On Thu, Sep 15, 2011 at 2:31 PM, Reto Bachmann-Gmür <[email protected]> wrote: >> Hello >> >> In the version of sling-stanbol[1] I've just pushed to github I'm >> adding all the enhancement to an MGraph. The idea is to allow queries >> on all the enhancements extracted from the jcr content. An issue is >> avoiding redundant information in the rdf store and the following >> questions arised: >> >> - Why do the resources of type fise:Enhancement have URIs? Do we >> expect that (rest) clients want to reference to such a resource? >> > > In case you want to provide feedback this might be the case. The training api I'd like to see would rather be stateless.
>> - What would a sound identity criterion for fise:EnhancementS be? I >> think none of the properties could be declared to be inverse >> functional, but maybe there is something like a "combined inverse >> functional property"? > > You are right that non of the properties is inverse functional. > I think even that there is nothing like a "combined inverse functional > property". > However there should not be two Enhancements from the same Engine (dc:creator) > with the same set of "dc:requires" and "dc:relation". > > See also the documentation of the currently used Enhancement Structure > at http://wiki.iks-project.eu/index.php/EnhancementStructure > > BTW: there is already an ongoing discussion about the next version of > the Enhancement Structure [1],[2],[3] Thanks for the comment and pointers, the code I just added[A] removes all enhancement for (extracted from) that resource. I think this should be fine as when a resource in the jcr repository is changed its metadata in the enhancement graph is update completely. Cheers, Reto [A] see https://github.com/IKS/sling-stanbol/blob/master/sling-stanbol-jcr-observer/src/main/java/org/apache/sling/stanbol/observer/EnhancingObserver.java line 191 > > [3] is the best source for a 3min Overview. In this picture > TextOccurrence maps to "TextAnnotation" in the current Enhancement > Structure and > EntityAnnotation maps also to "TextAnnotation" (they are split up to > allow multiple Occurrences > EntitySuggestion maps to "EnttiyAnnotation" in the current > Enhancement Structure. > > > best > Rupert > > [1] First Proposal > http://incubator.apache.org/stanbol/docs/trunk/enhancer/stanbolenhancementstructure.html > [2] Discussion: http://markmail.org/message/upzgzn5ew7cqa6ou > [3] Visualisation based on the Discussion: > http://creately.com/diagram/gkvbmoey1/UN4phlmAlny9qBWOPuN3u8qeVfE%3D > >> >> Cheers, >> Reto >> >> >> >> 1. https://github.com/IKS/sling-stanbol >> > > > > -- > | Rupert Westenthaler [email protected] > | Bodenlehenstraße 11 ++43-699-11108907 > | A-5500 Bischofshofen >
