ng4j-namedgraphs — Discussion of Named Graphs in RDF

[namedgraphs] Todo for next version

[Tim P. <tim...@ou...>]

Hi Olaf, Jennifer and all, 

I have started to bringNG4J inline with current Jena. 

Most changes are pretty trivial. However there appears to be a 
hack where we treat List<NamedGraph> and List<Graph> 
as covariant which will no longer work. 

Do you have a plan, are there other pitfalls?

yours
Tim 

[namedgraphs] N3JenaReader

[Tim P. <tim...@ou...>]

Hi, 


I am trying to upgrade NG4J to the latest Jena.
One of the quite small number of issues is that N3Reader has been removed. 
The CVS Log  http://jena.cvs.sourceforge.net/viewvc/jena/jena2/src/com/hp/hpl/jena/n3/N3JenaReader.java?hideattic=0&view=log 
says: 
Remove antlr-based N3 parser and route to JavaCC Turtle parser.

Is there a drop-in replacement?

thanks
Tim

Re: [namedgraphs] Release procedure

[Olaf H. <ha...@in...>]

On Monday 15 June 2009 18:18:25 Tim Pizey wrote:
> [...]
> Certainly in the POM and probably in build.xml we should use SNAPSHOT.

Okay - it is "0.9.2-SNAPSHOT" now, both in pom.xml and in build.xml
Furthermore, I adjusted the wiki entry.

Olaf

Re: [namedgraphs] Release procedure

[Tim P. <tim...@ou...>]

On Monday 15 Jun 2009 16:01:17 Olaf Hartig wrote:
> On Monday 15 June 2009 15:56:42 Tim Pizey wrote:
> > [...]
> > SNAPSHOT is a Maven special keyword.
> > What is special about SNAPSHOT is that it will go off and get the very
> > latest build.
> 
> Just to understand this. Does "will go off and get the very latest build" mean 
> Maven fetches the latest versions of all required libraries before compiling 
> the project?

No, I am being unclear because I am not certain of the details. 

Maven has two types of repository, those where 'snapshot versions' 
are allowed and those where they are not. 

The difference is that in addition to the file's version the file also has a date 
incorporated into its name. 

If I deploy a.jar at version 1.3 the file name in a non-snapshot repository will be a-1.3.jar.

However if I deploy to a snapshot repository then the file name will be,  for example: 
http://paneris.net/maven2/de/fuberlin/wiwss/ng4j/ng4j/0.9-SNAPSHOT/ng4j-0.9-20090606.175554-1.jar
I think that this is artefact id + version + date + time + serial 

So when a dependency has the special tag SNAPSHOT then Maven goes and checks 
the remote repository for the most recent version, even if it has a locally cached copy 
which matches on version number alone. 


> > Using POST is fine, but is new to this project I think.
> 
> Yes it is new - remember, we did not had a version build property before you 
> suggested to have one. I added the POST prefix because I assumed having 
> version "0.9.1" after the release would not be right.
> However, I'm still unsure whether I should also adjust the version in pom.xml 
> to "POST-0.9.1".

Certainly in the POM and probably in build.xml we should use SNAPSHOT. 

cheers
Tim

Re: [namedgraphs] Release procedure

[Olaf H. <ha...@in...>]

On Monday 15 June 2009 15:56:42 Tim Pizey wrote:
> [...]
> SNAPSHOT is a Maven special keyword.
> What is special about SNAPSHOT is that it will go off and get the very
> latest build.

Just to understand this. Does "will go off and get the very latest build" mean 
Maven fetches the latest versions of all required libraries before compiling 
the project?

> Using POST is fine, but is new to this project I think.

Yes it is new - remember, we did not had a version build property before you 
suggested to have one. I added the POST prefix because I assumed having 
version "0.9.1" after the release would not be right.
However, I'm still unsure whether I should also adjust the version in pom.xml 
to "POST-0.9.1".

Olaf

Re: [namedgraphs] Release procedure

[Tim P. <tim...@ou...>]

On Monday 15 Jun 2009 14:13:47 Olaf Hartig wrote:
> On Monday 15 June 2009 13:59:52 Tim Pizey wrote:
> > [...]
> > Just before open a beer  I think we need edit and commit
> > pom.xml and build.xml to append -SNAPSHOT to version number.
> 
> Okay - after creating the release I adjusted the version property 
> to "POST-0.9.1" - at least in build.xml. I was not aware that there is a 
> similar entry in pom.xml.
> Why do you suggest to append "-SNAPSHOT" to the version number? I assumed 
> my "POST-"  prefix is more intuitive. However, if the "-SNAPSHOT" postfix is 
> common practice I can change this. But with an increased version number, 
> right?

Olaf, 
you are right, I had it wrong, I checked on IRC , and the sequence is 

1.2
1.3-SNAPSHOT
1.3

