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
Copy file name to clipboardExpand all lines: docs/data_models/term_naming_standards.md
+8-9Lines changed: 8 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
## Naming conventions
4
4
### Namespace prefixes
5
-
- Names should be all lowercase (e.g., `nidm`, `cogatlas`)
5
+
- Names should be all lowercase (e.g., `nidm`, `snomed`)
6
6
7
7
### Properties (graph "edges")
8
8
- Names should adhere to camelCase (uses capitalized words except for the first word/letter)
@@ -27,14 +27,13 @@ What this might look like in semantic triples:
27
27
In cases where we reuse a term for a class that comes from an existing controlled vocabulary, and that vocabulary follows a different naming convention (e.g., all lowercase), we should follow the existing naming convention.
<pclass="mt-6 text-lg leading-8 text-gray-300">Reap the benefits of curated vocabularies (e.g., BIDS, SNOMED CT, and the Cognitive Atlas) and linked data, without the implementation expertise.</p>
202
+
<pclass="mt-6 text-lg leading-8 text-gray-300">Reap the benefits of curated vocabularies (e.g., BIDS, SNOMED CT, and NIDM) and linked data, without the implementation expertise.</p>
0 commit comments