@@ -37,7 +37,7 @@ way the image was acquired. Axes have natural labels, expressing meaning,
3737such as "time" or "slice", and they may have tick labels such as acquisition
3838time. The scanner captures this information, but typical image formats cannot
3939store it, so it is easy to lose metadata and make analysis errors; see
40- :doc: ` biap_0006 `.
40+ :ref: ` biap6 `.
4141
4242We plan to expand Nibabel's API to encode axis and tick labels by integrating
4343the Xarray package: `http://xarray.pydata.org `_. Xarray simplifies HDF5
@@ -49,12 +49,12 @@ data, or save them with the image. We plan to:
4949* Develop HDF5 equivalents of standard image formats, for serialization of
5050 data with labels.
5151* Expand the current standard image format, NIfTI, to store labels in a JSON
52- addition to image metadata: ` https://github.com/nipy/nibabel/wiki/BIAP3 `_ .
52+ addition to image metadata: :ref: ` biap3 ` .
5353* Read image metadata from DICOM, the standard scanner format.
5454
55- Reading and attaching DICOM data will start with code integrated from Dcmstack,
56- by Brendan Moloney: ` https://github.com/moloney/dcmstack `_ ; see:
57- ` https://github.com/nipy/nibabel/wiki/BIAP4 `_ .
55+ Reading and attaching DICOM data will start with code integrated from
56+ ` Dcmstack < https://github.com/moloney/dcmstack >`_, by Brendan Moloney ; see:
57+ :ref: ` biap4 ` .
5858
5959DICOM metadata is often hidden inside "private" DICOM elements that need
6060specialized parsers. We want to expand these parsers to preserve full metadata
0 commit comments