- From: Richard Cyganiak <richard@cyganiak.de>
- Date: Mon, 3 Jul 2017 14:26:50 +0100
- To: Jan Wielemaker <J.Wielemaker@vu.nl>
- Cc: Wouter Beek <wouter@triply.cc>, Gregg Kellogg <gregg@greggkellogg.net>, Dan Brickley <danbri@google.com>, Ivan Herman <ivan@w3.org>, public-rdf-comments Comments <public-rdf-comments@w3.org>, "Peter F. Patel-Schneider" <pfpschneider@gmail.com>
Hi Jan, > On 1 Jul 2017, at 12:49, Jan Wielemaker <J.Wielemaker@vu.nl> wrote: > > It has always been in my mind that there should be white space between the three elements of a triple. I really dislike the (I fear) fact that > this has been abandoned. It complicates managing triple files using > generic text tools significantly. With the demand to have comments on > their own line and white space between the three elements you can easily > process n-triples files with very simple tools and you can give more > reliable syntax errors. If we are allowed to write > > _:a<http://example.com/p>"42" ^^ xsd:integer . > > n-triples files get IMHO less readable, harder to parse and it gets > harder to give sensible error messages while I see no benefits. The N-Triples document defines two languages: “N-Triples” and “Canonical N-Triples”. The latter requires a single space between RDF terms and does not permit comments, and is reasonably well-suited to processing with line-based text tools. Producers are encouraged to produce Canonical N-Triples. https://www.w3.org/TR/n-triples/#canonical-ntriples Best, Richard
Received on Monday, 3 July 2017 13:27:20 UTC