...
- The ODM file must be a well-formed XML file. See the XML standard for details.
- The ODM file must conform to the XML Namespace standard. See the XML Namespace standard for details.
- The ODM file must contain only elements and attributes defined in the ODM standard schema or in a valid vendor extension schema, and must satisfy the rules about element nesting and the formats of attribute values and element bodies.
- The ODM file must contain a single (top-level) ODM element
- The ODM file must use the ODM v2.0 namespace, which is "http://www.cdisc.org/ns/odm/v2.0"
- The ODMVersion attribute on the top-level ODM element must be set to "2.0"
- The ODM file should begin with a prolog, or XML declaration, as this is considered a best practice
The XML schema for Version 2.0 of the ODM can be found at https://github.com/cdisc-org/DataExchange-ODM. Jira |
---|
showSummary | false |
---|
server | Issue Tracker (JIRA) |
---|
serverId | 85506ce4-3cb3-3d91-85ee-f633aaaf4a45 |
---|
key | ODM-33 |
---|
|
The final version of this specification will be posted at https://www.cdisc.org/standards/data-exchange/odm.
Code Block |
---|
|
info | Example of prolog and top-level ODM v2.0 XML element |
---|
| : |
Code Block |
---|
<?xml version="1.0" encoding="UTF-8"?>
<ODM xmlns="http://www.cdisc.org/ns/odm/v2.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance "
xsi:schemaLocation="http://www.cdisc.org/ns/odm/v2.0 ODM2-0-0.xsd"
ODMVersion="2.0"
FileOID="000-00-0000"
FileType="Transactional"
Description="Sample ItemData Extension"
AsOfDateTime="2022-06-04T07:57:00"
CreationDateTime="2022-06-06T10:30:00"> |
The semantic constraints are expressed throughout the rest of this document.
...
- The ODM file must be a well-formed JSON file. See the ECMA-404 standard for details.
- The ODM file must satisfy the rules about element nesting and the formats of values defined in the ODM standard.
Jira |
---|
server | Issue Tracker (JIRA) |
columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution | columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 85506ce4-3cb3-3d91-85ee-f633aaaf4a45 |
---|
key | ODM-34 |
The root object corresponds to the ODM element.- The ODMVersion attribute of the root object must be set to "2.0".
Code Block |
---|
language | js |
---|
title | Example of ODM v2.0 JSON file |
---|
|
{
"ODM": {
"ODMVersion": "2.0",
"FileOID": "000-00-0000",
"FileType": "Transactional",
"Description": "Sample ItemData Extension",
"AsOfDateTime": "2022-06-04T07:57:00",
"CreationDateTime": "2022-06-06T10:30:00",
"Study": {
"OID": "xxx",
"StudyName": "NIH Chronic Low Back Pain example",
"MetaDataVersion": {
"OID": "yyy",
...
}
}
}
}
|