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.

Sign up for GitHub

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

Jump to bottom

API and Model Change Compliance #260

Open
gra-moore opened this issue Nov 3, 2021 · 5 comments
Open

API and Model Change Compliance #260

gra-moore opened this issue Nov 3, 2021 · 5 comments
Labels
next-minor-release The issue is not scheduled for the current release, but planned for a release soon after that.

Comments

@gra-moore
Copy link
Collaborator

There is currently no definition of compliance with regards the API or related to the data model. To improve interoperability and data quality is there some way to describe and add compliance definitions. Ideally, this should be represented as a test suite in code that can test implementations that claim compliance.
@cookeac cookeac reopened this Nov 10, 2021
@cookeac
Copy link
Collaborator

cookeac commented Nov 10, 2021

I think this one was closed by mistake (intended close of 261).

@stale
Copy link

stale bot commented Feb 8, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale-issue Identifies that an issue is stale and will be closed unless reactivated. label Feb 8, 2022
@gra-moore gra-moore removed the stale-issue Identifies that an issue is stale and will be closed unless reactivated. label Feb 9, 2022
@gra-moore
Copy link
Collaborator Author

We should discuss this again.

@stale
Copy link

stale bot commented May 10, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale-issue Identifies that an issue is stale and will be closed unless reactivated. label May 10, 2022
@cookeac cookeac removed the stale-issue Identifies that an issue is stale and will be closed unless reactivated. label May 10, 2022
@stale
Copy link

stale bot commented Aug 8, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale-issue Identifies that an issue is stale and will be closed unless reactivated. label Aug 8, 2022
@cookeac cookeac removed the stale-issue Identifies that an issue is stale and will be closed unless reactivated. label Aug 8, 2022
@cookeac cookeac added the next-minor-release The issue is not scheduled for the current release, but planned for a release soon after that. label Oct 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
next-minor-release The issue is not scheduled for the current release, but planned for a release soon after that.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@gra-moore @cookeac @AndreasSchultzGEA