This probably means that RC1, RC2 etc are not meaningful in this schema.


SNAPSHOT is a Maven special keyword. 
What is special about SNAPSHOT is that it will go off and get the very latest build.

Using POST is fine, but is new to this project I think.

> > Do we really want
> > "Remove all IDE-specific config and project files from the new directory."
> 
> I did not remove the .classpath and .project file. However, since I'm using 
> another IDE but Eclipse I have further config and project files in the main 
> dir of my local copies. I don't think these should be distributed.

cool.



cheers
Tim

Re: [namedgraphs] Release procedure

[Olaf H. <ha...@in...>]

On Monday 15 June 2009 13:59:52 Tim Pizey wrote:
> [...]
> Just before open a beer  I think we need edit and commit
> pom.xml and build.xml to append -SNAPSHOT to version number.

Okay - after creating the release I adjusted the version property 
to "POST-0.9.1" - at least in build.xml. I was not aware that there is a 
similar entry in pom.xml.
Why do you suggest to append "-SNAPSHOT" to the version number? I assumed 
my "POST-"  prefix is more intuitive. However, if the "-SNAPSHOT" postfix is 
common practice I can change this. But with an increased version number, 
right?

> Do we really want
> "Remove all IDE-specific config and project files from the new directory."

I did not remove the .classpath and .project file. However, since I'm using 
another IDE but Eclipse I have further config and project files in the main 
dir of my local copies. I don't think these should be distributed.

Olaf

[namedgraphs] Release procedure

[Tim P. <tim...@ou...>]

Hi Olaf, all, 


Just before open a beer  I think we need edit and commit 
pom.xml and build.xml to append -SNAPSHOT to version number. 

Do we really want 
"Remove all IDE-specific config and project files from the new directory."

cheers
Tim

Re: [namedgraphs] new release

[Olaf H. <ha...@in...>]

Hey Tim,

On Monday 15 June 2009 12:31:25 Tim Pizey wrote:
> On Sunday 14 Jun 2009 07:51:08 Olaf Hartig wrote:
> > Hey,
> >
> > I just created and uploaded the new release NG4J v0.9.1
>
> Great, is there a release procedure, so that I can see what
> you mean.
>
> What does creating a release entail?

I documented the release process in our wiki:
http://sourceforge.net/apps/mediawiki/ng4j/index.php?title=Release_Process

Greetings,
Olaf

[namedgraphs] tests/de/fuberlin/wiwiss/ng4j/trig/TriGParserTest.java

[Tim P. <tim...@ou...>]

Hi, 

I have to comment this test out on linux as it has unencoded 
high value ascii string literals. 

cheers
tim

Re: [namedgraphs] new release

[Tim P. <tim...@ou...>]

On Sunday 14 Jun 2009 07:51:08 Olaf Hartig wrote:
> Hey,
> 
> I just created and uploaded the new release NG4J v0.9.1
> 

Great, is there a release procedure, so that I can see what 
you mean.

What does creating a release entail?

cheers
Tim

Re: [namedgraphs] new release

[Olaf H. <ha...@in...>]

Hey,

I just created and uploaded the new release NG4J v0.9.1

Thank you all for your valuable contributions!!!

Cheers,
Olaf

Re: [namedgraphs] All building with Maven

[Olaf H. <ha...@in...>]

On Thursday 11 June 2009 19:24:58 Jennifer Cormier wrote:
> Thank you Tim and Olaf.
>
> I looked over the pom.xml and checked it in to CVS.  Also added a comment
> to the feature request.  Do you want to close the ticket, Olaf?  (I'm not
> sure I have the permissions to do so.)

Done.

It seems we are ready to release 0.9.1 finally. Please, would everyone test 
again if anything works as expected and notify me. Unless I read about any 
issues I will create and publish the new version tomorrow.

Greetings,
Olaf

Re: [namedgraphs] All building with Maven

[Jennifer C. <jen...@at...>]

Thank you Tim and Olaf.

I looked over the pom.xml and checked it in to CVS.  Also added a comment to
the feature request.  Do you want to close the ticket, Olaf?  (I'm not sure
I have the permissions to do so.)

Thanks!

Jennifer

Re: [namedgraphs] All building with Maven

[Tim P. <tim...@ou...>]

Hi Jennifer and Olaf, 

On Thursday 11 Jun 2009 16:25:48 Jennifer Cormier wrote:
> Hi Olaf,
> 
> I would like to take a look at the pom.xml and perhaps make some final edits
> before you create the release.  Last I checked Tim had not yet uploaded the
> latest version of the pom.xml.

Yes, I have been through it all from end to end. 
I think it is a bout right now. 

I will update the tracker now.

> This last question might be for Tim - do we need to create the repository
> for Maven artifacts before creating the release, or can that be done
> afterwards?


We can do it afterwards. 

