Skip to content
Closed
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: 2 additions & 0 deletions src/docs/spec.md
Original file line number Diff line number Diff line change
Expand Up @@ -362,6 +362,8 @@ This precludes spurious diffs in a git setting, which is an important concern fo

Note that only metadata elements permissible in a global context (G, or L/G) can be used in the metadata-file.

**Entity references**: All identifiers in a SSSOM/TSV file (both in the metadata section and in the TSV columns) MUST be in CURIE form. The use of full-length identifiers is officially not supported.
Copy link
Contributor Author

@joeflack4 joeflack4 Apr 18, 2024

Choose a reason for hiding this comment

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

The change

@gouttegd I copied pretty much ver batim what you suggested here. Seemed good enough.

Copy link
Contributor

Choose a reason for hiding this comment

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

I’ve already put that change in my #362 PR. It just need to be approved and merged.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

That is good to hear, thanks! I'll close this, tehn.


We recommend to use the following *filename conventions* for SSSOM metadatafiles:

- TSV files should have the extension `.sssom.tsv`, for example: `mp-hp-exact-0.0.1.sssom.tsv`.
Expand Down