You can subscribe to this list here.
2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
(8) |
Dec
(4) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2006 |
Jan
(6) |
Feb
(1) |
Mar
(1) |
Apr
(1) |
May
(13) |
Jun
(18) |
Jul
(9) |
Aug
(7) |
Sep
(2) |
Oct
(31) |
Nov
(2) |
Dec
(2) |
2007 |
Jan
|
Feb
(7) |
Mar
(12) |
Apr
(8) |
May
(8) |
Jun
(10) |
Jul
(7) |
Aug
|
Sep
(2) |
Oct
(2) |
Nov
(1) |
Dec
|
2008 |
Jan
|
Feb
(1) |
Mar
(1) |
Apr
(1) |
May
(6) |
Jun
(2) |
Jul
|
Aug
(37) |
Sep
(9) |
Oct
(5) |
Nov
(5) |
Dec
(10) |
2009 |
Jan
(10) |
Feb
(9) |
Mar
(3) |
Apr
(4) |
May
(25) |
Jun
(61) |
Jul
(24) |
Aug
(12) |
Sep
(7) |
Oct
(1) |
Nov
(4) |
Dec
(1) |
2010 |
Jan
(12) |
Feb
(14) |
Mar
|
Apr
(1) |
May
|
Jun
(9) |
Jul
(1) |
Aug
(3) |
Sep
(21) |
Oct
(2) |
Nov
|
Dec
(5) |
2011 |
Jan
(3) |
Feb
(7) |
Mar
(1) |
Apr
|
May
(4) |
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
(1) |
2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Olaf H. <ha...@in...> - 2009-05-29 18:35:58
|
Hey, On Friday 29 May 2009 19:35:22 Jennifer Cormier wrote: > [...] > > Can you explain what we need SingleNamedGraphModel for? > > For a project I was working on, I needed a way to convert a ng4j.NamedGraph > to a Model and retain the graph name. Thus the SingleNamedGraphModel. > Thought others might find it useful also so we contributed it to the > project. I see. > [...] > Let's aim for the following week then for the release. That will give us > more time to sort out the library list, the pom.xml, and upgrading > bouncycastle libraries. Okay. > Last night I checked in an initial version of LIBRARIES.txt in the /lib > directory. I had versions for some but not all of the libraries included > with Jena 2.5.6. There are some other gaps, too, like grddl. The log says: revision 1.1 date: 2007/03/08 22:54:03; author: sfakste; state: Exp; Added the jena grddl library(-ies) Looking at the Packages provided at the SourceForge project page for Jena I found grddl-0.3 - added this info to lib/LIBRARIES.txt > I also included a "source" column with the intent that we'd list the > location from which to obtain each library. Great idea. Thanks, Olaf |
From: Jennifer C. <jen...@at...> - 2009-05-29 17:24:10
|
Hi Olaf, > I don't quite understand why you added SingleNamedGraphModel. I don't find > a reference to it (except from all your new SingleNamedGraph*.java files). > Can you explain what we need SingleNamedGraphModel for? For a project I was working on, I needed a way to convert a ng4j.NamedGraph to a Model and retain the graph name. Thus the SingleNamedGraphModel. Thought others might find it useful also so we contributed it to the project. > Next week is ESWC - I will go there tomorrow. This means, I'm unsure > whether I find the time to get anything done. Let's aim for the following week then for the release. That will give us more time to sort out the library list, the pom.xml, and upgrading bouncycastle libraries. Last night I checked in an initial version of LIBRARIES.txt in the /lib directory. I had versions for some but not all of the libraries included with Jena 2.5.6. There are some other gaps, too, like grddl. I also included a "source" column with the intent that we'd list the location from which to obtain each library. Jennifer -----Original Message----- From: Olaf Hartig [mailto:ha...@in...] Sent: Friday, May 29, 2009 12:58 PM To: Jennifer Cormier Cc: ng4...@li... Subject: Re: [namedgraphs] new release Hey Jennifer, On Wednesday 27 May 2009 21:19:02 Jennifer Cormier wrote: > Olaf, > > Thank you for your willingness to wait a few extra days. I've tested > TriGWriter and made the additional changes I planned. (Now there is a > new class, SingleNamedGraphModel, which is like NamedGraphModel except > that it is backed by a single NamedGraph rather than a NamedGraphSet.) I don't quite understand why you added SingleNamedGraphModel. I don't find a reference to it (except from all your new SingleNamedGraph*.java files). Can you explain what we need SingleNamedGraphModel for? > So, unless someone else has additional changes, you can work on the > new release when it's most convenient for you. Next week is ESWC - I will go there tomorrow. This means, I'm unsure whether I find the time to get anything done. Greetings, Olaf |
From: Olaf H. <ha...@in...> - 2009-05-29 17:07:38
|
Hey, On Thursday 28 May 2009 18:56:01 Jennifer Cormier wrote: > Hi Tim > > > Do you have Maven installed? > > Are you happy to check in the updated pom? > > I don't have Maven installed. > > I could check in the new pom since the old one doesn't work with the > current NG4J build. But let's hold off briefly to see if anyone else steps > forward to test it or if Olaf would prefer to commit the pom.xml file. Sorry, I don't dare to check this stuff because I don't know anything about Maven. Olaf |
From: Olaf H. <ha...@in...> - 2009-05-29 16:58:39
|
Hey Jennifer, On Wednesday 27 May 2009 21:19:02 Jennifer Cormier wrote: > Olaf, > > Thank you for your willingness to wait a few extra days. I've tested > TriGWriter and made the additional changes I planned. (Now there is a new > class, SingleNamedGraphModel, which is like NamedGraphModel except that it > is backed by a single NamedGraph rather than a NamedGraphSet.) I don't quite understand why you added SingleNamedGraphModel. I don't find a reference to it (except from all your new SingleNamedGraph*.java files). Can you explain what we need SingleNamedGraphModel for? > So, unless someone else has additional changes, you can work on the new > release when it's most convenient for you. Next week is ESWC - I will go there tomorrow. This means, I'm unsure whether I find the time to get anything done. Greetings, Olaf |
From: Jennifer C. <jen...@at...> - 2009-05-28 16:44:09
|
Hi Tim > Do you have Maven installed? > Are you happy to check in the updated pom? I don't have Maven installed. I could check in the new pom since the old one doesn't work with the current NG4J build. But let's hold off briefly to see if anyone else steps forward to test it or if Olaf would prefer to commit the pom.xml file. In the future if you would you create change requests at the sourceforge site and submit new code, bugs, etc., there, that'd be great. That would make it easier for us to track things and also help to avoid cluttering people's inboxes with extra attachments. (It's fine to also mention whatever on the mailing list, of course. I'm only trying to avoid attachments and excessive back-and-forth.) Also, while working on the list of jar file versions I noticed that there's a newer version of the bouncy castle libraries, and I see that you've included the newer version in your pom. I've downloaded the latest libraries (for JDK 1.5 - we haven't forced people to 1.6 yet) and will do some testing with those. Before committing the pom I'd like to finish the library version list and make sure it coincides with the pom. Thanks for all your help in improving the release! Jennifer -----Original Message----- From: Tim Pizey [mailto:tim...@ou...] Sent: Thursday, May 28, 2009 10:28 AM To: Jennifer Cormier Cc: ng4...@li... Subject: Re: [namedgraphs] new release Hi Jennifer, thanks for your reply. On Thursday 28 May 2009 14:56:26 Jennifer Cormier wrote: > I like the idea of having each jar name include its version. > > However, the NG4J project storage system is CVS hosted by sourceforge, > and I seem to recall reading (though I can't find it now) that > SourceForge discourages projects from committing too many binary files > or changing them too often, since CVS doesn't handle binary files very > well and it therefore takes up a lot of space. Yes, binary files have to be stored as blobs and cannot have their diffs stored. I cannot see that this would be different for SVN. However I do not think that it would be abusive to put renamed copies in, they are not that big. > I suppose that if a jar file is changing, then it probably doesn't > take much more or less space to replace it by a file with a different name. True > Since we're not replacing jar files with different versions right now, > rather than renaming the files, I propose we include a list of what > version each jar file is. When a jar file is later replaced, we can > plan to use a new naming scheme. That makes sense. > I think I was the last one to update the Jena jars. I do have a list > of the versions of each. (Yes, it was Jena 2.5.6.) I will take > responsibility for creating a text file listing each jar and its version. > I'll send out a note when I've checked in the file and let you all > know if there are some remaining gaps in the list. > Thanks. Do you have Maven installed? Are you happy to check in the updated pom? regards Tim |
From: Tim P. <tim...@ou...> - 2009-05-28 14:27:45
|
Hi Jennifer, thanks for your reply. On Thursday 28 May 2009 14:56:26 Jennifer Cormier wrote: > I like the idea of having each jar name include its version. > > However, the NG4J project storage system is CVS hosted by sourceforge, and > I seem to recall reading (though I can't find it now) that SourceForge > discourages projects from committing too many binary files or changing them > too often, since CVS doesn't handle binary files very well and it therefore > takes up a lot of space. Yes, binary files have to be stored as blobs and cannot have their diffs stored. I cannot see that this would be different for SVN. However I do not think that it would be abusive to put renamed copies in, they are not that big. > I suppose that if a jar file is changing, then it probably doesn't take > much more or less space to replace it by a file with a different name. True > Since we're not replacing jar files with different versions right now, > rather than renaming the files, I propose we include a list of what version > each jar file is. When a jar file is later replaced, we can plan to use a > new naming scheme. That makes sense. > I think I was the last one to update the Jena jars. I do have a list of > the versions of each. (Yes, it was Jena 2.5.6.) I will take > responsibility for creating a text file listing each jar and its version. > I'll send out a note when I've checked in the file and let you all know if > there are some remaining gaps in the list. > Thanks. Do you have Maven installed? Are you happy to check in the updated pom? regards Tim |
From: Jennifer C. <jen...@at...> - 2009-05-28 14:11:19
|
Tim, I'm sorry that the lack of versioning of the jars has caused so much trouble. You raise a very good point. I like the idea of having each jar name include its version. However, the NG4J project storage system is CVS hosted by sourceforge, and I seem to recall reading (though I can't find it now) that SourceForge discourages projects from committing too many binary files or changing them too often, since CVS doesn't handle binary files very well and it therefore takes up a lot of space. I suppose that if a jar file is changing, then it probably doesn't take much more or less space to replace it by a file with a different name. Since we're not replacing jar files with different versions right now, rather than renaming the files, I propose we include a list of what version each jar file is. When a jar file is later replaced, we can plan to use a new naming scheme. I think I was the last one to update the Jena jars. I do have a list of the versions of each. (Yes, it was Jena 2.5.6.) I will take responsibility for creating a text file listing each jar and its version. I'll send out a note when I've checked in the file and let you all know if there are some remaining gaps in the list. Regards, Jennifer -----Original Message----- From: Tim Pizey [mailto:tim...@ou...] Sent: Thursday, May 28, 2009 9:00 AM To: ng4...@li... Subject: Re: [namedgraphs] new release On Thursday 28 May 2009 09:29:35 Tim Pizey wrote: > > However I will let you know how I get on. > I have updated the pom, which I attach, but the tests are failing for me. Failed tests: testValidateSignatureNamedGraphNodeStringX509CertificateArrayList(de.fuberli n.wiwiss.ng4j.swp.util.SWPSignatureUtilitiesTest) testVerifyAllSignatures_Serialized(de.fuberlin.wiwiss.ng4j.swp.SWPNamedGraph SetTest) These also fail in Eclipse. My build environment is Kubuntu (AMD64), Eclipse, Java 1.6. I get quite a few warnings from the ant build and in eclipse. The lack of versioning of the jars has been really painful. I have spent a silly amount of time on something which is so basic. Please, please use jars named for their versions. The unversioned jars are almost all from the jena project: arq, jena, jenatest etc The version of jena which the software currently builds with is 2.5.6, but I believe jena is now at 2.6.1-SNAPSHOT The pom fails to build with the latest jena because N3JenaReader() has been deleted. Java development does not need to be this painful. I am tying to get jena to adopt Maven as its build tool, in addition to exporting to Maven repositories. This would offer the possibility of a coherent Continuous Integration approach across the whole set of tools. I am using Hudson, which I recommend. yours Tim |
From: Tim P. <tim...@ou...> - 2009-05-28 12:59:52
|
On Thursday 28 May 2009 09:29:35 Tim Pizey wrote: > > However I will let you know how I get on. > I have updated the pom, which I attach, but the tests are failing for me. Failed tests: testValidateSignatureNamedGraphNodeStringX509CertificateArrayList(de.fuberlin.wiwiss.ng4j.swp.util.SWPSignatureUtilitiesTest) testVerifyAllSignatures_Serialized(de.fuberlin.wiwiss.ng4j.swp.SWPNamedGraphSetTest) These also fail in Eclipse. My build environment is Kubuntu (AMD64), Eclipse, Java 1.6. I get quite a few warnings from the ant build and in eclipse. The lack of versioning of the jars has been really painful. I have spent a silly amount of time on something which is so basic. Please, please use jars named for their versions. The unversioned jars are almost all from the jena project: arq, jena, jenatest etc The version of jena which the software currently builds with is 2.5.6, but I believe jena is now at 2.6.1-SNAPSHOT The pom fails to build with the latest jena because N3JenaReader() has been deleted. Java development does not need to be this painful. I am tying to get jena to adopt Maven as its build tool, in addition to exporting to Maven repositories. This would offer the possibility of a coherent Continuous Integration approach across the whole set of tools. I am using Hudson, which I recommend. yours Tim |
From: Tim P. <tim...@ou...> - 2009-05-28 08:29:44
|
On Thursday 28 May 2009 09:06:21 Tim Pizey wrote: > On Wednesday 27 May 2009 20:19:02 Jennifer Cormier wrote: > > I wonder if anyone has been able to create a Maven build for NG4J. Tim? > > Anyone? That would be a great addition for the release. > > Ah, I am delighted to hear this might be of interest. > > I will try to get to it, but do not hold up the release. OK, the situation is that the Jena Maven build is a little non-standard too. So I need to get that polished and accepted by Jena before being able to contribute the updates to ng4j. However I will let you know how I get on. Tim |
From: Tim P. <tim...@ou...> - 2009-05-28 08:06:37
|
On Wednesday 27 May 2009 20:19:02 Jennifer Cormier wrote: > > I wonder if anyone has been able to create a Maven build for NG4J. Tim? > Anyone? That would be a great addition for the release. Ah, I am delighted to hear this might be of interest. I will try to get to it, but do not hold up the release. Tim |
From: Jennifer C. <jen...@at...> - 2009-05-27 19:10:43
|
Olaf, Thank you for your willingness to wait a few extra days. I've tested TriGWriter and made the additional changes I planned. (Now there is a new class, SingleNamedGraphModel, which is like NamedGraphModel except that it is backed by a single NamedGraph rather than a NamedGraphSet.) So, unless someone else has additional changes, you can work on the new release when it's most convenient for you. I wonder if anyone has been able to create a Maven build for NG4J. Tim? Anyone? That would be a great addition for the release. Jennifer -----Original Message----- From: Olaf Hartig [mailto:ha...@in...] Sent: Tuesday, May 26, 2009 12:02 PM To: Jennifer Cormier Cc: ng4...@li... Subject: Re: [namedgraphs] new release Hey Jennifer, > [...] > This is already a busy week for me; I can try to get the above done. > Could we aim for next week instead for the actual release? Sure. Greetings, Olaf |
From: Olaf H. <ha...@in...> - 2009-05-26 16:03:00
|
Hey Jennifer, > [...] > This is already a busy week for me; I can try to get the above done. Could > we aim for next week instead for the actual release? Sure. Greetings, Olaf |
From: Jennifer C. <jen...@at...> - 2009-05-26 14:32:45
|
Hi Olaf, It's great that you've made so many improvements! Regarding the plans for a new release, I * agree with the plan to postpone upgrading Jena/ARQ libraries * do have some things in the pipeline that I would like to include * need to do some tests with the modified version of TriGWriter This is already a busy week for me; I can try to get the above done. Could we aim for next week instead for the actual release? Thanks, Jennifer -----Original Message----- From: Olaf Hartig [mailto:ha...@in...] Sent: Sunday, May 24, 2009 5:03 PM To: ng4...@li... Subject: [namedgraphs] new release Hey, We released the most recent NG4J, 0.9, in Dec.2008. Since then I fixed several bugs - mainly in the Sem.Web Client Lib. Furthermore, I developed a new in-memory storage solution for the Sem.Web Client Lib. This store provides significantly better query execution times compared to the Jena-based implementation (reductions to about 31.7%). Read my latest blog post for details and an evaluation: http://apps.sourceforge.net/wordpress/squin/2009/05/24/new-bgp-query-handler -for-the-semantic-web-client-library-reduces-query-times-to-a-third/ Since the fixes as well as the new storage solution should not only be available in CVS I want to release a new version (0.10) of NG4J this week. Does someone object? Does someone has something in the pipeline which should go in this release? Should we upgrade to the latest Jena/ARQ libraries before the release? Notice, with their latest release the Jena/ARQ folks converted their codebase to Java5 and did lots of clean up (i.e. a large amount of deprecated classes and methods have been removed). Hence, upgrading NG4J to the latest Jena/ARQ could be a bit laborious and, more importantly, could introduce issues that may go unnoticed. For this reason, I suggest to release 0.10 with the Jena/ARQ libs we currently have in our CVS and to upgrade after the release. Greetings, Olaf |
From: Richard C. <ri...@cy...> - 2009-05-25 08:33:01
|
Olaf, On 24 May 2009, at 22:02, Olaf Hartig wrote: > Should we upgrade to the latest Jena/ARQ libraries before the > release? Notice, > with their latest release the Jena/ARQ folks converted their > codebase to > Java5 and did lots of clean up (i.e. a large amount of deprecated > classes and > methods have been removed). Hence, upgrading NG4J to the latest Jena/ > ARQ > could be a bit laborious and, more importantly, could introduce > issues that > may go unnoticed. For this reason, I suggest to release 0.10 with the > Jena/ARQ libs we currently have in our CVS and to upgrade after the > release. Sounds reasonable to me. Richard > > > Greetings, > Olaf > ------------------------------------------------------------------------------ > Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT > is a gathering of tech-side developers & brand creativity > professionals. Meet > the minds behind Google Creative Lab, Visual Complexity, Processing, & > iPhoneDevCamp asthey present alongside digital heavyweights like > Barbarian > Group, R/GA, & Big Spaceship. http://www.creativitycat.com > _______________________________________________ > ng4j-namedgraphs mailing list > ng4...@li... > https://lists.sourceforge.net/lists/listinfo/ng4j-namedgraphs |
From: Olaf H. <ha...@in...> - 2009-05-24 21:02:47
|
Hey, We released the most recent NG4J, 0.9, in Dec.2008. Since then I fixed several bugs - mainly in the Sem.Web Client Lib. Furthermore, I developed a new in-memory storage solution for the Sem.Web Client Lib. This store provides significantly better query execution times compared to the Jena-based implementation (reductions to about 31.7%). Read my latest blog post for details and an evaluation: http://apps.sourceforge.net/wordpress/squin/2009/05/24/new-bgp-query-handler-for-the-semantic-web-client-library-reduces-query-times-to-a-third/ Since the fixes as well as the new storage solution should not only be available in CVS I want to release a new version (0.10) of NG4J this week. Does someone object? Does someone has something in the pipeline which should go in this release? Should we upgrade to the latest Jena/ARQ libraries before the release? Notice, with their latest release the Jena/ARQ folks converted their codebase to Java5 and did lots of clean up (i.e. a large amount of deprecated classes and methods have been removed). Hence, upgrading NG4J to the latest Jena/ARQ could be a bit laborious and, more importantly, could introduce issues that may go unnoticed. For this reason, I suggest to release 0.10 with the Jena/ARQ libs we currently have in our CVS and to upgrade after the release. Greetings, Olaf |
From: Tim P. <tim...@ou...> - 2009-05-18 09:57:26
|
Hi Olaf, On Monday 18 May 2009 10:45:00 Olaf Hartig wrote: > Hey Tim, > > On Sunday 17 May 2009 22:20:11 Tim Pizey wrote: > > > Sun package imports there are replacements now. > > import sun.misc.BASE64Decoder; > > What are these replacements? org.apache.commons.codec.binary.Base64; provided by http://commons.apache.org/codec/ Whilst giving 'first impression' feedback, I notice some American (non-ISO) date formats in CHANGES. cheers Tim |
From: Tim P. <tim...@ou...> - 2009-05-18 09:47:05
|
Olaf, Thank you. Tim On Monday 18 May 2009 10:31:10 Olaf Hartig wrote: > Hey Tim, > > On Sunday 17 May 2009 22:46:26 Tim Pizey wrote: > > Hi, > > > > I have two graphs, one generated by a hand written xsl script and the > > other generated by TriGWriter.write(NamedGraphSet set, Writer out, String > > baseURI) > > > > How can I test them for equality, as they have many trivial differences. > > The Graph interface of Jena contains the method 'isIsomorphicWith' to > compare two RDF graphs. Since the NamedGraph interface is an extension of > the Graph interface you can use this method. > > Greetings, > Olaf |
From: Olaf H. <ha...@in...> - 2009-05-18 09:45:35
|
Hey Tim, On Sunday 17 May 2009 22:20:11 Tim Pizey wrote: > Trivial problems with the ant build on Debian/AMD64. > > [java] Warning: at xsl:stylesheet on line 8 of > file:///home/dist/ng4j-0.9/tests/de/fuberlin/wiwiss/ng4j/trix/tests/extensi >on1.xsl: [java] Running an XSLT 1.0 stylesheet with an XSLT 2.0 processor Fixed. > Non-utf8 encoded characters in javadoc author tags: > @author Tobias Gau� Fixed. > Sun package imports there are replacements now. > import sun.misc.BASE64Decoder; What are these replacements? > But there was 1 test failure: > [java] 1) > testValidateSignatureNamedGraphNodeStringX509CertificateArrayList(de.fuberl >in.wiwiss.ng4j.swp.util.SWPSignatureUtilitiesTest)junit.framework.AssertionF >ailedError [java] at > de.fuberlin.wiwiss.ng4j.swp.util.SWPSignatureUtilitiesTest.testValidateSign >atureNamedGraphNodeStringX509CertificateArrayList(SWPSignatureUtilitiesTest. >java:302) [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) [java] at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:3 >9) [java] at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp >l.java:25) See ./tests/KnownIssues.txt Greetings, Olaf |
From: Olaf H. <ha...@in...> - 2009-05-18 09:32:06
|
Hey Tim, On Sunday 17 May 2009 22:46:26 Tim Pizey wrote: > Hi, > > I have two graphs, one generated by a hand written xsl script and the other > generated by TriGWriter.write(NamedGraphSet set, Writer out, String > baseURI) > > How can I test them for equality, as they have many trivial differences. The Graph interface of Jena contains the method 'isIsomorphicWith' to compare two RDF graphs. Since the NamedGraph interface is an extension of the Graph interface you can use this method. Greetings, Olaf |
From: Tim P. <tim...@ou...> - 2009-05-17 20:42:49
|
Hi, Trivial problems with the ant build on Debian/AMD64. [java] Warning: at xsl:stylesheet on line 8 of file:///home/dist/ng4j-0.9/tests/de/fuberlin/wiwiss/ng4j/trix/tests/extension1.xsl: [java] Running an XSLT 1.0 stylesheet with an XSLT 2.0 processor Non-utf8 encoded characters in javadoc author tags: @author Tobias Gau� Sun package imports there are replacements now. import sun.misc.BASE64Decoder; But there was 1 test failure: [java] 1) testValidateSignatureNamedGraphNodeStringX509CertificateArrayList(de.fuberlin.wiwiss.ng4j.swp.util.SWPSignatureUtilitiesTest)junit.framework.AssertionFailedError [java] at de.fuberlin.wiwiss.ng4j.swp.util.SWPSignatureUtilitiesTest.testValidateSignatureNamedGraphNodeStringX509CertificateArrayList(SWPSignatureUtilitiesTest.java:302) [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) I am sure these are all trivial and easy to fix. I attach the log file yours Tim Pizey |
From: Tim P. <tim...@ou...> - 2009-05-17 20:34:17
|
Hi, I have two graphs, one generated by a hand written xsl script and the other generated by TriGWriter.write(NamedGraphSet set, Writer out, String baseURI) How can I test them for equality, as they have many trivial differences. thanks Tim |
From: Richard C. <ri...@cy...> - 2009-05-13 08:33:47
|
On 12 May 2009, at 18:52, Tim Pizey wrote: > These are the first database tables in any product I have seen which > do not > have a meaningless, numeric key called id. Fair enough. I've seen plenty of DBs that don't have them, but that's still the exception. They are usually added because they make keeping referential integrity and foreign key constraints more efficient and robust; but these things don't apply in the case of NG4J. You can consider NG4J (or any database-backed RDF store, for that matter) an unusual application of database technology. Richard > > Quite a few tools 'just work' if you have such a key. > > > > cheers > Tim > |
From: Tim P. <tim...@ou...> - 2009-05-12 17:53:42
|
Hi Richard, thanks for your reply. On Tuesday 12 May 2009 18:30:38 Richard Cyganiak wrote: > On 12 May 2009, at 15:21, Tim Pizey wrote: > > The reason I ask is that I pointed an old favourite tool at my > > database, saw > > all the jena tables but could see no ng4j tables. > > Figured out after a while this was due to their lack of an id field. > > They have no reason to have an id field. They are not Jena tables. I know I am talking out of complete ignorance, and hope you will bear with me. These are the first database tables in any product I have seen which do not have a meaningless, numeric key called id. Quite a few tools 'just work' if you have such a key. cheers Tim |
From: Richard C. <ri...@cy...> - 2009-05-12 17:31:00
|
Tim, On 12 May 2009, at 15:21, Tim Pizey wrote: > Just starting out, taking over someone else's code, and frankly do not > understand anything, so please pardon this question, but why do Jena > tables > have a numeric key fields called 'id'' and ng4j tables not? NG4J simply uses a completely different layout for its database backend. It's not derived from Jena's database backend. > The reason I ask is that I pointed an old favourite tool at my > database, saw > all the jena tables but could see no ng4j tables. > Figured out after a while this was due to their lack of an id field. They have no reason to have an id field. They are not Jena tables. > Is this something that can optionally be added to a particular project No. > or may be added to ng4j in the future, Unlikely, there is AFAICT no reason to add such a column to the NG4J database layout. Best, Richard > or am I being just plain silly? > > yours > Tim > > > > ------------------------------------------------------------------------------ > The NEW KODAK i700 Series Scanners deliver under ANY circumstances! > Your > production scanning environment may not be a perfect world - but > thanks to > Kodak, there's a perfect scanner to get the job done! With the NEW > KODAK i700 > Series Scanner you'll get full speed at 300 dpi even with all image > processing features enabled. http://p.sf.net/sfu/kodak-com > _______________________________________________ > ng4j-namedgraphs mailing list > ng4...@li... > https://lists.sourceforge.net/lists/listinfo/ng4j-namedgraphs |
From: Tim P. <tim...@ou...> - 2009-05-12 14:22:43
|
Hi, Just starting out, taking over someone else's code, and frankly do not understand anything, so please pardon this question, but why do Jena tables have a numeric key fields called 'id'' and ng4j tables not? The reason I ask is that I pointed an old favourite tool at my database, saw all the jena tables but could see no ng4j tables. Figured out after a while this was due to their lack of an id field. Is this something that can optionally be added to a particular project or may be added to ng4j in the future, or am I being just plain silly? yours Tim |