[SERVER-17049] Allow $ref and $schema keywords to support JSON Schema management Created: 26/Jan/15 Updated: 05/Mar/18 Resolved: 26/Jan/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | JavaScript, Querying, Usability |
| Affects Version/s: | 2.6.7, 3.0.0-rc6 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Trivial - P5 |
| Reporter: | Marcel Bennett | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
JSON Schema requires two fields to include the $ prefix. First is the $schema keyword that defines the version and URI of the schema to be stored. Second is the $ref used to describe pointers to additional schema data. More info on JSON Schema is available here: http://json-schema.org/documentation.html As JSON Schema is becoming a more heavily used tool for JSON data management As JSON is requested for config file support I see it as a useful exception to the no $ prefix error and it could even be useful to allow $ref resolution and caching in future (as a separate issue). |
| Comments |
| Comment by Marcel Bennett [ 27/Jan/15 ] |
|
Ideally the $data keyword should also be allowed as that is being possibly added as part of JSON Schema draft 5. $data is a Relative JSON Pointer and could potentially be required as such and an option to resolve references could be made available. |
| Comment by Marcel Bennett [ 26/Jan/15 ] |
|
It's not a duplicate at all. Not even really a subset. That's why I created it.
The only way to store JSON Schema files 'as is' is to have this option. As it is now I cannot store a JSON Schema file without manipulating it first which is a major inhibitor to the purpose for which I want to use Mongo. |
| Comment by Ramon Fernandez Marina [ 26/Jan/15 ] |
|
mbennett@uecomm.com.au, this ticket is a subset of Regards, |