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

Cardinality of replacements #95

Closed
aisaac opened this issue Sep 12, 2023 · 2 comments · Fixed by #115
Closed

Cardinality of replacements #95

aisaac opened this issue Sep 12, 2023 · 2 comments · Fixed by #115

Comments

@aisaac
Copy link

aisaac commented Sep 12, 2023

The current spec for Deprecate seems to strongly hint there can be only one entity to replace a deprecated entity. Can't this be several entities? In which case the spec should probably mention that there can be several Create (or Add, cf issue 93) activities next to the Deprecate one.

@zimeon zimeon added the Needs discussion A topics that is possibly in-scope but need discusion to decide on a resolution label Sep 28, 2023
@zimeon
Copy link
Member

zimeon commented Sep 28, 2023

I agree, we should allow the possibility of multiple activities related to a Deprecate

@sfolsom
Copy link
Collaborator

sfolsom commented Oct 3, 2023

It was never our intention to say an entity could only be replaced by one entity, e.g. Splits.

@zimeon zimeon added Editorial and removed Needs discussion A topics that is possibly in-scope but need discusion to decide on a resolution labels Oct 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants