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

Referenced Standards follows that standard governance #249

Open
JohnMoehrke opened this issue Feb 9, 2023 · 2 comments
Open

Referenced Standards follows that standard governance #249

JohnMoehrke opened this issue Feb 9, 2023 · 2 comments
Assignees

Comments

@JohnMoehrke
Copy link
Contributor

When pointing at a standard, do we expect that that standard organization governance on patch / errata / CP releases is followed? It might be common knowledge that when we reference a standard, that we do expect that standard governance applies and thus if that standard organization approves what they consider an effective errata, that it is effective within IHE as well. However we found that this was possibly not common knowledge.

Recommendation that General Introduction pages be updated to include language to make this concept understood.

  • Chapter 6 - External Relationships
    • it seems the current second paragraph implies this. Especially the "do not contradict conformance". So this would seem the right paragraph to enhance.
  • Appendix E - Standards Profiling and Documentation Conventions
    • This seems less good of a place to say this, but may be useful to say it here too.
    • The reason this page seems useful for this concept is that this is where we express how we are referencing a select set of standards. So we could explain that references to a standard imply agreement with that standard organization governance on errata.

For example when we refer to a DICOM specification, do we expect that DICOM CPs that are accepted, and by DICOM governance become instantly effective, that that change is automatically expected of our use of that DICOM specification?

Same is true of many standards (including internal to IHE references).

  • IHE calls these Change Proposals
  • IETF calls these errata
  • W3C calls these Errata
  • OASIS-OPEN calls them Errata but I didn't find an obvious policy statement
  • HL7 has errata
  • etc
@JohnMoehrke
Copy link
Contributor Author

parties that might be interested in aiding with this
@IHE/iti-co-chairs @IHE/rad-co-chairs @IHE/dev-co-chairs @IHE/publications @jlamy

@JohnMoehrke JohnMoehrke self-assigned this Feb 9, 2023
@lynnfel
Copy link
Contributor

lynnfel commented Feb 9, 2023

The need to follow the change proposal process in underlying standards seems obvious to me, but your comment that "we found that this was possibly not common knowledge" makes these proposed changes a good idea.

@MaryLJ MaryLJ self-assigned this Jun 30, 2023
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

No branches or pull requests

3 participants