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

Minor fix to the “overview” document regarding the TSV format #284

Merged
merged 2 commits into from
Jun 11, 2023
Merged

Minor fix to the “overview” document regarding the TSV format #284

merged 2 commits into from
Jun 11, 2023

Conversation

gouttegd
Copy link
Contributor

Partially addresses [#283]

  • docs/ have been added/updated if necessary
  • make test has been run locally (N/A; documentation change only)
  • tests have been added/updated (N/A; documentation change only)
  • CHANGELOG.md has been updated. (N/A; documentation change only)

This PR fixes point 1. and 2. described in #283 (disallowing the use of curie_map as a link to an external curie map and fixing a discrepancy in the recommended file naming convention for the external metadata file).

Remove the bit in the specification that suggested the `curie_map`
parameter in the YAML metadata of a mapping set could be a link to an
external curie map. `curie_map` should only be used to provide an
embedded curie map. It is unclear whether an external curie map should
be allowed at all, but if it is, it should be specified using a distinct
parameter.
The recommendation is that the external metadata file, when present,
should have the extension `.sssom.yml` (not `-meta.yml`).
@gouttegd gouttegd requested a review from matentzn June 10, 2023 17:31
Copy link
Collaborator

@matentzn matentzn left a comment

Choose a reason for hiding this comment

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

Perfect, thanks!

@matentzn matentzn merged commit 295678f into mapping-commons:master Jun 11, 2023
@gouttegd gouttegd deleted the fix-overview-tsv branch June 11, 2023 13:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants