niem-manifest.xml

Purpose: To allow automated and (via code generation) human navigation of the NIEM IEPD package. Also provides version info, dependencies, descriptions of each artifact, path name,name of the specification, name of the file,created date, update date, checksum,

(will be removed as this format collesces into the selected format):
 * Discussion**:

Is there an existing standard for a computable manifest?? Several have been identified below in the annotated references section.

Need to talk to Kevin P/ONC to see what tooling they have. It has been suggested that we publish the requirements. The tooling team has been given requirements already, to a limited extent, on the packaging requirements. Bob Y will see if we can get this list of consolidated requirements, probably on the Thursday call.

Java manifest spec? .net manifest? Provide these as potentials for Kevin and others to consider.

Virtual package concept: where one package depends on others packages only. And contains no other artifacts directly. Fixed and floating references (from one package to another).

Sample:

 > >> >>> text >>> text >>> text >>> other-file-paths(internal or external) >>> text >>> text >>> other-file-paths(internal or external) >>> author >>> 123545 >>> object-taxonomy:\Specifications\Patient-Discovery\2.00.00, audience-taxonomy:\Implementers\Specification\, audience-taxonomy:\Testers\Specification\ >>> >> >  

From Dublin Core (possible attributes):

1. Title 2. Creator 3. Subject 4. Description 5. Publisher 6. Contributor 7. Date 8. Type 9. Format 10. Identifier 11. Source 12. Language 13. Relation 14. Coverage 15. Rights


 * Annotated References:**

Some Microsoft manifest file formats: [|http://msdn.microsoft.com/en-us/library/aa375632(VS.85).aspx]

Microsoft ClickOnce Deployment manifest format (is similar in many ways to the format we've been independently developing): []

Debian packaging format: []

Eric Heflin (so far! help solicited)
 * Page authors:**