publication layout

• formal publication web -- http://profiles.ihe.net/${domain}
  • index.html at all folder levels assisting with navigating that folder content. Might be based on .xml or folder content?
  • papers/${domain}/${paper}
    • e.g. http://profiles.ihe.net/ITI/papers/index.html -- holds human narrative navigation to all papers
    • e.g. http://profiles.ihe.net/ITI/papers/MetadataHandbook.html
  • publications/${domain}/volume[1-5]/
    • TODO us there a need for a /TF/ folder? Doesn't seem needed
    • e.g. http://profiles.ihe.net/ITI/volume1/ch-9.html -- Profile 9: ATNA
    • e.g. http://profiles.ihe.net/ITI/volume2/ITI-20.html -- Transaction ITI-20 - Record Audit Event
  • publications/${domain}/${supplement}
    • e.g. http://profiles.ihe.net/ITI/MHD/index.html
    • might we have each a redirect from http://profiles.ihe.net/ITI/ATNA to http://profiles.ihe.net/ITI/volume1/ch-9.html
  • e.g. http://profiles.ihe.net/ITI/index.html -- contains all publications from ITI
  • e.g. http://profiles.ihe.net/index.html -- contains all domains with links to their index.html
• common among all domains and publication types (supplement, technical framework, or IG)
  • profiles.xml & profiles.html -- master index of all IHE profiles across all domains (similar to https://wiki.ihe.net/index.php/Profiles)
  • actors.xml & actors.html -- master index of all IHE actors across all domains
  • transactions.xml & transactions.html -- master index of all IHE transactions across all domains pointing to narrative
  • content.xml & content.html -- master index of all IHE content across all domains pointing to narrative
  • vocabulary.html -- equivalent to Appendix C: Namespaces
  • glossary.html -- equivalent to Appendix D: Glossary (not clear if it is an active glossary or uses SKMT Glossary)
  • profiling.html -- equivalent to Appendix E: Profiling
  • statements.html -- equivalent to Appendix F: Integration Statements

Occasionally content gets moved, and it is useful to have a user using the old URL redirected to the new destination. This is also useful with canonical URI to redirect to the html page where that artifact (e.g. a CodeSystem) is published. When a "redirect" is needed, Mary can make that happen.