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

[RCP-45] Legacy and Deprecated Data Elements #104

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

paulhethmon
Copy link

@paulhethmon paulhethmon commented Oct 1, 2023

Draft RCP-045 for legacy/deprecated fields and lookups.

Link to Spec.

@darnjo darnjo marked this pull request as draft October 1, 2023 20:14
# Table of Contents
- [Summary of Changes](#summary-of-changes)
- [Introduction](#introduction)
- [Section 1: Field](#section-1-field)
Copy link
Member

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.

@darnjo
Copy link
Member

darnjo commented Oct 1, 2023

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.

@darnjo darnjo linked an issue Oct 1, 2023 that may be closed by this pull request
@darnjo darnjo added this to the Approved Discussion Items milestone Oct 1, 2023
@darnjo darnjo added the enhancement New feature or request label Oct 1, 2023
…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**
Copy link
Member

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.

@darnjo darnjo changed the title RCP-045 Legacy/Deprecated Fields and Lookups RCP-45 Legacy/Deprecated Fields and Lookups Jul 1, 2024
@darnjo darnjo changed the title RCP-45 Legacy/Deprecated Fields and Lookups RCP-45 - Legacy and Deprecated Data Elements Jul 1, 2024
@darnjo darnjo changed the title RCP-45 - Legacy and Deprecated Data Elements RCP-45: Legacy and Deprecated Data Elements Jul 1, 2024
@darnjo darnjo changed the title RCP-45: Legacy and Deprecated Data Elements [RCP-45] Legacy and Deprecated Data Elements Jul 3, 2024
@Jad212s
Copy link
Member

Jad212s commented Sep 5, 2024

Should the first word in the definition of the Obsolete lookup value under FieldStatus and LookupStatus lookups say "Obsolete" instead of "Deprecated" in the spec?

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[RCP-45] Legacy and Deprecated Data Elements
3 participants