-
Notifications
You must be signed in to change notification settings - Fork 15
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
[RCP-45] Legacy and Deprecated Data Elements #104
base: main
Are you sure you want to change the base?
[RCP-45] Legacy and Deprecated Data Elements #104
Conversation
# Table of Contents | ||
- [Summary of Changes](#summary-of-changes) | ||
- [Introduction](#introduction) | ||
- [Section 1: Field](#section-1-field) |
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.
One note here, usually Section 2 is for the spec, and 3 for Certification.
So your sections should be 2.1, 2.2, etc.
Looks good so far. Thanks for posting this. I added it to the Oct 2023 Transport agenda and converted it to a Draft PR for now. |
…y-and-deprecated-data-elements.md Updated and generalized content, added Model Resource, and updated examples.
|
||
The following fields are proposed as additions: | ||
|
||
- **FieldStatus**: closed enumeration with allowed values: **Obsolete**, **Deprecated**, **Active**, **Transition** |
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.
Note: there is a pending question as to whether we use something more general here, like ElementStatus, rather than Model/Field/LookupStatus.
Draft RCP-045 for legacy/deprecated fields and lookups.
Link to Spec.