-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
22.01 #97
22.01 #97
Conversation
On branch 22.01 Changes to be committed: modified: README.md deleted: VERSION.py modified: config.toml modified: content/bco-domains.md renamed: content/extension-scm.md -> content/extension-domain.md deleted: content/extension-fhir.md modified: content/provenance-domain.md modified: content/usability-domain.md modified: content/user_guide.md
Changes to be committed: modified: content/description-domain.md modified: content/execution-domain.md modified: content/parametric-domain.md
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a summary of changes since the last version?
Added language about object_id versioning and prefix Changes to be committed: modified: content/provenance-domain.md modified: content/top-level.md
Changes to be committed: modified: content/examples/HCV1a.json modified: content/examples/HIVE_metagenomics.json modified: content/examples/UVP.json modified: content/examples/glycosylation-sites-UniCarbKB.json modified: content/top-level.md
Changes to be committed: modified: content/faq.md modified: content/sop.md
response to Issue #72 Changes to be committed: modified: content/faq.md
#97 (review) Changes to be committed: modified: content/faq.md modified: content/provenance-domain.md modified: content/top-level.md
What's Changed
Full Changelog: 1.4.2...22.01 |
@mr-c Its a lot since we stoped tracking versions once we realized that IEEE-2791-2020 would be the repo for the standard. This repo has been repurposed to house the documentation, and so this PR will be the first release to be inline with the BCO Portal and DB release. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor changes made.
I know that this came up before, but why is the external references field only for publicly accessible data, forcing non-public data to find a home somewhere else?
@kee007ney where do you see that? Actually the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Made minor changes to text.
No description provided.