Hi Rupert, I think the default configuration of this engine should use full IRIs for the properties rather than CURIEs. As not to allow ambiguity and not to rely on a an external service.
I'm also not sure if and how the CURIE spec requirement "The host language MUST provide one or more mechanisms for defining the mapping from the prefixto an IRI." is satisfied here. Cheers, Reto On Tue, Oct 15, 2013 at 7:32 PM, Rupert Westenthaler < rupert.westentha...@gmail.com> wrote: > Hi Adrian, > > > On Tue, Oct 15, 2013 at 6:17 PM, Adrian Gschwend <ml-...@netlabs.org> > wrote: > > Hi, > > > > Based on Retos Stanbol book I created a new enhancement engine for a > > SKOS vocabulary I created. > > > > This worked well with one exception: When I create a new "Apache Stanbol > > Enhancer Engine: Entityhub Linking" entry via the "+" it seems to create > > some default Type-Mappings like: > > > > dbp-ont:Organisation;\ dbp-ont:Newspaper;\ schema:Organization\ >\ > > dbp-ont:Organisation > > > > Once I add the enhancer to a chain it complains that my new enhancer is > > not available. In the log file I saw that it does not know the prefix > > dbp-ont so I deleted the entry till I didn't had any more issues, which > > were these prefixes: > > > > dbp-ont > > schema > > skos > > Prefix mappings are provided by the NamespacePrefixProvider. The > following implementations are available and included in the default > launcher configurations > > * stanbol provider > (org.apache.stanbol.commons.namespaceprefix.provider.stanbol): This > one defines a Java Enumeration [1] with all prefixes used by Stanbol. > This includes also the tree prefixes mentioned above > * prefix.cc provider > (org.apache.stanbol.commons.namespaceprefix.provider.prefixcc): This > service loads prefix mappings from http://http://prefix.cc > > In addition you can also use full URIs when configuring the type mappings > > > > > So basically I got rid of all the Type-Mappings now. > > > > I am not aware of any issues with type mappings. Illegal type mappings > are just ignored and logged. They should not affect other valid > mappings. > > > Is this a bug or is this a feature that the prefixes are not known? > > If the launcher you are using include the NamespacePrefixProvider and > the stanbol provider using the above prefixes should work. > > best > Rupert > > > [1] > http://svn.apache.org/repos/asf/stanbol/trunk/commons/namespaceprefix/stanbolprovider/src/main/java/org/apache/stanbol/commons/namespaceprefix/mappings/DefaultNamespaceMappingsEnum.java > > -- > | Rupert Westenthaler rupert.westentha...@gmail.com > | Bodenlehenstraße 11 ++43-699-11108907 > | A-5500 Bischofshofen >
