55We use this repository to gather feedback from the community regarding the
66[ "JData Format Specification"] ( JData_specification.md ) , or JData format. Such
77feedback is crucial to finalize this file specification and help improve
8- it in the future once disseminated.
8+ it in the future once disseminated.
99
1010The latest version of the JData specification can be found in the file named
1111[ JData_specification.md] ( JData_specification.md ) . The specification is written
1212in the [ Markdown format] ( https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet )
1313for convenient editing and version control.
1414
15+ The version and status of the current draft are indicated in the header of
16+ [ JData_specification.md] ( JData_specification.md ) . Frozen releases are published
17+ at https://neurojson.org/jdata/ . A formal JSON Schema for validating JData
18+ documents is provided in [ schema/jdata_format_schema.json] ( schema/jdata_format_schema.json ) .
19+
1520## What is JData
1621
1722JData defines a set of ** standardized** , ** lightweight** and ** language-neutral** annotations
@@ -27,8 +32,8 @@ JSON format BJData/UBJSON for smaller file size and faster parsing. These data f
2732are JSON/BJData compliant and can be readily read without needing one to write their
2833own format. There exist numerous JSON parsers, abundant BJData/UBJSON parsers, and
2934extensively developed tools in the large JSON ecosystem - including utilities like
30- as ` jq ` , JSON-native NoSQL databases, and JSON-based standards such as JSON-schema
31- for validation, JSON- Reference and JSON-LD for data linking, JSON-Path for query etc.
35+ ` jq ` , JSON-native NoSQL databases, and JSON-based standards such as JSON Schema
36+ for validation, JSON Reference and JSON-LD for data linking, JSONPath for query, etc.
3237
3338![ ] ( ./images/JData_Diagram.png )
3439
@@ -48,8 +53,8 @@ draft of this file specification, including
4853 RFC (Request for comments) commit (where the entire file is removed
4954 and re-added so that every line appears in such commit). One can
5055 write short comments as well as post replies on this RFC page.
51- - The latest RFC commit is based on ** Draft 2 (version v0.8) ** . Please use
52- [ this link ] ( https://github.com/NeuroJSON/jdata/commit/6bb02c8a654938451d686c4a7c2b1b0619e7cf17 ) to comment .
56+ - For feedback on the current version, the [ Issues section ] ( https://github.com/NeuroJSON/jdata/issues )
57+ is the preferred channel .
5358 - To add a comment, you need to first register a github account, and then
5459 browse the above RFC page. When hovering your cursor over each line, a
5560 "plus" icon is displayed, clicking it will allow one to comment on a
0 commit comments