Meta tags:
Headings (most frequently used words):
json, lines, line, is, documentation, for, the, text, file, format, utf, encoding, each, valid, value, terminator, conventions,
Text of the page (most frequently used words):
json (23), the (17), lines (11), line (8), file (8), value (8), text (6), for (6), files (6), #format (6), this (4), also (4), may (4), but (4), not (4), jsonl (4), with (4), terminator (4), last (3), when (3), values (3), valid (3), utf (3), page (2), first (2), called (2), any (2), see (2), like (2), are (2), recommended (2), space (2), including (2), after (2), and (2), must (2), byte (2), org (2), will (2), characters (2), encoding (2), ascii (2), escape (2), tactile, theme, maintained, generated, 2025, utc, jekyll, ian, ward, jason, long, report, bug, make, suggestion, editing, programs, call, should, mime, type, yet, standardized, help, writing, rfc, would, greatly, appreciated, issue, application, stream, compressors, saving, resulting, bz2, bzip2, gzip, saved, extension, conventions, strongly, required, every, makes, generating, concatenating, easier, follows, means, supported, because, surrounding, white, implicitly, ignored, parsing, definition, most, common, objects, arrays, permitted, blank, null, each, standard, order, mark, feff, included, encodings, other, than, very, unlikely, decoded, chance, low, accidentally, misinterpreting, allows, unicode, strings, only, sequences, however, those, escapes, hard, read, viewed, editor, author, choose, work, plain, has, three, requirements, describes, newline, delimited, convenient, storing, structured, data, that, processed, one, record, time, works, well, unix, style, processing, tools, shell, pipelines, great, log, flexible, passing, messages, between, cooperating, processes, web, validator, examples, home, documentation,
Text of the page (random words):
json lines json lines documentation for the json lines text file format home examples validator on the web json org 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 1 utf 8 encoding 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 like the json standard a byte order mark u feff must not be included 2 each line is a valid json value the most common values will be objects or arrays but any json value is permitted e g null is a valid value but a blank line is not see json org for a definition of json values 3 line terminator is n this means r n is also supported because surrounding white space is implicitly ignored when parsing json values including a line terminator after the last json value in a file is strongly recommended but not required including a line terminator after every json value makes generating and concatenating json lines files easier if a line terminator follows the last json value in a file it must be the last byte in the file conventions 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 report a bug or make a suggestion tactile theme by jason long this page is maintained by ian ward generated by jekyll on 2025 12 02 16 49 52 utc
|