-
Notifications
You must be signed in to change notification settings - Fork 24
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix examples of SSSOM/TSV files. (#362)
The examples provided in the SSSOM/TSV section of the "overview" document are full of errors and would fail the most basic validation by our own tools: - use of `Lexical` instead of `semapv:LexicalMatching` in the `mapping_justification` field (probably a remnant of the time prior to the adoption of the SEMAPV vocabulary); - bogus IRI prefix for the SKOS namespace (missing terminal `#`); - use of a full-length identifier (instead of a CURIE) for `creator_id`. This PR fixes those errors. In addition, it also ensures that the fields are listed in the *recommended order*. It’s not critical but if we take the time to recommend that fields be sorted in a given order, the least we can do is to follow our own advice in our examples. While we are at it, we also add a small note about the requirement for using CURIEs in the SSSOM/TSV format, since that requirement currently does not appear anywhere but is already enforced by `sssom validate`. This is a band-aid until the docs are completely overhauled as part of #330. Co-authored-by: Nico Matentzoglu <nicolas.matentzoglu@gmail.com>
- Loading branch information
Showing
1 changed file
with
27 additions
and
17 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters