-
Notifications
You must be signed in to change notification settings - Fork 44
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
Technology scope update #734
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jspellman
approved these changes
Mar 4, 2024
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.
Looks good as discussed in subgroup
I am personally OK with this change but several members have over the past year questioned whether we should provide a conformance model. This change will commit us to doing so. |
bruce-usab
approved these changes
Mar 5, 2024
Although one technically can have a standard without a conformance model — it is unclear how to conform. Or you can’t clearly say what you need to do to conform.
In such cases I think it becomes more of an Informal Standard — more of an informal guideline or best practices document, lacking the formal structure and rigor of a traditional standard with a clear conformance model.
Gregg
… On Mar 5, 2024, at 5:14 AM, rachaelbradley ***@***.***> wrote:
I am personally OK with this change but several members have over the past year questioned whether we should provide a conformance model. This change will commit us to doing so.
—
Reply to this email directly, view it on GitHub <#734 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACNGDXUGBCJ3FZIZ4IY4KXLYWXAKXAVCNFSM6AAAAABD4GLMCSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZYG42TEOBVGQ>.
You are receiving this because you are subscribed to this thread.
|
github-actions bot
added a commit
that referenced
this pull request
Mar 21, 2024
SHA: 1a10636 Reason: push, by alastc Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
github-actions bot
added a commit
that referenced
this pull request
Mar 21, 2024
SHA: 1a10636 Reason: push, by alastc Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
github-actions bot
added a commit
that referenced
this pull request
Mar 21, 2024
SHA: 1a10636 Reason: push, by alastc Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
github-actions bot
added a commit
that referenced
this pull request
Mar 21, 2024
SHA: 1a10636 Reason: push, by alastc Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #224