From christoph.lange at uni-bremen.de Mon Jan 23 14:59:46 2012 From: christoph.lange at uni-bremen.de (Christoph LANGE) Date: Mon, 23 Jan 2012 14:59:46 +0100 Subject: [Hets-users] [Hets-devel] How do I reuse an OWL ontology (in an RDF/XML file) in a heterogeneous spec? In-Reply-To: <4F1D38F4.3020508@dfki.de> References: <4F199B46.6090904@uni-bremen.de> <4F19C2A3.1030206@informatik.uni-bremen.de> <4F1A173C.3000309@uni-bremen.de> <4F1D38F4.3020508@dfki.de> Message-ID: <4F1D67D2.5010106@uni-bremen.de> Hi Christian, let me Cc hets-users, maybe this is relevant for someone else as well. 2012-01-23 11:39 Christian Maeder: > Am 21.01.2012 02:39, schrieb Christoph LANGE: >> With Hets [converting an OWL RDF/XML ontology to OWL Manchester] didn't work for me. I installed Hets from the sources >> according to the instructions in README; just that I didn't understand >> what this concretely means: >> >>> Further environment variables for provers are: >>> >>> ... >>> HETS_OWL_TOOLS >> >> Trying to run "hets -g OpenAALOntology.owl" without having that variable >> set gives me the error "OWL2Parser.jar not found". >> >> Indeed there is no such JAR, so I have to build it. I found out that >> there is an undocumented target "make java-libs", but that doesn't work. >> It expects an OWL API directory in some directory that I don't have: >> >>> $ make java-libs > > The proper target is "initialize_java", to get the API-sources first. OK, thanks ? good to know! Maybe you could document that somewhere. > On our machines (fb3) HETS_OWL_TOOLS is (should be) set to > /home/linux-bkb/hets-owl-tools. Under Ubuntu it is: > > export HETS_OWL_TOOLS=/usr/lib/hets/hets-owl-tools > > (via utils/debian/auto-package/debian/natty/hets_script) I build Hets manually from the sources. Maybe Hets assumes a reasonable default for that variable, or otherwise I will see where the OWL tools end up after running "make" and set the variable accordingly. >> BTW, another final thing I have not yet fully understood is that library >> paths seem to be "semi-absolute" in a way, i.e. I made that part of >> AAL.het work by writing >> >> library AAL >> from OpenAALOntology get OpenAAL >> >> and then calling "hets -g AAL.het". However I can't call Hets from other >> directories. >> >> Other examples in Hets-lib use the whole directory path below "Hets-lib" >> as library identifiers, and then you have to run Hets from the >> "Hets-lib" directory. > > You can add several directories to the HETS_LIB variable (separated by > colon). Please report possible errors. I rather wondered about library paths from the perspective of maintaining the Hets-lib repository ? not from the perspective of running Hets. But it's good to know that the HETS_LIB variable exists. I haven't used it so far; I guess Hets assumed some default, maybe "../Hets-lib" from the Hets directory. Cheers, Christoph -- Christoph Lange, Universit?t Bremen http://kwarc.info/clange, Skype duke4701 My up-to-date presentations: http://www.slideshare.net/langec From christoph.lange at uni-bremen.de Wed Jan 25 18:41:48 2012 From: christoph.lange at uni-bremen.de (Christoph LANGE) Date: Wed, 25 Jan 2012 18:41:48 +0100 Subject: [Hets-users] Specification of 'SPEC with logic TRANSLATION' syntax Message-ID: <4F203EDC.9020800@uni-bremen.de> Hi Till, hi all, so far I had the wrong assumption that in HetCASL it is not (yet) possible to choose a specific translation for a view within HetCASL code (instead of just on the GUI). (@Till, e.g. in today's OntoIOp phone call I said so, and you corrected me.) From searching Hets-lib I found out that the abstract syntax feature is LOGIC-REDUCTION, but from the examples I don't completely understand how it's used. IIUC the HetCASL Summary says that it refers to a morphism (or to a _co_morphism?). When grepping Hets-lib for the concrete syntax "with logic", I see three variants. Could you explain to me what they mean, and (maybe off-list) which one we would need for OntoIOp? * SPEC with logic SourceLogic2TargetLogic * SPEC with logic SourceLogic -> TargetLogic * SPEC with logic -> TargetLogic Cheers, and thanks, Christoph -- Christoph Lange, Universit?t Bremen http://kwarc.info/clange, Skype duke4701 My up-to-date presentations: http://www.slideshare.net/langec From Till.Mossakowski at dfki.de Thu Jan 26 16:05:13 2012 From: Till.Mossakowski at dfki.de (Till Mossakowski) Date: Thu, 26 Jan 2012 16:05:13 +0100 Subject: [Hets-users] Specification of 'SPEC with logic TRANSLATION' syntax In-Reply-To: <4F203EDC.9020800@uni-bremen.de> References: <4F203EDC.9020800@uni-bremen.de> Message-ID: <4F216BA9.1000906@dfki.de> Hi Christoph, > so far I had the wrong assumption that in HetCASL it is not (yet) > possible to choose a specific translation for a view within HetCASL code > (instead of just on the GUI). > > (@Till, e.g. in today's OntoIOp phone call I said so, and you corrected > me.) > > From searching Hets-lib I found out that the abstract syntax feature is > LOGIC-REDUCTION, No, you need LOGIC-TRANSLATION but from the examples I don't completely understand how > it's used. IIUC the HetCASL Summary says that it refers to a morphism > (or to a _co_morphism?). LOGIC-TRANSLATION refers to a comorphism LOGIC-REDUCTION refers to a morphism (however, it has not been fully implemented yet). It wil be used for projections to a sublogic. > When grepping Hets-lib for the concrete syntax "with logic", I see three > variants. Could you explain to me what they mean, and (maybe off-list) > which one we would need for OntoIOp? > > * SPEC with logic SourceLogic2TargetLogic We definitely need this one in OntoIOp, as it calls a logic translation by its name. This is needed for using non-default logic translations. > * SPEC with logic SourceLogic -> TargetLogic > * SPEC with logic -> TargetLogic These syntaxes invoke the default logic translation from SourceLogic to TargetLogic. The second one omits SourceLogic since this is known from the context. We need at least one variant for OntoIOp. Best, Till -- Prof. Dr. Till Mossakowski Cartesium, room 2.51 Phone +49-421-218-64226 DFKI GmbH Bremen Fax +49-421-218-9864226 Cyber-Physical Systems Till.Mossakowski at dfki.de Enrique-Schmidt-Str. 5, D-28359 Bremen http://www.informatik.uni-bremen.de/~till/ Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH principal office, *not* the address for mail etc.!!!: Trippstadter Str. 122, D-67663 Kaiserslautern management board: Prof. Wolfgang Wahlster (chair), Dr. Walter Olthoff supervisory board: Prof. Hans A. Aukes (chair) Amtsgericht Kaiserslautern, HRB 2313