From david.legg at searchevent.co.uk Fri Oct 10 03:47:31 2008 From: david.legg at searchevent.co.uk (David Legg) Date: Fri, 10 Oct 2008 11:47:31 +0100 Subject: [Mulgara-general] SPARQL/Update announcement Message-ID: <48EF32C3.3030209@searchevent.co.uk> This is probably old news to some of you but I thought this addition to SPARQL syntax looks very interesting... http://www.w3.org/Submission/2008/SUBM-SPARQL-Update-20080715/ If it became standard it looks like From david.legg at searchevent.co.uk Fri Oct 10 03:50:55 2008 From: david.legg at searchevent.co.uk (David Legg) Date: Fri, 10 Oct 2008 11:50:55 +0100 Subject: [Mulgara-general] SPARQL/Update announcement In-Reply-To: <48EF32C3.3030209@searchevent.co.uk> References: <48EF32C3.3030209@searchevent.co.uk> Message-ID: <48EF338F.3040504@searchevent.co.uk> Gah! > If it became standard it looks like > ... random mouse clicks can be so dangerous ;-) I was going to say it looks very useful. Regards, David Legg From gearon at ieee.org Fri Oct 10 22:00:53 2008 From: gearon at ieee.org (Paul Gearon) Date: Sat, 11 Oct 2008 00:00:53 -0500 Subject: [Mulgara-general] SPARQL/Update announcement In-Reply-To: <48EF32C3.3030209@searchevent.co.uk> References: <48EF32C3.3030209@searchevent.co.uk> Message-ID: Yes, this is planned. It's a matter of time and availability. It should be easy for us, since each of the operations are already supported with TQL syntax. Since we can also do SPARQL "where" clauses then that part is covered too. Paul On Fri, Oct 10, 2008 at 5:47 AM, David Legg wrote: > This is probably old news to some of you but I thought this addition to > SPARQL syntax looks very interesting... > > http://www.w3.org/Submission/2008/SUBM-SPARQL-Update-20080715/ > > If it became standard it looks like > _______________________________________________ > Mulgara-general mailing list > Mulgara-general at mulgara.org > http://mulgara.org/mailman/listinfo/mulgara-general > From gearon at ieee.org Thu Oct 16 22:38:14 2008 From: gearon at ieee.org (Paul Gearon) Date: Fri, 17 Oct 2008 00:38:14 -0500 Subject: [Mulgara-general] Mulgara 2.0.6 released Message-ID: I am pleased to announce the release of Mulgara version 2.0.6. Mulgara can be downloaded at: http://mulgara.org/download.html Features to note in this release are: - A servlet providing a SPARQL Protocol endpoint. - SPARQL support in the Web User Interface. - Improvements to the storage layer, speeding up large loads, while using less space and fewer files. This release also addresses an administrative error in the last two releases where binaries were created for Java 6 instead of Java 5. Full details can be found at: http://mulgara.org/release.html#v2.0.6 Bug reports and feature requests can be logged with our tracking system at: http://mulgara.org/trac/newticket Regards, Paul Gearon From gearon at ieee.org Fri Oct 17 09:14:12 2008 From: gearon at ieee.org (Paul Gearon) Date: Fri, 17 Oct 2008 11:14:12 -0500 Subject: [Mulgara-general] New WebUI Message-ID: Hi everyone, This WebUI in Mulgara has recently undergone a complete re-write, making it much lighter weight. However, we have endeavoured to keep all the old functionality unchanged. There are also some substantial new features that should be of interest to most users. The WebUI is accessed by pointing a browser to a host running a standalone Mulgara instance. By default, Mulgara runs its web services on port 8080, so you'll usually use a URL of: http://localhost:8080/webui Cosmetically, you'll see that we now use a style similar to the mulgara.org website. But the real changes are under the hood. The first major change is that the Query box now autodetects SPARQL. This lets you type any SPARQL query, and it will execute as normal. We are still working on 100% SPARQL compliance, but this has been steadily improving all year. TQL commands and queries still work exactly the same, so if you never use SPARQL you will not see the difference. Next, graph URIs need no longer look like: rmi://host/server#name Instead, *any* valid absolute URI can be used (relative URIs are coming). This means you can create and use graphs with names like: http://yourdomain.com/mydata urn:www.agxml.org:schemas:all:2:0 foo:bar If you create a graph with a given URI then you can insert and select from it as usual. Mulgara also offers the option of querying graphs that you haven't defined. If the URI of the graph is a URL that Mulgara understands, then it will attempt to retrieve data from that source and interpret it accordingly (through the mechanism we call "Resolvers"). For instance, you can find out the all the classes in RDF by querying the ontology published at the location described in the RDF namespace URL: select $class from where $class ; Finally, the Graph URI field is now used as the default graph for SPARQL queries. This field is initially set for the "Example Queries", and has always been used as a location for resources returned from a query, allowing URIs in results to be linked to queries about those resources. While this has not changed, SPARQL queries which do not define a FROM clause will also use this field as the location for the data being queried. When combined with the URL resolution above, this makes it easy to do things like testing the DAWG test cases, such as the one at: http://www.w3.org/2001/sw/DataAccess/tests/r2#dawg-triple-pattern-003 Set the Graph URI to: http://www.w3.org/2001/sw/DataAccess/tests/data-r2/triple-match/data-02.ttl Type the test query into the Query Text field: SELECT * WHERE { ?a ?a ?b . } The results are then rendered in the WebUI table layout. We hope you like these new features. Many of them are quite new, so we look forward to bug reports and feature requests. Regards, Paul Gearon From subs at rdfined.dk Wed Oct 22 05:37:30 2008 From: subs at rdfined.dk (Rune Stilling) Date: Wed, 22 Oct 2008 14:37:30 +0200 Subject: [Mulgara-general] "Could not commit creation of model ..." Message-ID: <44C65E5E-A294-411B-B95B-E41C9A89207F@rdfined.dk> Hi I'm trying to get some Krule up and running, but I stumble when I try to create a typemodel or prefixmodel: create ; I just get the error: Error: Could not commit creation of model rmi://...:8089/ server1#type of type http://mulgara.org/mulgara#TypeModel I have tried both IP-addresse, localhost and machine name. I'm also perfectly able to create other models except for those of some type. What's wrong? \Rune From subs at rdfined.dk Wed Oct 22 07:17:49 2008 From: subs at rdfined.dk (Rune Stilling) Date: Wed, 22 Oct 2008 16:17:49 +0200 Subject: [Mulgara-general] "Could not commit creation of model ..." In-Reply-To: <44C65E5E-A294-411B-B95B-E41C9A89207F@rdfined.dk> References: <44C65E5E-A294-411B-B95B-E41C9A89207F@rdfined.dk> Message-ID: <3569FCE4-06BD-4DDB-BE51-4E252F5D8D56@rdfined.dk> BTW - Here's the exception: 2008-10-22 16:15:56,439 WARN [execThread] itql.TqlSession - Couldn't execute command org.mulgara.query.QueryException: Could not commit creation of model rmi://88.80.197.184:8089/server1#type of type http://mulgara.org/ mulgara#TypeModel at org.mulgara.resolver.DatabaseSession.execute(DatabaseSession.java: 754) at org.mulgara.resolver.DatabaseSession.createModel (DatabaseSession.java:512) at org.mulgara.server.rmi.SessionWrapperRemoteSession.createModel (SessionWrapperRemoteSession.java:322) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source) at sun.rmi.transport.Transport$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Unknown Source) at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown Source) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer (StreamRemoteCall.java:247) at sun.rmi.transport.StreamRemoteCall.executeCall (StreamRemoteCall.java:223) at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126) at org.mulgara.server.rmi.RemoteSessionImpl_Stub.createModel(Unknown Source) at org.mulgara.server.rmi.RemoteSessionWrapperSession.createModel (RemoteSessionWrapperSession.java:438) at org.mulgara.query.operation.CreateGraph.execute(CreateGraph.java:83) at org.mulgara.itql.TqlAutoInterpreter.executeCommand (TqlAutoInterpreter.java:114) at org.mulgara.itql.TqlSession.executeCommand(TqlSession.java:242) at org.mulgara.itql.TqlSessionUI$ExecutionThread.run (TqlSessionUI.java:701) Caused by: org.mulgara.query.QueryException: org.mulgara.query.MulgaraTransactionException: Transaction rollback triggered at org.mulgara.resolver.MulgaraInternalTransaction.implicitRollback (MulgaraInternalTransaction.java:516) at org.mulgara.resolver.MulgaraInternalTransaction.execute (MulgaraInternalTransaction.java:627) at org.mulgara.resolver.DatabaseSession.execute(DatabaseSession.java: 751) at org.mulgara.resolver.DatabaseSession.createModel (DatabaseSession.java:512) at org.mulgara.server.rmi.SessionWrapperRemoteSession.createModel (SessionWrapperRemoteSession.java:322) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source) at sun.rmi.transport.Transport$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Unknown Source) at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown Source) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: org.mulgara.query.QueryException: Couldn't find resolver factory in internal resolver map http://mulgara.org/mulgara#TypeModel at org.mulgara.resolver.CreateModelOperation.execute (CreateModelOperation.java:103) at org.mulgara.resolver.MulgaraInternalTransaction.execute (MulgaraInternalTransaction.java:623) ... 17 more Den 22/10/2008 kl. 14.37 skrev Rune Stilling: > Hi > > I'm trying to get some Krule up and running, but I stumble when I try > to create a typemodel or prefixmodel: > > create mulgara#TypeModel>; > > I just get the error: > > Error: Could not commit creation of model rmi://...:8089/ > server1#type of type http://mulgara.org/mulgara#TypeModel > > I have tried both IP-addresse, localhost and machine name. I'm also > perfectly able to create other models except for those of some type. > > What's wrong? > > \Rune > > _______________________________________________ > Mulgara-general mailing list > Mulgara-general at mulgara.org > http://mulgara.org/mailman/listinfo/mulgara-general From DMS at viewpointusa.com Wed Oct 22 07:24:46 2008 From: DMS at viewpointusa.com (David Smith) Date: Wed, 22 Oct 2008 10:24:46 -0400 Subject: [Mulgara-general] "Could not commit creation of model ..." In-Reply-To: <3569FCE4-06BD-4DDB-BE51-4E252F5D8D56@rdfined.dk> References: <44C65E5E-A294-411B-B95B-E41C9A89207F@rdfined.dk> <3569FCE4-06BD-4DDB-BE51-4E252F5D8D56@rdfined.dk> Message-ID: <690E83C1D15F5B4D84ACDAC9D0C1FD87014C42AD@ROCHESTER01.viewpoint.local> Use: http://mulgara.org/mulgara#TypeGraph I found it by looking at the built in models with this query: select $subject $predicate $object from where $subject $predicate $object; As you can see, there is also a "built in" type model named: "sys:type" This was probably introduced in 2.0.6 with the change from the work "Model" to "Graph" --- SPARQLism Dave Smith -----Original Message----- From: mulgara-general-bounces at mulgara.org [mailto:mulgara-general-bounces at mulgara.org] On Behalf Of Rune Stilling Sent: Wednesday, October 22, 2008 10:18 AM To: Mulgara General Subject: Re: [Mulgara-general] "Could not commit creation of model ..." BTW - Here's the exception: 2008-10-22 16:15:56,439 WARN [execThread] itql.TqlSession - Couldn't execute command org.mulgara.query.QueryException: Could not commit creation of model rmi://88.80.197.184:8089/server1#type of type http://mulgara.org/ mulgara#TypeModel at org.mulgara.resolver.DatabaseSession.execute(DatabaseSession.java: 754) at org.mulgara.resolver.DatabaseSession.createModel (DatabaseSession.java:512) at org.mulgara.server.rmi.SessionWrapperRemoteSession.createModel (SessionWrapperRemoteSession.java:322) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source) at sun.rmi.transport.Transport$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Unknown Source) at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown Source) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer (StreamRemoteCall.java:247) at sun.rmi.transport.StreamRemoteCall.executeCall (StreamRemoteCall.java:223) at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126) at org.mulgara.server.rmi.RemoteSessionImpl_Stub.createModel(Unknown Source) at org.mulgara.server.rmi.RemoteSessionWrapperSession.createModel (RemoteSessionWrapperSession.java:438) at org.mulgara.query.operation.CreateGraph.execute(CreateGraph.java:83) at org.mulgara.itql.TqlAutoInterpreter.executeCommand (TqlAutoInterpreter.java:114) at org.mulgara.itql.TqlSession.executeCommand(TqlSession.java:242) at org.mulgara.itql.TqlSessionUI$ExecutionThread.run (TqlSessionUI.java:701) Caused by: org.mulgara.query.QueryException: org.mulgara.query.MulgaraTransactionException: Transaction rollback triggered at org.mulgara.resolver.MulgaraInternalTransaction.implicitRollback (MulgaraInternalTransaction.java:516) at org.mulgara.resolver.MulgaraInternalTransaction.execute (MulgaraInternalTransaction.java:627) at org.mulgara.resolver.DatabaseSession.execute(DatabaseSession.java: 751) at org.mulgara.resolver.DatabaseSession.createModel (DatabaseSession.java:512) at org.mulgara.server.rmi.SessionWrapperRemoteSession.createModel (SessionWrapperRemoteSession.java:322) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source) at sun.rmi.transport.Transport$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Unknown Source) at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown Source) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: org.mulgara.query.QueryException: Couldn't find resolver factory in internal resolver map http://mulgara.org/mulgara#TypeModel at org.mulgara.resolver.CreateModelOperation.execute (CreateModelOperation.java:103) at org.mulgara.resolver.MulgaraInternalTransaction.execute (MulgaraInternalTransaction.java:623) ... 17 more Den 22/10/2008 kl. 14.37 skrev Rune Stilling: > Hi > > I'm trying to get some Krule up and running, but I stumble when I try > to create a typemodel or prefixmodel: > > create mulgara#TypeModel>; > > I just get the error: > > Error: Could not commit creation of model rmi://...:8089/ > server1#type of type http://mulgara.org/mulgara#TypeModel > > I have tried both IP-addresse, localhost and machine name. I'm also > perfectly able to create other models except for those of some type. > > What's wrong? > > \Rune > > _______________________________________________ > Mulgara-general mailing list > Mulgara-general at mulgara.org > http://mulgara.org/mailman/listinfo/mulgara-general _______________________________________________ Mulgara-general mailing list Mulgara-general at mulgara.org http://mulgara.org/mailman/listinfo/mulgara-general From gearon at ieee.org Wed Oct 22 07:31:46 2008 From: gearon at ieee.org (Paul Gearon) Date: Wed, 22 Oct 2008 09:31:46 -0500 Subject: [Mulgara-general] "Could not commit creation of model ..." In-Reply-To: <44C65E5E-A294-411B-B95B-E41C9A89207F@rdfined.dk> References: <44C65E5E-A294-411B-B95B-E41C9A89207F@rdfined.dk> Message-ID: Hi Rune, I'm surprised at this, and will try to work it out... but you shouldn't need it anymore anyway. Instead of creating your own type graph (I'm slowly trying to change the name "model" to the name "graph") instead use the pre-existing graph . Paul On Wed, Oct 22, 2008 at 7:37 AM, Rune Stilling wrote: > Hi > > I'm trying to get some Krule up and running, but I stumble when I try > to create a typemodel or prefixmodel: > > create mulgara#TypeModel>; > > I just get the error: > > Error: Could not commit creation of model rmi://...:8089/ > server1#type of type http://mulgara.org/mulgara#TypeModel > > I have tried both IP-addresse, localhost and machine name. I'm also > perfectly able to create other models except for those of some type. > > What's wrong? > > \Rune > > _______________________________________________ > Mulgara-general mailing list > Mulgara-general at mulgara.org > http://mulgara.org/mailman/listinfo/mulgara-general > From gearon at ieee.org Wed Oct 22 07:42:07 2008 From: gearon at ieee.org (Paul Gearon) Date: Wed, 22 Oct 2008 09:42:07 -0500 Subject: [Mulgara-general] "Could not commit creation of model ..." In-Reply-To: <690E83C1D15F5B4D84ACDAC9D0C1FD87014C42AD@ROCHESTER01.viewpoint.local> References: <44C65E5E-A294-411B-B95B-E41C9A89207F@rdfined.dk> <3569FCE4-06BD-4DDB-BE51-4E252F5D8D56@rdfined.dk> <690E83C1D15F5B4D84ACDAC9D0C1FD87014C42AD@ROCHESTER01.viewpoint.local> Message-ID: On Wed, Oct 22, 2008 at 9:24 AM, David Smith wrote: > > > Use: http://mulgara.org/mulgara#TypeGraph Ah, I should have looked for this. Thanks David. I suppose this makes it even more important to find all the references to the word "Model" in the documentation (such as it is) and examples. > I found it by looking at the built in models with this query: > > select $subject $predicate $object from where > $subject $predicate $object; > > As you can see, there is also a "built in" type model named: "sys:type" > > This was probably introduced in 2.0.6 with the change from the work > "Model" to "Graph" --- SPARQLism Actually, both the change to "Graph" and the default instances of these graphs were introduced with 2.0 ALPHA. We figured that the change in major version number was the right time to make a significant change like this. For details, have a look at: http://mulgara.org/release.html#v2.0-alpha I didn't explicitly say that graph types have changed names here because we were expecting that people would no longer need to refer to them directly. Regards, Paul Gearon From subs at rdfined.dk Fri Oct 24 06:53:13 2008 From: subs at rdfined.dk (Rune Stilling) Date: Fri, 24 Oct 2008 15:53:13 +0200 Subject: [Mulgara-general] "Could not commit creation of model ..." In-Reply-To: References: <44C65E5E-A294-411B-B95B-E41C9A89207F@rdfined.dk> <3569FCE4-06BD-4DDB-BE51-4E252F5D8D56@rdfined.dk> <690E83C1D15F5B4D84ACDAC9D0C1FD87014C42AD@ROCHESTER01.viewpoint.local> Message-ID: <12FF2F63-97D2-41A8-97CA-C271296AC932@rdfined.dk> Hi Thanks both of you. I have got my first rule up an running using Horn- clauses. I must say that this is really elegant! \Rune From gearon at ieee.org Fri Oct 24 12:38:39 2008 From: gearon at ieee.org (Paul Gearon) Date: Fri, 24 Oct 2008 14:38:39 -0500 Subject: [Mulgara-general] "Could not commit creation of model ..." In-Reply-To: <12FF2F63-97D2-41A8-97CA-C271296AC932@rdfined.dk> References: <44C65E5E-A294-411B-B95B-E41C9A89207F@rdfined.dk> <3569FCE4-06BD-4DDB-BE51-4E252F5D8D56@rdfined.dk> <690E83C1D15F5B4D84ACDAC9D0C1FD87014C42AD@ROCHESTER01.viewpoint.local> <12FF2F63-97D2-41A8-97CA-C271296AC932@rdfined.dk> Message-ID: It'll be even more elegant when you don't have to run rlog as a separate process. Rlog, and the rules engine are completely my own work and my own ideas. *I* like it myself, but it's nice to get a complement for it. :-) Regards, Paul Gearon On Fri, Oct 24, 2008 at 8:53 AM, Rune Stilling wrote: > Hi > > Thanks both of you. I have got my first rule up an running using Horn- > clauses. I must say that this is really elegant! > > \Rune > > > _______________________________________________ > Mulgara-general mailing list > Mulgara-general at mulgara.org > http://mulgara.org/mailman/listinfo/mulgara-general > From subs at rdfined.dk Mon Oct 27 06:56:04 2008 From: subs at rdfined.dk (Rune Stilling) Date: Mon, 27 Oct 2008 14:56:04 +0100 Subject: [Mulgara-general] Question about KRULE Message-ID: <7386FE2A-0D15-4203-B906-B193E1469ED1@rdfined.dk> Hi - One question about KRULE. Let's say I have the following ontology: rdf:type(Tag, Class). rdf:type(tagInstance1, Tag). rdf:type(tagInstance2, Tag). I then create some rules using KRULE: rdf:type(derivedTagInstance, Tag) :- rdf:type(X, Tag). rdfs:label(derivedTagInstance, L) :- rdf:type(X, Tag), rdfs:label(X, L). What I would like the system to do is to create two new instances of the Tag class with labels copied from tagInstance1 and tagInstance2 (one label on one instance). Currently I get only one instance but two labels on derivedTagInstance. 1) Is there any way to let the Krule generate new ressource ID's? 2) Is there any way to connect rule one and rule two so that the system is able to create two distinct instances with two distinct labels? I know I'm probably pushing it, but maybe there is some way to do this? Regards Rune From gearon at ieee.org Mon Oct 27 07:08:48 2008 From: gearon at ieee.org (Paul Gearon) Date: Mon, 27 Oct 2008 09:08:48 -0500 Subject: [Mulgara-general] Question about KRULE In-Reply-To: <7386FE2A-0D15-4203-B906-B193E1469ED1@rdfined.dk> References: <7386FE2A-0D15-4203-B906-B193E1469ED1@rdfined.dk> Message-ID: On Mon, Oct 27, 2008 at 8:56 AM, Rune Stilling wrote: > Hi - One question about KRULE. > > Let's say I have the following ontology: > > rdf:type(Tag, Class). > rdf:type(tagInstance1, Tag). > rdf:type(tagInstance2, Tag). You'd probably want to put domains on those labels. I've been thinking about recognizing certain labels and giving them default domains (so "type" would become "rdf:type" automatically), but as yet I haven't done that. > I then create some rules using KRULE: > > rdf:type(derivedTagInstance, Tag) :- rdf:type(X, Tag). > rdfs:label(derivedTagInstance, L) :- rdf:type(X, Tag), rdfs:label(X, L). > > What I would like the system to do is to create two new instances of > the Tag class with labels copied from tagInstance1 and tagInstance2 > (one label on one instance). Currently I get only one instance but > two labels on derivedTagInstance. > > 1) Is there any way to let the Krule generate new ressource ID's? As it stands, no. This is feasible, but it's not on the roadmap. Do you need it to be? > 2) Is there any way to connect rule one and rule two so that the > system is able to create two distinct instances with two distinct > labels? Actually, they're not connected at all, so if the capability existed to create new instances, then you'd automatically get two of them. Connecting these rules would only be needed if you wanted to create a new instance in one of them, and re-use that instance in the other. > I know I'm probably pushing it, but maybe there is some way to do this? Not yet, but all things are possible. It's a matter of priorities. Do you have enough of a use case to convince my boss? :-) Regards, Paul