Hi Fabian, On Wed, May 9, 2012 at 12:39 AM, Fabian Christ <[email protected]> wrote: > 2012/5/9 Bertrand Delacretaz <[email protected]>: >>... >> interface Category { >> String getId(); >> String getLabel(); >> Category getParent(); >> } > > So for each type of enhancement you would have an interface - is this > the idea?...
Yes, so that a user can say "I'd like to add Categories to this content" or "I'm looking for Entities in my content", etc. > ...Can you explain how this corresponds to the enhancement > structure defined ones at [1]? ... I purposely didn't take that into account - my starting point is "what API would make Stanbol and similar services really easy to use for people who are not familiar with this stuff". But now that you ask, let's try: > ...What kind of information will become an > interface - is it the dc:type?... Looking at [1] the dc:types are for example "heading, section, sentence, Language, Location, Person, Location, Entity". I think I'm looking at something different - if I'm asking for Topic (a SINR interface) for example, my question is "which Topics does my content relate to, as a whole" and the answer might be "human rights, finance, countries/USA". If I'm asking for Entities, on the other hand, the question is "please point me to known entities in my content" and the answer might be "Barack Obama (from character index 12 to 23 and 146 to 150), USA (from character index 27 to 30)". So far, I haven't looked at how we would implement this...just trying to get it right at the API level. I imagine we might need different interpretations of the enhancement results to produce the above answers. -Bertrand > [1] http://wiki.iks-project.eu/index.php/EnhancementStructure
