On Thu, Aug 22, 2013 at 5:16 PM, Joseph M'Bimbi-Bene <jbi...@object-ive.com> wrote: > Hello, sorry for the late answer. > I am not sure i understand the problem (see my comments in your answer). > > > On Mon, Aug 19, 2013 at 2:53 PM, Rupert Westenthaler < > rupert.westentha...@gmail.com> wrote: > >> Hi Joseph, >> >> ATM the default type mappings can not be removed by the configuration. >> Via the configuration it is only possible to >> >> * change a mapping present in the default >> * add new mappings >> >> FYI the default mappings are >> >> dbp-ont:Organisation; dbp-ont:Newspaper; schema:Organization > >> dbp-ont:Organisation >> dbp-ont:Person; foaf:Person; schema:Person > dbp-ont:Person >> dbp-ont:Place; schema:Place; gml:_Feature > dbp-ont:Place >> skos:Concept > skos:Concept >> >> The main reason for having such defaults in the code is that in early >> version of the Engine it was not possible to configure type mappings >> at all. Now that one can configure such mappings it would be better to >> use no defaults and only populate the configuration form with those >> values. >> >> > Aren't the config of the engines parsed from these forms. I don't know much > of the inner mechanics of Stanbol, OSGi, etc. but i would expect the then > the forms to be populated by default and the parameters of the engine still > parsed from them.
The config is parsed from the forms and the forms are created from a XML file. The XML file is created at build time based on Java annotations. So basically their are two ways of having defaults: (1) defaults for a configuration parameter: This one is used of a configuration is not present. (2) default values in the form: Those are used to populate the configuration form. If the user does not remove/change those they will be parsed as actual configuration to the created OSGI component. > > >> The only reason while I can not do that easily is that such a change >> would have the consequence the currently used configuration will no >> longer have those mappings available. That means that most/all >> EntityLinkingEngine configurations that link agains dbpedia or an SKOS >> like vocabulary will lose their type mapping information. >> >> > But the engines are already created right ? So you might expect that their > configurations, unless you specifically change them via the config manager, > to remain the same. > And as i mentionned earlier, if the default parameters were just in the > forms and parsed from them, would this be a solution ? That is exactly the problem. The engines are already created so a change of the type (2) default would not be applied to them. However if we would change the type (1) defaults does affect them. So if I would move the current default from the code (type (2)) to the form (type (1)) newly created instances would not be affected. However the behavior of all existing instances would change. > > >> Because of that I would suggest to add an additional configuration >> parameter "enhancer.engines.linking.defaultTypeMappings". If set to >> "false" (default: true) this will deactivate the loading of the >> default type mappings. This would be a possibility to avoid this. best Rupert >> >> This ensures that current configuration are not affected while >> allowing users to deactivate the default mappings. >> >> WDYT >> Rupert >> >> p.s. I had not yet time to look into your other reported issue. >> >> On Fri, Aug 16, 2013 at 7:28 PM, Joseph M'Bimbi-Bene >> <jbi...@object-ive.com> wrote: >> > Hello everybody, I am having a proble with the type mapping of the >> > EntityHubLInkingEngine. >> > I already sent a mail in this list about using another predicate than >> > "rdf:type" to refer to the type of my entities and not having any >> > "entity-type" in the EntityAnnotation in the rdf result. >> > >> > This problem is still on with one of my site, so as a workaround i >> switched >> > back to the rdf:type predicate and introduced a banlist to avoid getting >> > anything in owl or skos vocabulary. A little annoying, but not dramatic. >> > >> > I am having another little problem still. I want to descibe people and >> > define them as people using the "http://dbpedia.org/ontology/Person"; >> > predicate as their type. >> > >> > I use the stanbol client and the way i retrieve response, I don't want >> the >> > type of the EntityAnnotation to be mapped to the "dc:type" of the >> > TextAnnotation. The problem is that even if i remove every type mapping, >> i >> > still get the type mapped in the TextAnnotation. >> > >> > -------------------------------- >> > >> > here is the text i used for the Enhancement: >> > "Bertrand DURAND Groupe EMI : Cellule Moteur de Recherche EDF – DSP / CSP >> > IT / DPM" >> > >> > here is the rdf decribing Bertrand Durand: >> > >> > <rdf:Description rdf:about=" >> http://www.edf.fr/EdfPeople.owl#DURAND_Bertrand >> > "> >> > <rdf:type>http://dbpedia.org/ontology/Person</rdf:type> >> > <skos:altLabel>Bertrand DURAND</skos:altLabel> >> > <skos:prefLabel>DURAND Bertrand</skos:prefLabel> >> > </rdf:Description> >> > >> > >> > Here is the TextAnnotation: >> > >> > <rdf:Description >> > rdf:about="urn:enhancement-12de8163-45c1-9fb8-1bb9-5e4a762d6c56"> >> > <j.4:selection-context xml:lang="fr">Bertrand DURAND Groupe EMI : >> > Cellule Moteur de Recherche</j.4:selection-context> >> > <j.1:type rdf:resource="http://dbpedia.org/ontology/Person"/> >> > <j.4:extracted-from >> > >> rdf:resource="urn:content-item-sha1-32737b14dc8e05f182138e882db2476a858560b3"/> >> > <j.4:confidence rdf:datatype=" >> http://www.w3.org/2001/XMLSchema#double >> > ">0.722500040531159</j.4:confidence> >> > <j.4:selected-text xml:lang="fr">Bertrand DURAND</j.4:selected-text> >> > <rdf:type rdf:resource=" >> http://fise.iks-project.eu/ontology/Enhancement >> > "/> >> > <rdf:type rdf:resource=" >> > http://fise.iks-project.eu/ontology/TextAnnotation"/> >> > <j.4:end rdf:datatype="http://www.w3.org/2001/XMLSchema#int >> > ">19</j.4:end> >> > <j.1:created rdf:datatype="http://www.w3.org/2001/XMLSchema#dateTime >> > ">2013-08-16T17:01:11.720Z</j.1:created> >> > <j.1:creator rdf:datatype="http://www.w3.org/2001/XMLSchema#string >> > >> ">org.apache.stanbol.enhancer.engines.entitylinking.engine.EntityLinkingEngine</j.1:creator> >> > <j.4:start rdf:datatype="http://www.w3.org/2001/XMLSchema#int >> > ">0</j.4:start> >> > </rdf:Description> >> > >> > And here is the configuration of the linking engine: >> > >> > enhancer.engines.linking.typeMappings=[""] >> > enhancer.engines.linking.labelField="rdfs:label" >> > enhancer.engines.linking.typeField="rdf:type" >> > >> > ------------------------------------- >> > >> > Hope it helps you improve Stanbol :) Have a nice day !! >> > best regards, Joseph >> >> >> >> -- >> | Rupert Westenthaler rupert.westentha...@gmail.com >> | Bodenlehenstraße 11 ++43-699-11108907 >> | A-5500 Bischofshofen >> -- | Rupert Westenthaler rupert.westentha...@gmail.com | Bodenlehenstraße 11 ++43-699-11108907 | A-5500 Bischofshofen
