This area can be used to store a single document that represents the result of the calibration in a human-readable form. For example, a version of the calibration certificate saved in PDF-A format can be stored in the previous appearance of the analogue calibration certificate that was previously issued in paper format to the client after the calibration service provider fulfilled the calibration order. The users of the DCC and also the authorised persons in the field of quality management thus have the possibility to see an image of the analogue calibration certificate they were used to seeing during the phase of conversion to a digital representation of calibration certificates. By using Base64 encoding, the PDF-A document can be stored together with the above-mentioned information in the XML file.
The authors of the DCC assume that HTML5 will establish itself as a human-readable format over time. An output of the calibration certificate based on browser technologies has the advantage that it is format-free. The output of larger tables is then easily possible and more efficient for the user.
For example, units outside the SI system of units can additionally be displayed (e.g. nautical miles, millimetres of mercury, degrees Oechsle), provided that this facilitates and improves the readability of the calibration certificate by the user. The non-SI units should only be used in the human readable part. Here they are useful because in this way non-metrologists can find "their familiar units" again. For communication between machines, the use of SI units is indispensable in order to exclude confusion from the outset. The conversion of SI units and non-SI units should be reserved for the metrologists at the calibration service provider, who guarantee the correctness of the conversion.
The tree structure of the element dcc:document has the following appearance:
<xs:complexType name="byteDataType"> <xs:annotation> <xs:documentation> The byteDataType defines a type which allows to add binary encoded files to the measurement result section. </xs:documentation> </xs:annotation> <xs:sequence> <xs:element name="name" type="dcc:textType" minOccurs="0"/> <xs:element name="description" type="dcc:richContentType" minOccurs="0"/> <xs:element name="fileName" type="dcc:notEmptyStringType"/> <xs:element name="mimeType" type="dcc:notEmptyStringType"/> <xs:element name="dataBase64" type="xs:base64Binary"/> </xs:sequence> <xs:attribute name="id" type="xs:ID" use="optional"/> <xs:attribute name="refId" type="xs:IDREFS" use="optional"/> <xs:attribute name="refType" type="dcc:refTypesType" use="optional"/> </xs:complexType>
<dcc:document> <dcc:fileName>GEMIMEG-Tool_gp_temp.pdf</dcc:fileName> <dcc:mimeType>application/pdf</dcc:mimeType> <dcc:dataBase64>VeryLongBase64String...==</dcc:dataBase64> </dcc:document>