Hi, Adrian,
I can reproduce your problem. I think the problem is that ontop plugin
sometimes does not aware that the imports have been changed by the
Protege. We will look into this issue further.
I have a quick workaround now. After you add the imports and the
prefixes in the Protege (your step 2), save the ontology and restart
the Protege.
Now ontop should be able to handle the prefixes properly as in the
attached snapshots. I hope this will solve your problem.
Best,
Guohui
PS: I also cc this email to the mail list, as other users might have
the same issue.
On Wed, Apr 16, 2014 at 11:12 AM, Adrian Brasoveanu
<
adrian.b...@gmail.com> wrote:
> Hello Guohoi,
>
> Thanks for your quick answer. I was travelling by train last night and had a
> bad Internet connection.
>
> Here are the steps I do when I get the error (they can be done in about 1
> minute):
>
> Step 1 - I create a new ontology, add a namespace to it and import 2
> ontologies,
> let's say FOAF and QB
>
> Step 2 - I put the right namespaces for FOAF and QB as Protege doesn't seem
> to make the binding correctly.
>
> Step 3 - I create a mapping like :{Person} a foaf:Person . and I get the
> error.
>
> I attach pictures for each step.
>
> It might be that I'm missing a simple step, but if I am missing a step, I
> don't find it in the new documentation.
>
> Best regards,
> Adrian