Skip to content
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

Update README.md #222

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,14 +2,15 @@ Open Digital Specimen (openDS) is the cornerstone of DiSSCo's vision for a seaml

As a digital surrogate on the internet, openDS encapsulates the essence of a "Digital Specimen," offering a solution for collections ranging from marine specimens to botanical and mineralogical holdings. Leveraging established biodiversity information standards such as Darwin Core, Minimal Information Digital Specimen, Latimer Core, Access to Biological Collection Data Schema, Extension FOR Geosciences, and the emerging Global Biodiversity Information Facility Unified Model, openDS harmonises and elevates the quality and machine actionability of scientific data.

The openDS data model consists of a documented set of [JSON schemas](https://schemas.dissco.tech/) that describe the Digital Specimen and related digital objects. The documentation can be found here: https://dev.terms.dissco.tech/
The openDS data model consists of a documented set of [JSON schemas](https://schemas.dissco.tech/) that describe the Digital Specimen and related digital objects. The documentation can be found here: https://terms.dissco.tech/
Version v0.3 of openDS was community reviewed and will be used in a first production version (Minimum Valuable Product) of the core digital specimen infrastructure.

## How to become involved and contribute
Linking third-party/extended specimen data together, as openDS proposes, requires many stakeholders to test and adopt the specification. This is especially the case for integrating data at multiple levels, like: specimen, collection types, species, genomics, and cross-discipline to geology, genomics, etc. This necessitates global collaboration among all players in the landscape converging towards a single specification as far as possible.

You can become involved and contribute by making comments through Github issues. For this, we created two simple [Github templates](https://github.com/DiSSCo/openDS/issues/new/choose): one for feedback on a term and another for general comments. When commenting on a term please include the term name, for example, dwc:highestBiostratigraphicZone. Note that most terms are coming from existing standards but a few are openDS specific. We aim to apply controlled vocabularies for terms where appropriate to increase data quality and interoperability. These are not yet part of the documentation.

DiSSCo is supported by different EU grants. A dedicated development team and other collaborators working towards a robust specification. The implementations can be seen in our current [Sandbox](https://sandbox.dissco.tech/). Note that the openDS data model v0.3 has not yet been implemented in our sandbox annotations portal (sandbox.dissco.tech), which still uses version v0.2. However, some JSON examples of v0.3 can be found through our development API, for example, https://dev.dissco.tech/api/v1/digital-specimen.
DiSSCo is supported by different EU grants. A dedicated development team and other collaborators are working towards a robust openDS specification. The implementation (under construction) can be tried out in our [Sandbox](https://sandbox.dissco.tech/). A JSON example of v0.3 in progress can be found through our development API, for example, https://dev.dissco.tech/api/v1/digital-specimen.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We are at v0.4.0 already. We skipped v0.3 in sandbox




Loading