Wrong media type for Retrieve Instance transaction about dicom-server HOT 5 CLOSED

Thank you, @hackermd ! That certainly simplifies the retrieve transactions and makes all of them consistent with each other. We're looking into this now, and it certainly makes sense. Thanks! We'll keep you posted here.

from dicom-server.

Great! Thanks for looking into it @StevenBorg

from dicom-server.

@hackermd After some discussion, our take is that we should adopt the newer framework, even prior to acceptance under the standard, while still maintaining backward compatibility (in this case) for APIs which might be using the current standard. Do you see any concerns with this approach?

from dicom-server.

No concerns. I agree that this would be the best approach.

The "newer" framework has actually always been the standard - at least it was supposed to. The goal of Supplement 183 was to refactor the documentation of Part 18 without actually changing the behavior. Unfortunately, a few things got broken and we are currently trying to correct those. However, since Supplement 183 was officially accepted, we should probably consider application/dicom to be standard compliant or at least support it in a backwards compatible manner. We are going to do the same client-side (see ImagingDataCommons/dicomweb-client#43).

from dicom-server.

Issue is fixed. Closing

from dicom-server.