Bug #80255 for RDF-TriN3: RDF-TriN3-0.202 fails with RDF::Trine >= 1.000

Wed Oct 17 23:38:55 2012 ANDK [...] cpan.org - Ticket created

CC:	GWILLIAMS [...] cpan.org
Subject:	RDF-TriN3-0.202 fails with RDF::Trine >= 1.000_01

As per subject. Sample fail report: 1.000_01: http://www.cpantesters.org/cpan/report/23567735 1.001: http://www.cpantesters.org/cpan/report/23769989 HTH && Regards,

Thu Oct 18 00:02:26 2012 gwilliams [...] cpan.org - Correspondence added

On Wed Oct 17 23:38:55 2012, ANDK wrote: Show quoted text

> As per subject. > > Sample fail report: > > 1.000_01: http://www.cpantesters.org/cpan/report/23567735 > > 1.001: http://www.cpantesters.org/cpan/report/23769989 > > HTH && Regards,

This is my fault. RDF::Trine::Parser::Turtle was re-implemented in these versions of RDF::Trine, and it broke the RDF::TriN3 subclass. I'll work with TOBYINK to get this fixed in a new release of RDF::TriN3.

Thu Oct 18 00:02:27 2012 The RT System itself - Status changed from 'new' to 'open'

Thu Oct 18 06:09:24 2012 perl [...] toby.ink - Correspondence added

On 2012-10-18T05:02:26+01:00, GWILLIAMS wrote: Show quoted text

> This is my fault. RDF::Trine::Parser::Turtle was re-implemented in > these versions of RDF::Trine, and it broke the RDF::TriN3 subclass.

In current versions, the N3 parser no longer subclasses the Turtle parser; it has all the methods it needed inlined. However, it looks like I was relying on certain regexes in the Turtle parser package. I was hoping for a release of RDF-Trine including the new format registry, serializer and parser APIs before releasing an update to RDF- TriN3.

Wed Dec 12 11:33:01 2012 perl [...] toby.ink - Correspondence added

Resolved 0.203.

Wed Dec 12 11:33:01 2012 perl [...] toby.ink - Status changed from 'open' to 'resolved'

Bug #80255 for RDF-TriN3: RDF-TriN3-0.202 fails with RDF::Trine >= 1.000_01