Proposal to Make RFC 8785 Mandatory for DICOM/JSON Implementations
35 views
Skip to first unread message
Mathieu Malaterre
Jun 19, 2025, 3:27:27 AMJun 19
to DICOM Forum
Dear DICOM/JSON Implementers,
I would like to propose making RFC 8785 (1) mandatory for DICOM/JSON Model (2). Since its publication in June 2020, multiple implementations in various programming languages have become available (3).
Before proceeding further, I’d like to ask: are any of you already using RFC 8785 in your implementations? If so, how well has it worked in practice?
In my own environment, adopting this RFC would be beneficial. However, I recognize that making it mandatory might discourage implementers from fully exposing the DICOM JSON model as an API in their products.
At present, my main challenge lies in handling certain Value Representations—specifically DS, FL, FD, and IS (4). I’d also like to remind implementers that C++'s std::to_chars/from_chars has been standardized since C++17 (5), which may help address some of these difficulties.
Best regards,
I would like to propose making RFC 8785 (1) mandatory for DICOM/JSON Model (2). Since its publication in June 2020, multiple implementations in various programming languages have become available (3).
Before proceeding further, I’d like to ask: are any of you already using RFC 8785 in your implementations? If so, how well has it worked in practice?
In my own environment, adopting this RFC would be beneficial. However, I recognize that making it mandatory might discourage implementers from fully exposing the DICOM JSON model as an API in their products.
At present, my main challenge lies in handling certain Value Representations—specifically DS, FL, FD, and IS (4). I’d also like to remind implementers that C++'s std::to_chars/from_chars has been standardized since C++17 (5), which may help address some of these difficulties.
Best regards,
Reply all
Reply to author
Forward
0 new messages