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

chapter 4.2 is too big, needs to be broken down #30

Closed
JohnMoehrke opened this issue Sep 4, 2020 · 5 comments
Closed

chapter 4.2 is too big, needs to be broken down #30

JohnMoehrke opened this issue Sep 4, 2020 · 5 comments
Assignees
@MaryLJ @JohnMoehrke @vassilpeytchev
Labels
enhancement New feature or request
Milestone
Phase 2: February...

Comments

@JohnMoehrke
Copy link
Contributor

see the breakdown I have made in the wiki page for XDS
https://wiki.ihe.net/index.php/Cross-Enterprise_Document_Sharing#Vol._3

It would create many files, but I think this level of referenceability is needed. Possibly H4 could be done with #
@JohnMoehrke JohnMoehrke self-assigned this Oct 19, 2020
@JohnMoehrke
Copy link
Contributor Author

break out H4 in 4 into standalone html files.
add to contents the H4

@JohnMoehrke JohnMoehrke added this to the Phase 2 milestone Nov 13, 2020
@vassilpeytchev
Copy link
Contributor

I disagree that 4.2 needs to be broken down. I suggest we leave it as is.

@JohnMoehrke JohnMoehrke removed this from the Phase 2: February 2021 milestone Feb 8, 2021
@JohnMoehrke
Copy link
Contributor Author

@vassilpeytchev is considering a different way to make the content more accessible. This may result in a new issue covering the new model, and this item might be canceled.

@JohnMoehrke JohnMoehrke added this to the Phase 2: February 2021 milestone Feb 8, 2021
@JohnMoehrke JohnMoehrke added the enhancement New feature or request label Feb 8, 2021
@JohnMoehrke
Copy link
Contributor Author

look at #29

@JohnMoehrke
Copy link
Contributor Author

need to assess if update by Vassil is sufficient for now. If so, what is the left over that might be future issues to solve?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@MaryLJ MaryLJ

@JohnMoehrke JohnMoehrke

@vassilpeytchev vassilpeytchev

Labels
enhancement New feature or request
Projects
None yet
Milestone
Phase 2: February 2021
Development

No branches or pull requests
3 participants
@MaryLJ @JohnMoehrke @vassilpeytchev