Often a single license can be used to represent the licensing terms. Sometimes it is necessary to include a choice of one or more licenses or some combination of license identifiers. Examples: "LGPL-2.1-only OR MIT", "LGPL-2.1-only AND MIT", "GPL-2.0-or-later WITH Bison-exception-2.2".
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-06-13 UTC."],[[["\u003cp\u003eThe provided data describes a JSON format for representing license information.\u003c/p\u003e\n"],["\u003cp\u003eThe JSON structure includes two main fields: \u003ccode\u003eexpression\u003c/code\u003e and \u003ccode\u003ecomments\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eexpression\u003c/code\u003e field, a string, is designed to contain license identifiers and can include complex combinations of licenses using logical operators like "OR" and "AND".\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003ecomments\u003c/code\u003e field, also a string, allows for the inclusion of additional information.\u003c/p\u003e\n"]]],[],null,["# License\n\n- [JSON representation](#SCHEMA_REPRESENTATION)\n\nLicense information."]]
