Re: Incompatibility of TriX format
I know I promised a PR, but I see you already committed one. Sorry about that, I'm only now coming back home from vacation. On Tue, Jul 19, 2016 at 12:37 PM, Andy Seabornewrote: > On 15/07/16 21:01, Martynas Jusevičius wrote: >> >> Created an issue: https://issues.apache.org/jira/browse/JENA-1211 > > > Great - > > I can make a pull request. > > and PR awaited! > > Andy > > >> >> On Thu, Jul 14, 2016 at 2:06 PM, Andy Seaborne wrote: >>> >>> On 14/07/16 11:38, Andy Seaborne wrote: On 14/07/16 10:10, Martynas Jusevičius wrote: > > > Hey, > > Jena seems to use another DTD than the one hosted by W3C: > https://www.w3.org/2004/03/trix/trix-1/trix-1.0.dtd vs. > > > https://github.com/apache/jena/blob/master/jena-arq/src/main/java/org/apache/jena/riot/lang/TriX.java > As per the comments : it uses http://www.hpl.hp.com/techreports/2004/HPL-2004-56.html > > From the first glance, at least the root element differs: vs. > . > > The TriX namespace resolves to that DTD version, so I would expect it > to be "standard": http://www.w3.org/2004/03/trix/trix-1/ > > As a result, we are getting parse errors when trying to read TriX that > conform to W3C DTD: > > ERROR riot:84 - [line: 2, col: 54] Unrecognized XML element: trix > > Can we agree that the DTD should be fixed? Presumably you mean fix the code (it's not DTD driven). > I can make a pull request. >>> >>> >>> >>> And please raise a JIRA then put the JIRA id in the PR. >>> >>> thanks >>> >>> Good. It would be best if the reader works with both forms. Andy > > Martynas > atomgraph.com > >>> >
Re: Incompatibility of TriX format
On 15/07/16 21:01, Martynas Jusevičius wrote: Created an issue: https://issues.apache.org/jira/browse/JENA-1211 Great - >>> > I can make a pull request. and PR awaited! Andy On Thu, Jul 14, 2016 at 2:06 PM, Andy Seabornewrote: On 14/07/16 11:38, Andy Seaborne wrote: On 14/07/16 10:10, Martynas Jusevičius wrote: Hey, Jena seems to use another DTD than the one hosted by W3C: https://www.w3.org/2004/03/trix/trix-1/trix-1.0.dtd vs. https://github.com/apache/jena/blob/master/jena-arq/src/main/java/org/apache/jena/riot/lang/TriX.java As per the comments : it uses http://www.hpl.hp.com/techreports/2004/HPL-2004-56.html From the first glance, at least the root element differs: vs. . The TriX namespace resolves to that DTD version, so I would expect it to be "standard": http://www.w3.org/2004/03/trix/trix-1/ As a result, we are getting parse errors when trying to read TriX that conform to W3C DTD: ERROR riot:84 - [line: 2, col: 54] Unrecognized XML element: trix Can we agree that the DTD should be fixed? Presumably you mean fix the code (it's not DTD driven). > I can make a pull request. And please raise a JIRA then put the JIRA id in the PR. thanks Good. It would be best if the reader works with both forms. Andy Martynas atomgraph.com
Re: Incompatibility of TriX format
Created an issue: https://issues.apache.org/jira/browse/JENA-1211 On Thu, Jul 14, 2016 at 2:06 PM, Andy Seabornewrote: > On 14/07/16 11:38, Andy Seaborne wrote: >> >> On 14/07/16 10:10, Martynas Jusevičius wrote: >>> >>> Hey, >>> >>> Jena seems to use another DTD than the one hosted by W3C: >>> https://www.w3.org/2004/03/trix/trix-1/trix-1.0.dtd vs. >>> >>> https://github.com/apache/jena/blob/master/jena-arq/src/main/java/org/apache/jena/riot/lang/TriX.java >>> >> >> As per the comments : it uses >> http://www.hpl.hp.com/techreports/2004/HPL-2004-56.html >> >>> >>> From the first glance, at least the root element differs: vs. >>> . >>> >>> The TriX namespace resolves to that DTD version, so I would expect it >>> to be "standard": http://www.w3.org/2004/03/trix/trix-1/ >>> >>> As a result, we are getting parse errors when trying to read TriX that >>> conform to W3C DTD: >>> >>>ERROR riot:84 - [line: 2, col: 54] Unrecognized XML element: trix >>> >>> Can we agree that the DTD should be fixed? >> >> >> Presumably you mean fix the code (it's not DTD driven). >> >> > I can make a pull request. > > > And please raise a JIRA then put the JIRA id in the PR. > > thanks > > >> >> Good. >> >> It would be best if the reader works with both forms. >> >> Andy >> >>> >>> Martynas >>> atomgraph.com >>> >> >
Re: Incompatibility of TriX format
On 14/07/16 11:38, Andy Seaborne wrote: On 14/07/16 10:10, Martynas Jusevičius wrote: Hey, Jena seems to use another DTD than the one hosted by W3C: https://www.w3.org/2004/03/trix/trix-1/trix-1.0.dtd vs. https://github.com/apache/jena/blob/master/jena-arq/src/main/java/org/apache/jena/riot/lang/TriX.java As per the comments : it uses http://www.hpl.hp.com/techreports/2004/HPL-2004-56.html From the first glance, at least the root element differs: vs. . The TriX namespace resolves to that DTD version, so I would expect it to be "standard": http://www.w3.org/2004/03/trix/trix-1/ As a result, we are getting parse errors when trying to read TriX that conform to W3C DTD: ERROR riot:84 - [line: 2, col: 54] Unrecognized XML element: trix Can we agree that the DTD should be fixed? Presumably you mean fix the code (it's not DTD driven). > I can make a pull request. And please raise a JIRA then put the JIRA id in the PR. thanks Good. It would be best if the reader works with both forms. Andy Martynas atomgraph.com
Re: Incompatibility of TriX format
On 14/07/16 10:10, Martynas Jusevičius wrote: Hey, Jena seems to use another DTD than the one hosted by W3C: https://www.w3.org/2004/03/trix/trix-1/trix-1.0.dtd vs. https://github.com/apache/jena/blob/master/jena-arq/src/main/java/org/apache/jena/riot/lang/TriX.java As per the comments : it uses http://www.hpl.hp.com/techreports/2004/HPL-2004-56.html From the first glance, at least the root element differs: vs. . The TriX namespace resolves to that DTD version, so I would expect it to be "standard": http://www.w3.org/2004/03/trix/trix-1/ As a result, we are getting parse errors when trying to read TriX that conform to W3C DTD: ERROR riot:84 - [line: 2, col: 54] Unrecognized XML element: trix Can we agree that the DTD should be fixed? Presumably you mean fix the code (it's not DTD driven). > I can make a pull request. Good. It would be best if the reader works with both forms. Andy Martynas atomgraph.com