I think that you need to go into sourceforge shell account and create the directory 
maven2 at the webroot, after that you should be able to do everything from 
the command line. 

cheers
Tim

Re: [namedgraphs] All building with Maven

[Olaf H. <ha...@in...>]

On Thursday 11 June 2009 17:25:48 Jennifer Cormier wrote:
> Hi Olaf,
>
> I would like to take a look at the pom.xml and perhaps make some final
> edits before you create the release.  Last I checked Tim had not yet
> uploaded the latest version of the pom.xml.

Okay - tell me when you are done.

> Also, has GRDDL already been marked deprecated in the code and in
> index.html?

Not yet.

Olaf

Re: [namedgraphs] All building with Maven

[Jennifer C. <jen...@at...>]

Hi Olaf,

I would like to take a look at the pom.xml and perhaps make some final edits
before you create the release.  Last I checked Tim had not yet uploaded the
latest version of the pom.xml.

Also, has GRDDL already been marked deprecated in the code and in
index.html?

This last question might be for Tim - do we need to create the repository
for Maven artifacts before creating the release, or can that be done
afterwards?

Thanks,

Jennifer
 
P.S. Olaf - sorry for the duplicate message - I neglected to hit reply-all
the first time.


-----Original Message-----
From: Olaf Hartig [mailto:ha...@in...]
Sent: Thursday, June 11, 2009 9:49 AM
To: ng4...@li...
Subject: Re: [namedgraphs] All building with Maven

Hey,

On Thursday 11 June 2009 14:59:16 Tim Pizey wrote:
> Hi all,
>
> I have everything building correctly,
> with the one excluded test excluded, all else passing.
>
> This gives us 39% test coverage:
> http://paneris.net/ng4j/cobertura/index.html
>
> Annoyingly I did not make a note of the previous percentage.
>
> The ant build completes, fails on the known failing test.

Great work. Thank you!

Does this mean I can create the new release after replacing pom.xml in CVS
with the new version provided with Feature Request 2801813 ?

Olaf

Re: [namedgraphs] All building with Maven

[Olaf H. <ha...@in...>]

Hey,

On Thursday 11 June 2009 14:59:16 Tim Pizey wrote:
> Hi all,
>
> I have everything building correctly,
> with the one excluded test excluded, all else passing.
>
> This gives us 39% test coverage:
> http://paneris.net/ng4j/cobertura/index.html
>
> Annoyingly I did not make a note of the previous percentage.
>
> The ant build completes, fails on the known failing test.

Great work. Thank you!

Does this mean I can create the new release after replacing pom.xml in CVS 
with the new version provided with Feature Request 2801813 ?

Olaf

[namedgraphs] All building with Maven

[Tim P. <tim...@ou...>]

Hi all, 

I have everything building correctly, 
with the one excluded test excluded, all else passing. 

This gives us 39% test coverage: 
http://paneris.net/ng4j/cobertura/index.html

Annoyingly I did not make a note of the previous percentage. 

The ant build completes, fails on the known failing test. 

Tim

Re: [namedgraphs] new release

[Olaf H. <ha...@in...>]

On Wednesday 10 June 2009 17:37:33 Jennifer Cormier wrote:
> 0.9.1 sounds good to me!
>
> There are a few other loose ends to clean up.  If there are no objection
> I'll
>
> * Remove the jakarta-oro library
> * Upgrade the axis library to version 1.4

No objections from me.

Olaf

Re: [namedgraphs] new release

[Jennifer C. <jen...@at...>]

0.9.1 sounds good to me!

There are a few other loose ends to clean up.  If there are no objection
I'll

* Remove the jakarta-oro library
* Upgrade the axis library to version 1.4


Jennifer
 

-----Original Message-----
From: Olaf Hartig [mailto:ha...@in...] 
Sent: Wednesday, June 10, 2009 10:38 AM
To: ng4...@li...
Subject: Re: [namedgraphs] new release

Hey,

On Tuesday 02 June 2009 17:41:15 Tim Pizey wrote:
> On Tuesday 02 Jun 2009 15:53:25 Tim Pizey wrote:
> > This has been the subject of previous discussions, which I have not 
> > chased these down, but my 2p would be that numbers to the right of 
> > the first point may not exceed 9.
>
> 
>http://www.sonatype.com/books/maven-book/reference/pom-relationships-se
>ct-p
>om- syntax.html#pom-reationships-sect-versions
>
> Is the guidance from Maven

Okay, I understand their reasoning.

Now we have to decide for a version number. I would go for 0.9.1 for the
following reasons. We added two new things since 0.8:

i) my identifier-based Graph and NamedGraphSet implementation and
ii) Jennifer's SingleNamedGraph* stuff.

In addition to this there are many bug fixes.
My new stuff is not completely used by SWClLib due to integration issues (I
will work on this after the release). I think SingleNamedGraph* as the only
new feature does not justify naming the new release 1.0.

