Publishing Package Artifact Definition
Contents
- 1 Publishing Package - initial layout only
- 1.1 Definition and Purpose
- 1.2 SAIF Matrix Location
- 1.3 Audience
- 1.4 Applicability
- 1.5 Requirements, Relationships and Content
- 1.6 Artifact Technology
- 1.7 Content Constraints
- 1.8 Content Guidelines
- 1.9 Publishing Representation(s)
- 1.10 Publishing Constraints
- 1.11 Tooling Considerations
- 1.12 Development Process Considerations
- 1.13 Governance Process Considerations
- 1.14 Issues
Publishing Package - initial layout only
Alternate considerations:
- Publication Package
- Publishing Grouper
- Publication Grouper
Definition and Purpose
A mechanism by which to define a package that organizes and documents a set of SAIF artifacts for publication. Its purpose is to support balloting and distribution of specifications using SAIF artifacts, and includes a means of documenting the package itself, over and above the documentation inherent in each of the artifacts that it is packaging. The packaging occurs by reference to SAIF artifacts that are stored elsewhere. The package is not a "container."
SAIF Matrix Location
This artifact is "Level-independent" because it is may be used to package artifacts at any level. Row(s)
- Conceptual (CIM)
- Logical (PIM)
- Implementable (PSM)
Column(s)
- Enterprise/Business
- Information
- Computational
- Engineering
- Technical
Audience
Briefly, publication packages may be assembled for any target audience.
Health Care Community Audiences:
- General public
- Health care practitioners
- Health system administrators
- Health care policy makers
Health Care Information Technology (IT) Audiences:
- System designers and architects
- System purchasers
- Programmers/implementers
- System vendor management
Applicability
This artifact provides a convenient way to assemble and document artifacts for publication. Therefore it will be created wherever and whenever a Work Group, project team, or HL7 publishers wish to publish SAIF artifacts for whatever purpose.
- Rationale: Is designed as an aid for publication and will be core vehicle for the HL7 publishing software.
Requirements, Relationships and Content
- Provide a means for uniquely identifying the package to be published.
- Rationale Seems obvious.
- Provide a means to "include", by reference, a specific SAIF artifact, or an identifiable sub-component of that artifact for publication.
- Rationale The purpose is to publish SAIF artifacts and doing it by reference allows multiple such packages to include a given artifact without having to alter the content of the artifact itself. In some cases, it may be useful to, for example, include a single identified "class" from an information model.
- Provide a means for grouping (a sub-package, if you will) artifact references or other groups within the package.
- Rationale Such grouping allows the package to have a hierarchical structure (chapters, sections, etc. in order to facilitate understanding of the content.
- Provide ability to add documentation (with mark-up) that precedes and follows each group and reference in the package, including the package itself.
- Rationale Anticipate the need for "preceding" and "following" text that supplements the information in the components themselves.
- Include contextual data such as copyrights, authorship, responsibility, etc. to support publication.
- Rationale Handle the meta-data for the publication itself.
Relationships and traceability
- Some relationship
- Rationale: Reason for relationship
- Some other relationship
- Rationale: Reason for other relationship
Artifact types that may or must relate to this artifact types:
- Many-related Artifact Type
- Another Many-related Artifact Type
Content
- Content element name - Brief Description
- Another content element name - Brief Description
- Sub-element name - Brief Description
- Another content element name - Brief Description
Artifact Technology
Text here
Rationale
- Some reason
- Some other reason
Alternatives
Some technology
- Some pro or con
- Some other pro or con
Content Constraints
- Some rule
- Rationale: Some reason
- Some other rule
- Rationale: Some other reason
Content Guidelines
- Some rule
- Rationale: Some reason
- Some other rule
- Rationale: Some other reason
Publishing Representation(s)
- Some text
- Rationale: Some rationale
- Some other text
- Rationale: Some other rationale
Publishing Constraints
- Some rule
- Rationale: Some reason
- Some other rule
- Rationale: Some other reason
Tooling Considerations
- Nice-to-have|Required: Some feature
- Rationale: Some rationale
- Nice-to-have|Required: Some other feature
- Rationale: Some other rationale
Development Process Considerations
- Some text
- Rationale: Some rationale
- Some other text
- Rationale: Some other rationale
Governance Process Considerations
- Governance Process name - Some process description
- Rationale: Some rationale
- Another Governance Process name - Process description
- Rationale: Some other rationale
Issues
- Some issue
- Some other issue