You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"affiliation": "TIB - Leibniz Information Centre for Science and Technology, Germany"
12
+
},
13
+
{
14
+
"name": "Borgelt, Hendrik",
15
+
"orcid": "0000-0001-5886-7860",
16
+
"affiliation": "TU Dortmund University, Germany"
17
+
},
18
+
{
19
+
"name": "Doerr, Mark",
20
+
"orcid": "0000-0003-3270-6895",
21
+
"affiliation": "University of Greifswald, Germany"
22
+
},
23
+
{
24
+
"name": "Linke, David",
25
+
"orcid": "0000-0002-5898-1820",
26
+
"affiliation": "Leibniz Institute for Catalysis, Albert-Einstein-Str. 29 A, 18059 Rostock, Germany"
27
+
}
28
+
],
29
+
"description": "<p><a href=\"https://nfdi-de.github.io/chem-dcat-ap/\">ChemDCAT-AP</a> is a metadata schema extension for providing chemistry specific metadata for a dataset. It builds upon the domain-agnostic <a href=\"https://nfdi-de.github.io/dcat-ap-plus/\">DCAT-AP-PLUS</a> schema.</p> <p>The metadata schema is developend as <a href=\"https://linkml.io/\">LinkML</a> model which allows to generate various artefacts such as JSON-Schema, SHACL shapes, Python-bindings, and documentation.</p>",
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,9 @@
1
-
# Contributing to dcat-4C-ap
1
+
# Contributing to chem-dcat-ap
2
2
3
3
:+1: First of all: Thank you for taking the time to contribute!
4
4
5
5
The following is a set of guidelines for contributing to
6
-
dcat-4C-ap. These guidelines are not strict rules.
6
+
chem-dcat-ap. These guidelines are not strict rules.
7
7
Use your best judgment, and feel free to propose changes to this document
8
8
in a pull request.
9
9
@@ -22,7 +22,7 @@ in a pull request.
22
22
23
23
## Code of Conduct
24
24
25
-
The dcat-4C-ap team strives to create a
25
+
The chem-dcat-ap team strives to create a
26
26
welcoming environment for editors, users and other contributors.
27
27
Please carefully read our [Code of Conduct](CODE_OF_CONDUCT.md).
28
28
@@ -73,7 +73,7 @@ Please submit a [Pull Request][pulls] to submit a new term for consideration.
73
73
- Never work on the main branch, always work on an issue/feature branch
74
74
- Core developers can work on branches off origin rather than forks
75
75
- Always create a PR on a branch to maximize transparency of what you are doing
76
-
- PRs should be reviewed and merged in a timely fashion by the dcat-4C-ap technical leads
76
+
- PRs should be reviewed and merged in a timely fashion by the chem-dcat-ap technical leads
77
77
- PRs that do not pass GitHub actions should never be merged
78
78
- In the case of git conflicts, the contributor should try and resolve the conflict
79
79
- If a PR fails a GitHub action check, the contributor should try and resolve the issue in a timely fashion
@@ -102,20 +102,20 @@ Core developers should read the material on the [LinkML site](https://linkml.io/
102
102
- Include examples and counter-examples (intentionally invalid examples)
103
103
- Rationale: these serve as documentation and unit tests
104
104
- These will be used by the automated test suite
105
-
- All elements of the nmdc-schema must be illustrated with valid and invalid data examples in src/data. New schema elements will not be merged into the main branch until examples are provided
105
+
- All elements of the schema must be illustrated with valid and invalid data examples in src/data. New schema elements will not be merged into the main branch until examples are provided
106
106
- Invalid example data files should be invalid for one single reason, which should be reflected in the filename. It should be possible to render the invalid example files valid by addressing that single fault.
107
107
- Use enums for categorical values
108
108
- Rationale: Open-ended string ranges encourage multiple values to represent the same entity, like “water”, “H2O” and “HOH”
109
109
- Any slot whose values could be constrained to a finite set should use an Enum
110
110
- Non-categorical values, e.g. descriptive fields like `name` or `description` fall outside of this.
111
111
- Reuse
112
112
- Existing scheme elements should be reused where appropriate, rather than making duplicative elements
113
-
- More specific classes can be created by refinining classes using inheritance (`is_a`)
113
+
- More specific classes can be created by refining classes using inheritance (`is_a`)
[](https://github.com/nfdi-de/chem-dcat-ap/actions/workflows/main.yaml)
0 commit comments