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

Draft IS-13-like mechanism to update distinguishing info of Inputs and Outputs #130

Draft
wants to merge 2 commits into
base: v1.0.x
Choose a base branch
from

Conversation

garethsb
Copy link
Contributor

For discussion!
Would resolve #126

@garethsb
Copy link
Contributor Author

An alternative now that IS-13 Annotation API has introduced a /node/ base path for the Node API-related resources, would be to add a /streamcompatibility/ base path to that API, with inputs/ and /outputs under it.

@alabou
Copy link
Collaborator

alabou commented May 29, 2023

Why an IS-13 feature is implemented in the IS-11 API?

@garethsb
Copy link
Contributor Author

Can the Stream Compatibility Management activity group first evaluate the feature, whether there are user stories for assigning user annotations to IS-11 inputs and outputs? Then e can decide where it belongs.

@peterbrightwell
Copy link
Contributor

If we're going to start reusing examples perhaps have better text than "that one" and "over there" :)

Base automatically changed from publish-preliminary to v1.0-dev July 24, 2023 10:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants