DICOM PS3.18 2024e - Web Services |
---|
The value or values of a given DICOM attribute are given in the "Value" array. The value multiplicity (VM) is not contained in the DICOM JSON object.
"Value": [ "bar", "foo" ]
"Value": [ "bar" ]
For those VRs specified in PS3.5 as being affected by Specific Character Set (0008,0005) and permitting multiple delimiter-separated string Values, i.e., SH, LO, PN, and UC, the bit combination 05/12 (0x5C) is used to separate Values into the “Value” array, regardless of whether the Graphic Character represented by 05/12 is the BACKSLASH (such as in the Default Character Set) or the YEN SIGN (such as in [JIS X 0201]). See Section 6.1.2.3 “Encoding of Character Repertoires” in PS3.5. The expected behavior on transcoding from JSON to other representations and vice versa is to preserve the semantics of multiple separate values, whether they are encoded as a multi-valued array in JSON or as a delimiter-separated character stream in PS3.5 representations.
Graphic Characters that match the delimiter specified for the Character Set for multi-valued VRs cannot be represented as Values in some Character Sets when encoded in PS3.5 representations. Accordingly, it is inadvisable to use a Graphic Character within a JSON value for the SH, LO, PN, and UC VRs such as a BACKSLASH or YEN SIGN that will be represented as 05/12 in the Default Character Set or [JIS X 0201], because when transcoding to a PS3.5 representation, since there is no escape mechanism defined, they may inadvertently be interpreted as delimiters, splitting a Value. For example, DOS-style paths that use a BACKSLASH as a file component separator cannot be encoded within in a single Value of one of the affected VRs.
DICOM PS3.18 2024e - Web Services |
---|