-
Notifications
You must be signed in to change notification settings - Fork 81
-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DICOM JSON Format #128
Comments
Thank you for reaching out, @vsaase. It is true that this project is currently not covering conversions to/from JSON, but it makes sense to have that eventually, potentially as one more crate in the DICOM-rs umbrella. It only does not exist yet because the closest topics in the roadmap have been to incorporate more functionalities specific to DICOM representations and protocols, but a DICOM Web initiative should be bound to happen eventually. With that said, I believe that the shortest path towards converting a JSON value into an in-memory DICOM object would be to convert each element into an Please feel free to ask follow-up questions on this. And if there is interest from you to contribute to the project with a DICOM JSON proof of concept, I would also be more than grateful. |
Well, actually, I have something coming like this... I will try to submit another PR soon. Regards
|
Great! I will have a look later. I have been working on dicomweb in my spare time in the last few days |
Hi,
many thanks for your work!
Do you maybe have a working prototype for converting from DICOM binary format to JSON and back? Or any ideas on how to achieve this elegantly? Would be useful form DICOMWeb interaction.
I was just experimenting a bit with Serde:
Then this is the user facing version:
I believe Serde has much more flexibility for a better API than that. Just wanted to ask your opinion before diving in deeper..
Victor
The text was updated successfully, but these errors were encountered: