Re: prefix management

Chris Mungall <[email protected]>
Newsgroups gmane.comp.ai.prolog.swi
Message-ID <CAN9AifuKjeNsD=0F6JRj=NG7G9r+inyfuGbeFdmJJmc83kC6dQ@mail.gmail.com>
Looks like you're using thea v1 - there is a newer version that handles
OWL2 ontologies, with a redesigned API:

https://github.com/vangelisv/thea

Not sure if that is affecting your NS issue. I would try first
experimenting with the core semweb libraries, parsing using rdf_load,
seeing if you get the expected behavior first


On Tue, Oct 22, 2013 at 7:33 AM, Michele Palmia <[email protected]> wrote:

> Hi everybody,
>
> I'm a newby of SWI-Prolog so sorry for huge mistakes and embarrassing
> questions.
> I'm trying to debug some problems with an owl  file I'm working with and
> I'm facing prefix issues in prolog. My prolog shell
> imports thea/owl_parser, semweb/rdf_db, semweb/rdf_edit, semweb/rdfs and
> semweb/owl.
>
> After parsing the owl file with
> ?- owl_parse('file_path.owl', false, false, true).
> I try to check if namespaces have been imported (because it seems like they
> didn't) using
> ?- rdf_current_prefix(A, B).
> or
> ?- rdf_current_ns(A,B).
>
> I get an error saying
> ERROR: toplevel: Undefined procedure: current_ns/2 (DWIM could not correct
> goal)
> in both cases.
>
> Calling
> ?- rdf_register_ns(test, 'somestring')
> on the other hand, works like a charm.
>
> Am I not using some libraries I should import? Am I calling the wrong
> construct?
> By the way, is it normal for owl_parse not to import namespaces? What
> should I change to let owl_parse import them?
>
> Thank you in advance,
> Michele Palmia
> Università degli Studi di Padova
> -------------- next part --------------
> HTML attachment scrubbed and removed
> _______________________________________________
> SWI-Prolog mailing list
> [email protected]
> https://lists.iai.uni-bonn.de/mailman/listinfo.cgi/swi-prolog
>
-------------- next part --------------
HTML attachment scrubbed and removed
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.