[Neuroimaging] JSON-LD and DICOM?

[Steve Pieper]

To avoid repetition, I'll just point to my comments 3 years ago on this
topic [1].  Since then we've continued to work on DICOM in research
contexts [2] and we still think it's a neat idea.  The software is coming
along nicely too [3].

Cheers,
-Steve

[1] https://mail.scipy.org/pipermail/nipy-devel/2014-July/010143.html

[2] https://peerj.com/articles/2057/

[3] https://github.com/QIICR/dcmqi


On Mon, Jul 3, 2017 at 8:40 AM, Bennet Fauber <bennet at umich.edu> wrote:

> So, presumably, compatibility will be maintained if other software
> reads and uses vox_offset.
>
> It looks, from a brief scan, that the size of the JSON extension is
> not fixed, as it can accommodate multiple scanner vendors' versions of
> DICOM?
>
> Sorry for the naive questions.
>
> On Mon, Jul 3, 2017 at 8:29 AM, Matthew Brett <matthew.brett at gmail.com>
> wrote:
> > Hi,
> >
> > On Mon, Jul 3, 2017 at 1:19 PM, Bennet Fauber <bennet at umich.edu> wrote:
> >> With respect to Romain's comment, yes, backward compatibility is
> >> important.  How will this affect NIfTI compatibility with other
> >> software?  Is this proposed change to the NIfTI format going to be
> >> NIfTI-2?  Is there some sort of review process that this is going
> >> through like NIfTI-1?
> >
> > I think we're OK with backwards compatibility, because the JSON header
> > extension would be a "header extension" in this sense:
> >
> > https://nifti.nimh.nih.gov/nifti-1/documentation/faq#Q21
> >
> > Any compatible NIfTI1 reader should happily skip over the header
> > extension data it does not recognize - and I think that's true of the
> > major packages.
> >
> > As for the review process, that's what we're doing in these
> > discussions - I drafted up a spec a while ago, that is here:
> >
> > https://github.com/nipy/nibabel/wiki/json-header-extension
> >
> > That was the first pass.  See this thread for the initial discussion:
> >
> > https://mail.scipy.org/pipermail/nipy-devel/2014-July/010087.html
> >
> > I'm just in the process of finishing up a second pass. When I've done
> > that, and we've done another pass at discussion here, I'll email out
> > to the AFNI / SPM / FSL mailing lists to see if they've got any
> > thoughts.   Can you think of anywhere else the discussion should go?
> >
> > Cheers,
> >
> > Matthew
> > _______________________________________________
> > Neuroimaging mailing list
> > Neuroimaging at python.org
> > https://mail.python.org/mailman/listinfo/neuroimaging
> _______________________________________________
> Neuroimaging mailing list
> Neuroimaging at python.org
> https://mail.python.org/mailman/listinfo/neuroimaging
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/neuroimaging/attachments/20170703/9ddd28e1/attachment-0001.html>