Skip to content

Typo #4

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

Open
wants to merge 1 commit into
base: gh-pages
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
2 changes: 1 addition & 1 deletion source/first_steps.rst
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ This document offers an overview of the DATS model from a practical perspective,
The DATS model is centered around the `Dataset <https://github.com/biocaddie/WG3-MetadataSpecifications/blob/master/json-schemas/dataset_schema.json>`_ entity, which supports most of the relevant information about the data being observed.

The main building blocks of the DATS model are defined as "entities", which and for convenience purposes, may be compared to the different "sections" of information in a flat document.
Each entity has a number of properties that are instantiated either as other entities or as direct entries. For the latter, information may may be structured (e.g., integer, date, URI) or unstructured (string, or free text entries).
Each entity has a number of properties that are instantiated either as other entities or as direct entries. For the latter, information may be structured (e.g., integer, date, URI) or unstructured (string, or free text entries).

First and foremost, *Dataset* entity aims to cater for essential provenance information: who, when, what, why, where, and how.
By answering these questions, each dataset source will define its own view on what a dataset is.
Expand Down