Greetings,
Olaf

Re: [namedgraphs] new release

[Olaf H. <ha...@in...>]

Hey,

On Tuesday 02 June 2009 17:41:15 Tim Pizey wrote:
> On Tuesday 02 Jun 2009 15:53:25 Tim Pizey wrote:
> > This has been the subject of previous discussions, which I have not
> > chased these down, but my 2p would be that numbers to the right of the
> > first point may not exceed 9.
>
> http://www.sonatype.com/books/maven-book/reference/pom-relationships-sect-p
>om- syntax.html#pom-reationships-sect-versions
>
> Is the guidance from Maven

Okay, I understand their reasoning.

Now we have to decide for a version number. I would go for 0.9.1 for the 
following reasons. We added two new things since 0.8:

i) my identifier-based Graph and NamedGraphSet implementation and
ii) Jennifer's SingleNamedGraph* stuff.

In addition to this there are many bug fixes.
My new stuff is not completely used by SWClLib due to integration issues (I 
will work on this after the release). I think SingleNamedGraph* as the only 
new feature does not justify naming the new release 1.0.

Greetings,
Olaf

Re: [namedgraphs] Use of Grddl

[Olaf H. <ha...@in...>]

Hey,

On Saturday 06 June 2009 21:59:18 Tim Pizey wrote:
> [...]
> in DereferencerThread
>
> 	private DereferencingResult parseRdf(DereferencingTask task, String lang)
> throws Exception { if (lang.equals("default"))
> 			lang = null;
> 		if (lang.equals("html") || lang.equals("HTML")){
>
> We can see by inspection that if the lang is "default"  we will get an NPE

Fixed this bug.

Olaf

Re: [namedgraphs] NG4J project wiki

[Tim P. <tim...@ou...>]

Hi Olaf, 

On Wednesday 10 June 2009 13:39:20 Olaf Hartig wrote:
> On Wednesday 10 June 2009 12:42:01 Tim Pizey wrote:
> > Lets get this one out of the door so that we can focus on catching up with
> > current jena.
> 
> Definitely agree!
> 
> Regarding GRDDL: GRDDL does not seem to be used much in the wild. Furthermore, 
> GRDDL has some kind of being obsoleted by RDFa. And, the GRDDL support in 
> SWClLib is currently not actively maintained by anyone. I don't know how to 
> stress test the GRDDL support. So I couldn't really say whether the use of 
> the latest grddl.jar breaks anything.
> For these reasons, Richard and me came to the conclusion to deprecate GRDDL 
> support in SWClLib. This means the coming NG4J release will be the last that 
> contains GRDDL support unless someone steps up to maintain it. 

Good. 

> Given this 
> decision, I am unsure whether it makes sense to update the grddl.jar provided 
> with NG4J. Are there any reasons why we should use the latest grddl.jar in 
> the new release? Otherwise, I suggest to leave everything as it is.

If this means we can move quickly then lets leave things as they are. 

Then we can move straight on to the next version which will have no grddl. 

For my own project I do not intend to use any intermediates until ng4j and jena 
are in step. 
I do not use the semweb functionality and so do not use grddl. 

As far as I can see all we need to do is decide on what the next version is to be  
called and we are good to go. 


cheers
Tim

Re: [namedgraphs] NG4J project wiki

[Olaf H. <ha...@in...>]

Hey,

@Jennifer: Thanks a lot to initiate this!!!

On Wednesday 10 June 2009 12:42:01 Tim Pizey wrote:
> On Tuesday 09 June 2009 23:26:13 Jennifer Cormier wrote:
> > The initial reason for the wiki is that it was getting too complicated to
> > track the changes planned for upcoming releases.  Now there's a page for
> > the next release - Post 0.9 Release Plans - accessible from the wiki's
> > Main Page.
>
> This all looks good, and not a lot to actually fix, much of it seems to
> already be done, or to be the sort of thing which it is quicker to do than
> to document.
>
> Lets get this one out of the door so that we can focus on catching up with
> current jena.

Definitely agree!

Regarding GRDDL: GRDDL does not seem to be used much in the wild. Furthermore, 
GRDDL has some kind of being obsoleted by RDFa. And, the GRDDL support in 
SWClLib is currently not actively maintained by anyone. I don't know how to 
stress test the GRDDL support. So I couldn't really say whether the use of 
the latest grddl.jar breaks anything.
For these reasons, Richard and me came to the conclusion to deprecate GRDDL 
support in SWClLib. This means the coming NG4J release will be the last that 
contains GRDDL support unless someone steps up to maintain it. Given this 
decision, I am unsure whether it makes sense to update the grddl.jar provided 
with NG4J. Are there any reasons why we should use the latest grddl.jar in 
the new release? Otherwise, I suggest to leave everything as it is.

Greetings,
Olaf