This wiki has undergone a migration to Confluence found Here
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
NOTES:
package -
- packageLocation@root values
- "DEFN" The package represents the artifacts being defined.
- "BAL" The package groups a set of content defined elsewhere intended to be submitted for ballot
- QUESTION:[why "elsewhere" why could not a ballot package have DEFN elements within a DEFN package that is part of its content??]
- "PUB" The package a set of content defined elsewhere as a formal publication
- QUESTION:[why "elsewhere" why could not a publication package (like a Normative Edition) have DEFN elements within one or more DEFN package(s) that is(are) part of its content??]
- "DEFN" The package represents the artifacts being defined.
- contents:
- freehand, DAM, domainInstanceExample, SB, DT model, IFC, vocModel, staticModel (SM) (serialized or flat), serialized (SM), derived (SM), strucDoc, TE, INT, AR, interactionProfile, conformanceProfile, testScenario, publication, package
QUESTION:Why is mif:publication/mif:packageLocation/@root not limited to "PUB" only?
MIF ballot:
- says realmNamespace is "Mandatory",
- OBSERVATION: but it is optional in the schemas (at least in mif:package/packageLocation)
- also says that packageLocation/@artifact - "Identifies the type of artifact represented. Applies to all "Definition" artifacts. The set of artifacts is controlled by HL7's Publishing work group in consultation with Modeling & Methodology and Tooling."
- OBSERVATION: Clearly, it does not apply to the DEFN file for CorePrinciples, because it is not a "DC" and therefore its package location is (I believe):
- <mif:packageLocation root="DEFN" realmNamespace="UV" name="v3modelcoreprinciples"/>
- OBSERVATION: Clearly, it does not apply to the DEFN file for CorePrinciples, because it is not a "DC" and therefore its package location is (I believe):
- says realmNamespace is "Mandatory",
SAIF Matrix Location
Row(s)
- Conceptual (CIM)
- Logical (PIM)
- Implementable (PSM)
Column(s)
- Enterprise/Business
- Information
- Computational
- Engineering
- Technical
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
Text
Rationale: More text
Requirements, Relationships and Content
- Some requirement
- RationaleSome reason
- Some other requirement
- RationaleSome other reason
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