Skip to content

Commit 369af56

Browse files
author
Carsten
committed
Update specification
- Suggesting linguistic and typographic fixes here and there.
1 parent 2ccd4cd commit 369af56

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

docs/specification/index.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,10 @@
11
# What is a FAIR-IO
2-
A FAIR-IO bundle combines the necessary acquisition and provenance metadata together with multi-resolution, chunked binary data in a single cloud-compatible format for simplified sharing and re-use.
2+
A FAIR-IO (FAIR Image Object) bundle combines acquisition and provenance metadata together with multi-resolution, chunked binary pixel data in a single cloud-compatible format for simplified sharing and re-use. As such, FAIR-IO implements
3+
a FAIR Digital Object (FDO, DOI:10.5281/zenodo.7824714) as illustrated below.
34

45
![FAIR-IO concept](FAIR-IO_10.5281-zenodo.10512531.png)
56

7+
FAIR-IO is based on the following recommendations for binary (pixel) data and textual metadata.
68
## Recommendations for easily sharable binary data:
79
<div>
810
<table style="margin-left:5px;">
@@ -13,7 +15,7 @@ A FAIR-IO bundle combines the necessary acquisition and provenance metadata toge
1315
<li>Use data formats that store binary data with multiple resolutions in a single cloud-compatible, chunkable format. These enable web-optimised data access and high-performance cloud storage</li>
1416
<li>Store data in a public available space accessible via a data specific URL</li>
1517
</ul>
16-
<b>Serialization example:</b> ome-zarr (<a href="https://doi.org/10.1007/s00418-023-02209-1"> About</a> |<a href=""> Tools</a>)
18+
<b>Example format:</b> ome-zarr (<a href="https://doi.org/10.1007/s00418-023-02209-1"> About</a> |<a href=""> Tools</a>)
1719
</td>
1820
</tr>
1921

@@ -32,10 +34,9 @@ A FAIR-IO bundle combines the necessary acquisition and provenance metadata toge
3234
<li>Use metadata formats that store metadata in a machine readable form, that means </li>
3335
<li>store data in a public available space accessible via a data specific URL</li>
3436
</ul>
35-
<b>Serialization example:</b> JSONLD (<a href=""> About</a> |<a href=""> Tools</a>), Turtle (<a href=""> About</a> |<a href=""> Tools</a>)
37+
<b>Example formats:</b> JSON-LD (<a href=""> About</a> |<a href=""> Tools</a>), Turtle (<a href=""> About</a> |<a href=""> Tools</a>)
3638
</td>
3739
</tr>
38-
3940
</table>
4041
</div>
4142

0 commit comments

Comments
 (0)