Click to edit Master text styles
Second level
Third level
Fourth level
Fifth level
Schemas and xml reference documents for Prez Assessment Process:
1.File format identification = FileFormat.xsd contains an enumeration of format names, a complex type for specifying format (name, mimetype, version), and a structure to be used in future for filename extension to mimetype mapping.
2.As basis of input for #3 below, see sdrFormatStatusDefaults.xml, which is a structure for recording the default values used as input to the analysis process (builds in the Quality Policy Matrix = <status correlation> and preferred formats = <preferredFormats>)
3.Format Scoring Matrix = FileFormatStatus.xsd contains the structures used for recording Hannah's format status analysis (scoring factors, format score value, preservation quality, and policy status.
4.PreservationAssessmentFlags.xsd contains the structures used to record the preservation risk "red flags" that are to be searched for in the JHOVE output. 
5.preservationAssessmentFlags.xml: The red flag data used for input can be found in preservationAssessmentFlags.xml
6. SdrDigiprov.xsd contains the structures used to document digital provenance (digiprov) information.  Digiprov info consists of the combined outcomes from format identification, format status analysis, and preservation risk assessment procedures. Has 2 outputs:
1.SdrDigiprov (“root” element) 
digiprov_2.12.xml = output for one file (example of )
2.  sdrDigiprovSummary (“root” element) which contains a summary of digiprov information from the analysis of all files in the collection that was analysed.
DigiprovOut-3.xml is an example of that summary output for a limited selection of test files.
This slide puts the three charts together, displaying the format scores, quality values, and policy ratings associated with the image formats.
I threw in audio formats too, for further demonstration.
<amdSec ID="AMD_2.01.001"> to <amdSec ID="AMD_2.13.70">
A sequence of amdSec elements were be generated for all files in the collection, each one containing both a techMD element (for JHOVE output mdRef) and a digiprovMD element (for a preservation risk output mdRef).
<amdSec ID="AMD_2.">
<techMD ID="TECH_2." CREATED="2004-12-27T07:10:12">
<mdRef ID="JHOVE_2." LOCTYPE="URL" xlink:type="simple" xlink:href="./METADATA/AIHT-CONTENT/CONTRIBUTORS/1199_photos/wtc_web/jhove_2." MDTYPE="OTHER" OTHERMDTYPE="jhove" LABEL="./AIHT-CONTENT/CONTRIBUTORS/1199_photos/wtc_web/WTC1.jpg"/>
<digiprovMD ID="DIGIPROV_2." CREATED="2004-12-27T07:10:12">
<mdRef LOCTYPE="URL" xlink:type="simple" xlink:href="./METADATA/AIHT-CONTENT/CONTRIBUTORS/1199_photos/wtc_web/digiprov_2." MDTYPE="OTHER" OTHERMDTYPE="sdrDigiprov" LABEL="./AIHT-CONTENT/CONTRIBUTORS/1199_photos/wtc_web/WTC1.jpg"/>
Note that xlink:href attributes are used to reference external metadata files and that the LABEL attribute is used to specify the relative path to the file within the collection.
    Our original intention was to also include a mdWrap element within the digiprovMD element that would contain a subset of the information stored in the external digiprov file.  This was not done however, dut to lack of implementation time