-
Notifications
You must be signed in to change notification settings - Fork 6
Create release page for CASE 0.2.1 #162
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
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
f00b1f3
Create release page for CASE 0.2.1
plbt5 c5c20bf
Revert submodule pointer reversion
ajnelson-nist b354483
Update releases.yml
plbt5 dfa0107
Update index.md
plbt5 f6bdc6f
Adjust release description
ajnelson-nist 6d7fd7d
Adjust scope of data modification
ajnelson-nist File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,52 @@ | ||
--- | ||
title: 0.2.1 Release | ||
layout: releases | ||
custom_css: releases | ||
--- | ||
|
||
# {{ page.title }} | ||
|
||
*Date: TBD* | ||
|
||
## Ontology File(s) | ||
|
||
[GitHub](https://github.com/casework/CASE/releases/tag/0.2.1) | ||
|
||
## Migration guidance | ||
|
||
In terms of CASE-namespaced concepts, release 0.2.1 is a patch to 0.2.0. Migration from CASE 0.2.0 does not require alterations to existing data, except that ontology prefixes will now encode the ontology version in the concept IRI. | ||
|
||
## Release Notes | ||
|
||
### Focus | ||
|
||
The focus of this patch is on IRI's: | ||
* slash based as opposed to #-based IRI's | ||
|
||
|
||
### Changes | ||
|
||
*(These are changes to ontologies, classes or properties in the preexisting ontology.)* | ||
|
||
Throughout this section, many of the notes are tied to Change Proposals. These proposals are available on CASE's [Reference Material page](/resources/references.html). | ||
|
||
#### Development Changes | ||
|
||
*(These are changes to ontology development practice, and are not necessarily changes to ontology data.)* | ||
|
||
* None | ||
|
||
#### Breaking Changes | ||
|
||
*(These are changes to ontologies, classes or properties in the preexisting ontology that make the new release non-backward-compatible.)* | ||
|
||
* None | ||
|
||
|
||
#### Changes | ||
|
||
*(These are general changes to the preexisting ontology that are not breaking or range changes.)* | ||
|
||
* rdf-toolkit base-iri flag degenerates versionIRI when slash IRI form is used | ||
*([Change Proposal 38](https://drive.google.com/file/d/1T7ZmDZuslKAGc2HA3PPYhSmKqDDoqfkt/view))* | ||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.