{"slug":"oip-what-is-json","verification":{"valid":false,"entries":5,"head":null,"reason":"virtual_oip_sources_are_generated_references_not_hash_chained"},"count":5,"sources":[{"id":"json-s1","type":"protocol","url":"https://datatracker.ietf.org/doc/html/rfc8259","title":"RFC 8259: The JavaScript Object Notation (JSON) Data Interchange Format","quote":"JSON can represent four primitive types (strings, numbers, booleans, and null) and two structured types (objects and arrays).","summary":"The IETF standard defining JSON syntax, types, and parsing requirements.","author":"T. Bray","publisher":"IETF","date":"2017-12-01","claim_ids":["json-c1","json-c2","json-c3","json-c4"],"link_status":"ok","hash":"rfc8259json00001"},{"id":"json-s2","type":"protocol","url":"https://ecma-international.org/publications-and-standards/standards/ecma-404/","title":"ECMA-404: The JSON Data Interchange Format","quote":"A JSON value can be an object, array, number, string, true, false, or null.","summary":"The ECMA standard specifying JSON's exact grammar and data model.","author":"Ecma International","publisher":"Ecma International","date":"2017-01-01","claim_ids":["json-c1","json-c2","json-c3","json-c4"],"link_status":"ok","hash":"ecma404json00002"},{"id":"json-s3","type":"protocol","url":"https://www.json.org/json-en.html","title":"Introducing JSON","quote":"JSON is a lightweight data-interchange format. It is easy for humans to read and write. It is easy for machines to parse and generate.","summary":"The original JSON specification page by Douglas Crockford, describing JSON's design goals and simplicity.","author":"Douglas Crockford","publisher":"json.org","date":"2001-01-01","claim_ids":["json-c5","json-c6"],"link_status":"ok","hash":"jsonorg000000003"},{"id":"json-s4","type":"protocol","url":"https://miscsubjects.com/api/file/docs/BUILD_SPEC.md","title":"OIP BUILD_SPEC — JSON as the executable map","quote":"The JSON is the structured operating map a model reads without guessing. It contains routes, object ids, invocation shapes, proof links, and repair paths.","summary":"The OIP build specification defining how JSON serves as the machine-native substrate for all invocations, receipts, and repairs.","claim_ids":["json-c6"],"link_status":"ok","hash":"oipbuildspecjson04"},{"id":"json-s5","type":"protocol","url":"https://miscsubjects.com/api/dispatch?map=1&format=markdown","title":"Live OIP capability tree","quote":"root > shelf > system article > capability article > receipt","summary":"Public recursive capability tree showing OIP objects expressed as JSON.","claim_ids":["json-c6"],"link_status":"ok","hash":"oipmapjson000005"}]}