["Name", "Session", "Score", "Completed"]
@@ -43,13 +13,13 @@
["Deloise", "2012A", 19, true]
CSV seems so easy that many programmers have written code to generate it themselves, and almost every implementation is different. Handling broken CSV files is a common and frustrating task. CSV has no standard encoding, no standard column separator and multiple character escaping standards. String is the only type supported for cell values, so some programs attempt to guess the correct types.
+CSV seems so easy that many programmers have written code to generate it themselves, and almost every implementation is different. Handling broken CSV files is a common and frustrating task. CSV has no standard encoding, no standard column separator and multiple character escaping standards. String is the only type supported for cell values, so some programs attempt to guess the correct types.
-JSON Lines handles tabular data cleanly and without ambiguity. Cells may use the standard JSON types.
+JSON Lines handles tabular data cleanly and without ambiguity. Cells may use the standard JSON types.
-The biggest missing piece is an import/export filter for popular spreadsheet programs so that non-programmers can use this format.
+The biggest missing piece is an import/export filter for popular spreadsheet programs so that non-programmers can use this format.
-{"name": "Gilbert", "wins": [["straight", "7♣"], ["one pair", "10♥"]]}
@@ -58,11 +28,10 @@
{"name": "Deloise", "wins": [["three of a kind", "5♣"]]}
JSON Lines' biggest strength is in handling lots of similar nested data structures. One .jsonl file is easier to work with than a directory full of XML files.
JSON Lines' biggest strength is in handling lots of similar nested data structures. One .jsonl file is easier to work with than a directory full of XML files.
If you have large nested structures then reading the JSON Lines text directly isn't recommended. Use the "jq" tool to make viewing large structures easier:
+If you have large nested structures then reading the JSON Lines text directly isn't recommended. Use the "jq" tool to make viewing large structures easier:
grep pair winning_hands.jsonl | jq .
- This page describes the JSON Lines text format, also called newline-delimited JSON. - JSON Lines is a convenient format for storing structured data that may be processed - one record at a time. It works well with unix-style text processing tools and shell - pipelines. It's a great format for log files. It's also a flexible format for passing - messages between cooperating processes. -
-- The JSON Lines format has three requirements: -
-- JSON allows encoding Unicode strings with only ASCII escape sequences, however those - escapes will be hard to read when viewed in a text editor. The author of the JSON Lines - file may choose to escape characters to work with plain ASCII files. -
-- Encodings other than UTF-8 are very unlikely to be valid when decoded as UTF-8 so the chance - of accidentally misinterpreting characters - in JSON Lines files is low. -
-- The most common values will be objects or arrays, but any JSON value is permitted. -
-- See json.org for more information about JSON values. -
-'\n'
-
- This means '\r\n' is also supported because surrounding white space is
- implicitly ignored when parsing JSON values.
-
- The last character in the file may be a line separator, and it will be treated - the same as if there was no line separator present. -
-
- JSON Lines files may be saved with the file extension .jsonl.
-
- Stream compressors like gzip or bzip2 are recommended for
- saving space, resulting in .jsonl.gz or .jsonl.bz2 files.
-
- MIME type may be application/jsonl, but this is not yet standardized; any help
- writing the RFC would be greatly appreciated (see issue).
-
- Text editing programs call the first line of a text file "line 1". The first value in a - JSON Lines file should also be called "value 1". -
-+ This page describes the JSON Lines text format, also called newline-delimited JSON. + JSON Lines is a convenient format for storing structured data that may be processed + one record at a time. It works well with unix-style text processing tools and shell + pipelines. It's a great format for log files. It's also a flexible format for passing + messages between cooperating processes. +
++ The JSON Lines format has three requirements: +
++ JSON allows encoding Unicode strings with only ASCII escape sequences, however those + escapes will be hard to read when viewed in a text editor. The author of the JSON Lines + file may choose to escape characters to work with plain ASCII files. +
++ Encodings other than UTF-8 are very unlikely to be valid when decoded as UTF-8 so the chance + of accidentally misinterpreting characters + in JSON Lines files is low. +
++ The most common values will be objects or arrays, but any JSON value is permitted. +
++ See json.org for more information about JSON values. +
+'\n'
+
+ This means '\r\n' is also supported because surrounding white space is
+ implicitly ignored when parsing JSON values.
+
+ The last character in the file may be a line separator, and it will be treated + the same as if there was no line separator present. +
+
+ JSON Lines files may be saved with the file extension .jsonl.
+
+ Stream compressors like gzip or bzip2 are recommended for
+ saving space, resulting in .jsonl.gz or .jsonl.bz2 files.
+
+ MIME type may be application/jsonl, but this is not yet standardized; any help
+ writing the RFC would be greatly appreciated (see issue).
+
+ Text editing programs call the first line of a text file "line 1". The first value in a + JSON Lines file should also be called "value 1". +
diff --git a/on_the_web/index.html b/on_the_web/index.md similarity index 71% rename from on_the_web/index.html rename to on_the_web/index.md index d6d5c42..42334d4 100644 --- a/on_the_web/index.html +++ b/on_the_web/index.md @@ -1,41 +1,10 @@ - - - - - - - - - - -pytest-reportlog is a pytest plugin which writes testing report data in JSON lines format
- +NDJSON is a similar format that also allows blank lines
Bubbles supports JSON Lines datastores
@@ -47,17 +16,17 @@Graylog GELF is format for log messages, their stream is de-facto JSON lines.
Scrapy is a framework for web scraping & crawling, it supports and recommends JSON lines since long -- it might've even coined the term.
- +ClickHouse is an open source column-oriented DBMS. It supports JSON lines as JSONEachRow format for input and output.
-Dataflow kit is a web scraping open source framework written in Go. JSON Lines is one of the supported formats for storing results.
+Dataflow kit is a web scraping open source framework written in Go. JSON Lines is one of the supported formats for storing results.
dart uses JSON Lines as one of the possible reporters when running tests.
Apache Spark uses JSONL for reading and writing JSON data.
ArangoDB is an open source multi-model database. The JSON lines format allows to import huge amounts of documents sequentially (via arangoimport).
- +Rumble is a JSONiq engine that runs on top of Spark. It can process datasets in the JSON lines format that have billions of objects and more.
Neo4j the open-source graph database supports JSONL export and import via its standard library procedures apoc.export/import.json to allow stream processing of nodes and relationships.
CSS HTML Validator for Windows v22.0211+ now supports JSON Lines syntax checking.
-Miller supports JSON Lines format as input.
-Miller supports JSON Lines format as input.
diff --git a/stylesheets/stylesheet.css b/stylesheets/stylesheet.css index 4e68f60..6744299 100644 --- a/stylesheets/stylesheet.css +++ b/stylesheets/stylesheet.css @@ -90,7 +90,7 @@ header h2 { } .inner { - width: 620px; + width: 700px; margin: 0 auto; } diff --git a/validator/index.html b/validator/index.html deleted file mode 100644 index 240b6ab..0000000 --- a/validator/index.html +++ /dev/null @@ -1,52 +0,0 @@ - - - - - - - - - - - - - - - - -