The Library of Congress > Linked Data Service > LC Subject Headings (LCSH)

JSON (Document markup language)

  • URI(s)

  • Instance Of

  • Scheme Membership(s)

  • Collection Membership(s)

  • Variants

    • JavaScript Object Notation (Document markup language)
  • Broader Terms

  • Closely Matching Concepts from Other Schemes

  • Sources

    • found: Work cat.: XML Prague (Conference) (2012 : Prague, Czech Republic). XML Prague 2012, 2012:pp. 63-64 (JSON; XML and JSON have become the dominant formats for exchanging data on the Internet, and applications frequently need to send and receive data in many different JSON-based or XML-based formats; JSON programmers)
    • found: Introducing JSON website, Mar. 4, 2014:home page (JSON (JavaScript Object Notation) is a lightweight data-interchange format. It is easy for humans to read and write. It is easy for machines to parse and generate. It is based on a subset of the JavaScript Programming Language, Standard ECMA-262 3rd Edition - December 1999. JSON is a text format that is completely language independent but uses conventions that are familiar to programmers of the C-family of languages, including C, C++, C#, Java, JavaScript, Perl, Python, and many others. These properties make JSON an ideal data-interchange language.)
    • found: Wikipedia, Mar. 4, 2014:JSON (JSON, or JavaScript Object Notation, is an open standard format that uses human-readable text to transmit data objects consisting of attribute--value pairs. It is used primarily to transmit data between a server and web application, as an alternative to XML. Although originally derived from the JavaScript scripting language, JSON is a language-independent data format, and code for parsing and generating JSON data is readily available in a large variety of programming languages. Filename extension: .json; Internet media type: application/json; Uniform Type Identifier: public.json; Type of format: Data interchange; Extended from: JavaScript)
    • found: JSON tutorial, via website, Mar. 4, 2014(JSON: JavaScript Object Notation. JSON is syntax for storing and exchanging text information. Much like XML. JSON is smaller than XML, and faster and easier to parse. What is JSON?: JSON stands for JavaScript Object Notation. JSON is lightweight text-data interchange format. JSON is language independent. JSON is "self-describing" and easy to understand. JSON uses JavaScript syntax for describing data objects, but JSON is still language and platform independent. JSON parsers and JSON libraries exists for many different programming languages.)
    • found: An introduction to JavaScript Object Notation (JSON) in JavaScript and .NET, via Microsoft Development Network website, Mar. 4, 2014(When designing an application that will communicate with a remote computer, a data format and exchange protocol must be selected. There are a variety of open, standardized options, and the ideal choice depends on the applications requirements and pre-existing functionality. ... While most browsers can construct, send, and parse XML, JavaScript Object Notation (or JSON) provides a standardized data exchange format that is better-suited for Ajax-style web applications. JSON is an open, text-based data exchange format (see RFC 4627). Like XML, it is human-readable, platform independent, and enjoys a wide availability of implementations. Data formatted according to the JSON standard is lightweight and can be parsed by JavaScript implementations with incredible ease, making it an ideal data exchange format for Ajax web applications. Since it is primarily a data format, JSON is not limited to just Ajax web applications, and can be used in virtually any scenario where applications need to exchange or store structured information as text.)
  • Change Notes

    • 2014-03-04: new
    • 2014-06-14: revised
  • Alternate Formats

Suggest terminology

The LC Linked Data Service welcomes any suggestions you might have about terminology used for a given heading or concept.

Would you like to suggest a change to this heading?

Please provide your name, email, and your suggestion so that we can begin assessing any terminology changes.

Fields denoted with an asterisk (*) are required.