...
This document explains the principles of the JSON representation, and the conventions used. These are based on the "Flickr conventions" for JSON (https://www.flickr.com/services/api/response.json.html).
Note: The Data Exchange Standards team is still considering the development of a native JSON schema so that JSON files can be checked by a validating JSON parser to test that the file is syntactically valid.
Main principles
For the ODM JSON implementation, the following main principles apply:
...
- XML text content is treated as a name-value pair with the name being "_content".
Example:Jira server Issue Tracker (JIRA) columnscolumnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 85506ce4-3cb3-3d91-85ee-f633aaaf4a45 key ODM-10
Code Block | ||
---|---|---|
| ||
"ReasonForChange": {"_content": "Investigator typing error"} |
...
Code Block | ||
---|---|---|
| ||
{ "CreationDateTime": "2011-10-24T10:05:00", "Description": "JSON test", "FileOID": "JSON_Test_2020", "FileType": "Snapshot", "Granularity": "Metadata", "ODMVersion": "2.0", "Originator": "MySystem", ... ... } |
...
Pagenav2 |
---|