This means that all existing N-Triples parsers are lenient in that they process documents that are not valid N-Triples documents. This, however, does not make them too lenient as there is no requirement that an N-Triples processor reject inputs that are not N-Triples documents. This does mean that Canonical N-Triples documents are not valid N-Triples documents. peter PS: Of course what it really means is that the grammar section of the N-Triples document needs to be changed. On 06/28/2017 08:50 AM, Wouter Beek wrote: >> So it seems to me that spaces are not allowed anywhere in [1] in N-Triples, i.e., >> >> <x:y> <x:y> <x:y> . >> >> is not a valid N-Triples triple. > > I do follow your reasoning here, but this would mean that all existing > N-Triples parsers are too lenient. >Received on Wednesday, 28 June 2017 17:39:02 UTC
This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:41:56 UTC