I need to provide information about the quality of my data and how it was measured.

<gmd:dataQualityInfoDQ_DataQuality xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.isotc11isotc211.org/2005/gmd http://www.isotc211.org/2005/gmd/gmd.xsd 
	xsd http://www.isotc211.org/2005/gmi http://www.isotc211.org/2005/gmi/gmi.xsd"
    xmlns:gmi="http://www.isotc211.org/2005/gmi" xmlns:gco="http://www.isotc211.org/2005/gco"
    xmlns:gmd="http://www.isotc211.org/2005/gmd" xmlns:xlink="http://www.w3.org/1999/xlink"
    xmlns:srv="http://www.isotc211.org/2005/srv" xmlns:gml="http://www.opengis.net/gml/3.2">
    <gmd:DQ_DataQuality>
        <gmd:scope>
            <!--
        The DQ_Scope object can include an id attribute that allows the same quality scope to be referenced from several different sections of the metadata record. 
        For example, if all of the quality reports in the record pertain to the entire granule, they could all reference the same scope object with a value of "dataset".
        In this case, the id is set to datasetScope.
        -->
            <gmd:DQ_Scope id="datasetScope">
                <gmd:level>
                    <!--
                The MD_ScopeCode is a codelist that includes two standard attributes: a URL that gives the location of the codeList,
                and a value from the codelist. The location can be set to the standard location if the standard codelist is sufficient
                for the data provider needs or, if necessary, it can be set to a codelist that has been extended to include dataset
                specific values.
                -->
                    <gmd:MD_ScopeCode codeList="http:CodeListLocation//#MD_ScopeCode" codeListValue="dataset">dataset</gmd:MD_ScopeCode>
                </gmd:level>
                <!--
            The extent of the quality report can include specific information, if appropriate, or it can reference an extent defined
            in another part of the metadata record. In this case, the extent of the quality report is the same as that of the dataset,
            so the identifier boundingExtent is used. If necessary, the qualityReport can contain more than one extent. See extent examples.
            -->
                <gmd:extent xlink:href="#boundingExtent"/>
                <gmd:levelDescription>
                    <!--
                The levelDescription is used to provide more detail about the scope of the quality report. It can include name(s) of
                attributes or features or a text description of the scope. The properties also include dataset and other which are
                both character strings. If necessary, the quality report can contain more than one levelDescription.
                -->
                    <gmd:MD_ScopeDescription>
                        <gmd:dataset>
                            <gco:CharacterString>levelDescription</gco:CharacterString>
                        </gmd:dataset>
                    </gmd:MD_ScopeDescription>
                </gmd:levelDescription>
            </gmd:DQ_Scope>
        </gmd:scope>
        <gmd:report>
            <!--
        The report holds the meat of the DQ_DataQuality section of the metadata. It includes four major sections: the measure,
        the method, the date, and the result. There are a number of different types of reports that reflect general areas of
        data quality, e.g. DQ_Completeness, DQ_LogicalConsistency, DQ_PositionalAccuracy, DQ_ThematicAccuracy, DQ_TemporalAccuracy,
        DQ_QuantitativeAttributeAccuracy, and DQ_Usability. These are very general descriptors that should be used if clearly
        appropriate. At the same time, some of these names were created with collections of geographic features in mind and so
        may not make sense in the context of other data types. In those cases, the very general type DQ_QuantitativeAttributeAccuracy
        serves as a generally applicable catch-all.        
        -->
            <gmd:DQ_QuantitativeAttributeAccuracy>
                <!-- 
            Information about the quality measure: To facilitate data set comparisons, it is helpful if the results in the data quality
            reports are expressed in a comparable way and that there is a common understanding of the data quality measures that have
            been used. ISO 19157 provides a set of standard measures to facilitate comparisons, but these are very general, e.g. 
            "number of missing items" or "relative horizontal error". The standard also describes how user defined quality
            measures can be cataloged for sharing across a community.
               
         
   ISO   19115 quality reports include three elements thatA arenumber usedof totypes describeof thedata quality measurereports are available. The nameOfMeasure DQ_QuantitativeAttributeAccuracy is the most general and
            measureDescriptionmost are usedbroadly applicable of these.
            
            ISO 19115 quality reports include three elements that are used to describe the quality measure. The nameOfMeasure and
            measureDescription are used to provide enough information for a user to understand the measure being used if they are
            familiar with the measures used in a community. The measureIdentifier is used to support a search for more information.
            
            -->
                
            <!--
            ESDIS Data Quality Information: 
            
            The ECHO metadata model includes several kinds of quality information: QAStats and QAFlags.
            These measures have standard names. The QAStats are QAPercentMissingData, QAPercentOutOfBoundsData, QAPercentInterpolatedData,
            QAPercentCloudCover and the QAFlags are AutomaticQualityFlag, OperationalQualityFlag, ScienceQualityFlag. In the ISO
            implementation these are measure names.
            
            Currently the measure names serve as globally unique identifiers for the ESDIS quality measures so nameOfMeasure = identifier.
            
            The QAStats have self-explanatory names so they do not require a description. The QAFlags are more general and have mission or
            product specific explanations. In ECHO these are called AutomaticQualityFlagExplanation, OperationalQualityFlagExplanation,
            ScienceQualityFlagExplanation. In the ISO implementation, these explanations are measureDescriptions.
            
            Other quality information:
            
            Many ESDIS products include quality indicators that are specific to a particular product and not in the general ECHO
            model. In some cases this quality information is in product specific attributes (or additional attributes)
            with names that include "PERCENT" or start with "QA", e.g. PERCENTSHAPEFIXEDBRDFS, PERCENTLOWSUN, 
            QAPERCENTPOOROUTPUT250MBAND1, QAPERCENTPOOROUTPUT250MBAND2. In the ISO implementation these are measure names. 
            
            In some cases these names are self-explanatory, but in many cases, more detailed description of how they are
            calculated would benefit users. Those descriptions could be measure descriptions or references to how they
            were calculated could be provided as evaluation procedure citations.
            -->
                <gmd:nameOfMeasure>
                    <gco:CharacterString>nameOfMeasure</gco:CharacterString>
                </gmd:nameOfMeasure>
                <gmd:measureIdentification>
                    <gmd:MD_Identifier>
                        <gmd:code>
                            <gco:CharacterString>measureIdentifier</gco:CharacterString>
                        </gmd:code>
                    </gmd:MD_Identifier>
                </gmd:measureIdentification>
                <gmd:measureDescription>
                    <gco:CharacterString>measureDescription</gco:CharacterString>
                </gmd:measureDescription>
                <!--
                The evaluation method provides a description of how the measure was used in the context of a particular dataset
                in order to generate the quality report. ISO 19115 includes three elements that are relevant to the evaluationMethod:
                the type is a codelist with values of directInternal, directExternal, or indirect; the evaluationMethodDescription
                is a text description that is available to a user along with the metadata record; the evaluationProceedure provides
                a citation to more detailed information.
            -->
                <gmd:evaluationMethodType>
                    <gmd:DQ_EvaluationMethodTypeCode codeList="URI to codelist location" codeListValue="direct_external">direct_external</gmd:DQ_EvaluationMethodTypeCode>
                </gmd:evaluationMethodType>
                <gmd:evaluationMethodDescription>
                    <gco:CharacterString>evaluationMethodDescription</gco:CharacterString>
                </gmd:evaluationMethodDescription>
                <gmd:evaluationProcedure>
                    <gmd:CI_Citation>
                        <gmd:title>
                            <gco:CharacterString>title of reference material</gco:CharacterString>
                        </gmd:title>
                        <gmd:date gco:nilReason="missing"/>
                    </gmd:CI_Citation>
                </gmd:evaluationProcedure>
                <!--
                The dateTime gives the date and time of the quality test in ISO8601 compliant text format
            -->
                <gmd:dateTime>
                    <gco:DateTime>2012-10-02T15:44:00</gco:DateTime>
                </gmd:dateTime>
                <!--
                The result is the actual result of the quality test. There are four types of results: DQ_QuantitativeResult,
                DQ_ConformanceResult, QE_CoverageResult (from ISO 19115-2), and DQ_DescriptiveResult (from ISO 19157). A single
                report can contain one or two results.
            -->
                <gmd:result>
                    <gmd:DQ_QuantitativeResult>
                        <!-- 
                            gmd:DQ_QuantitativeResult:
                            
                            Results of many quality reports are single simple numbers (%'s or counts). In those cases a
                            DQ_QuantitativeResult can be used to hold the result.
                            
                            Unit definitions generally come from an accepted source that can be referenced for an authoritative 
                            definition. In Earth Science the UDUNITS package is commonly used (http://www.unidata.ucar.edu/software/udunits/). 
                            A more general source for unit definitions is "The Unified Code for Units of Measure" (http://unitsofmeasure.org).
                            See https://coastwatch.pfeg.noaa.gov/erddap/convert/units.html for a comparison of the two approaches.
                            
                            The xlink included in the valueUnit is designed to provide an unambiguous identifier for the definition of the
                            unit. Neither UCUM not UDUNITS support such URIs. UCUM does have a table of unit abbreviations and definitions
                            at http://unitsofmeasure.org/ucum.html#section-Alphabetic-Index. These can be referenced as
                            degrees Celsius = xlink:href="http://unitsofmeasure.org/ucum.html#Cel"                           
                        -->
                        <gmd:valueUnit xlink:href="AnyValidURI"/>
                        <gmd:value>
                            <!--
                                A Record is a string of value(s) with a given type. In most quantitative quality reports the type is a simple
                                primative type (gco:Real_PropertyType, gco:Integer_PropertyType). In other cases, it could be a string
                                (gco:CharacterString_PropertyType) that includes multiple numbers.                               
                            -->
                            <gco:Record xsi:type="gco:Integer_PropertyType">
                                <gco:Integer>999</gco:Integer>
                            </gco:Record>
                        </gmd:value>
                    </gmd:DQ_QuantitativeResult>
                </gmd:result>
                <gmd:result>
                    <gmi:QE_CoverageResult>
                        <!--
                            gmi:QE_CoverageResult:
                            
                            The gmi:QE_CoverageResult is used to provide a quality report that is in the form of a coverage (e.g. a
                            timeseries or grid). It therefore shares a number of elements with coverage descriptions. In cases where
                            these elements are repeated in a single metadata record, these can be references to elements that are
                            completely described elsewhere in the record (e.g. xlink:href="#datasetspatialRepresentation").
                            
                            The resultFile and resultFormat can be used to describe a coverage result that is in a different file.
                        -->
                        <gmi:spatialRepresentationType/>
                        <gmi:resultSpatialRepresentation/>
                        <gmi:resultContentDescription/>
                        <gmi:resultFormat/>
                        <gmi:resultFile/>
                    </gmi:QE_CoverageResult>
                </gmd:result>
                <gmd:result>
                    <gmd:DQ_ConformanceResult>
                        <<!--
                            gmd:DQ_ConformanceResult:
                            
                            The gmd:DQ_ConformanceResult is used to provide a quality report on conformance of a dataset to a
                            particular standard, e.g. an OGC Web Service or OPeNDAP.
                            
                            The result in this case is a Boolean, i.e. True or False.
                        -->
                        <gmd:specification/>
                        <gmd:explanation/>
                        <gmd:pass/>
                    </gmd:DQ_ConformanceResult>
                </gmd:result>
            </gmd:DQ_QuantitativeAttributeAccuracy>
        </gmd:report>
    </gmd:DQ_DataQuality>
</gmd:dataQualityInfo>

<mdb<mdq:dataQualityInfoDQ_DataQuality xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
   xmlns:mdbxsi:schemaLocation="http://standards.iso.org/iso/19115/-3/mdb/1.0"  http://standards.iso.org/iso/19115/-3/mdt/1.0/mdt.xsd"
   xmlns:citmdq="http://standards.iso.org/iso/1911519157/-32/citmdq/1.0" 
   xmlns:mccmdb="http://standards.iso.org/iso/19115/-3/mccmdb/1.0" 
   xmlns:mdqgco="http://standards.iso.org/iso/1915719115/-23/mdqgco/1.0"
   xmlns:gcomcc="http://standards.iso.org/iso/19115/-3/gcomcc/1.0" 
   xmlns:xlink="http://www.w3.org/1999/xlink">
   <mdq:DQ_DataQuality>
       xmlns:cit="http://standards.iso.org/iso/19115/-3/cit/1.0">
   <mdq:scope>
         <!--
        The DQ_Scope object can include an id attribute that allows the same quality scope to be referenced from several different sections of the metadata record. 
        For example, if all of the quality reports in the record pertain to the entire granule, they could all reference the same scope object with a value of "dataset".
        In this case, the id is set to datasetScope.
        -->
         <mcc:MD_Scope>
            <mcc<mcc:level>
               <!--
                The MD_ScopeCode is a codelist that includes two standard attributes: a URL that gives the location of the codeList,
                and a value from the codelist. The location can be set to the standard location if the standard codelist is sufficient
                for the data provider needs or, if necessary, it can be set to a codelist that has been extended to include dataset
                specific values.
                -->
               <mcc:MD_ScopeCode codeList="http:CodeListLocation//#MD_ScopeCode" codeListValue="dataset">dataset</mcc:MD_ScopeCode>
            </mcc:level>
            <!--
            The extent of the quality report can include specific information, if appropriate, or it can reference an extent defined
            in another part of the metadata record. In this case, the extent of the quality report is the same as that of the dataset,
            so the identifier boundingExtent is used. If necessary, the qualityReport can contain more than one extent. See extent examples.
            -->
            <mcc:extent xlink:href="#boundingExtent"/>
            <mcc:levelDescription>
               <!--
                The levelDescription is used to provide more detail about the scope of the quality report. It can include name(s) of
                attributes or features or a text description of the scope. The properties also include dataset and other which are
                both character strings. If necessary, the quality report can contain more than one levelDescription.
                -->
               <mcc:MD_ScopeDescription>
                  <mcc:dataset>
                     <gco:CharacterString>levelDescription</gco:CharacterString>
                  </mcc:dataset>
               </mcc:MD_ScopeDescription>
            </mcc:levelDescription>
         </mcc:MD_Scope>
      </mdq:scope>
   <mdq:standaloneQualityReport>
      <mdq:report>DQ_StandaloneQualityReportInformation>
         <!--
        The report holds the meat of the DQ_DataQuality section og the metadata. It includes four major sections: the measure,
        the method, the date, and the result. There are a number of different types of    DQ_StandaloneQualityReportInformation
            Many important data quality reports are described in scientific papers or reports that can be referenced as 
            standalone quality reports that reflectinclude generalcitations areasto of
the report and an abstract that provides a databrief
 quality, e.g. DQ_Completeness, DQ_LogicalConsistency, DQ_PositionalAccuracy, DQ_ThematicAccuracy, DQ_TemporalAccuracy,
     description of  DQ_QuantitativeAttributeAccuracy, and DQ_Usabilitythe result. TheseThis areis verya generalnew descriptorscapability thatintroduced shouldin beISO used19157. ifThe clearly
report includes a citation
     appropriate. At the same time, some of these names were created with collections of geographic features in mind and so
 -->
         <mdq:reportReference>
            may not make sense in the context of other data types. In those cases, the very general type DQ_QuantitativeAttributeAccuracy<cit:CI_Citation/>
         </mdq:reportReference>
         <mdq:abstract>
        serves as a generally applicable catch-all. <gco:CharacterString/>
         </mdq:abstract>
        --></mdq:DQ_StandaloneQualityReportInformation>
   </mdq:standaloneQualityReport>
      <mdq:DQ_QuantitativeAttributeAccuracy>report>
            <!-- 
        The report holds the Informationmeat aboutof the quality measure: To facilitate data set comparisons, it is helpful if the results in the data quality
DQ_DataQuality section og the metadata. It includes four major sections: the measure,
        the method, the date, and the result. There reports are expressed in a comparablenumber wayof and that there is a common understanding of the data quality measures that havedifferent types of reports that reflect general areas of
        data quality, e.g.  been used. ISO 19157 provides a set of standard measures to facilitate comparisons, but theseDQ_Completeness, DQ_LogicalConsistency, DQ_PositionalAccuracy, DQ_ThematicAccuracy, DQ_TemporalAccuracy,
        DQ_QuantitativeAttributeAccuracy, and DQ_Usability. These are very general, e.g.  descriptors that should be used if clearly
        appropriate. At the same time, "numbersome of missingthese items"names orwere "relativecreated horizontalwith error".collections Theof standardgeographic alsofeatures describesin howmind userand defined qualityso
        may not make sense measuresin canthe becontext catalogedof forother sharingdata acrosstypes. aIn community.
those cases, the very general type DQ_QuantitativeAttributeAccuracy
      
  serves as a generally applicable catch-all.     ISO 19157 quality reports
 include elements that are used to describe the-->
 quality measure in a new <mdq:DQ_MeasureReference Class.QuantitativeAttributeAccuracy>
         <!-- 
  The nameOfMeasure and measureDescription are used to provide enough information forInformation aabout user to understand thethe quality measure: 
To facilitate data set comparisons, it is helpful if the results in beingthe useddata ifquality
 they are familiar with the measures used in a community. The measureIdentifier isreports usedare toexpressed supportin a search
comparable way and that there is a common understanding of the data forquality moremeasures information.that have
           
 been used. ISO 19157 provides a set of standard measures to  -->
       facilitate comparisons, but these are very general, e.g. 
     <mdq:measure>
       "number of missing items" or "relative horizontal  <mdq:DQ_MeasureReference>
       error". The standard also describes how user defined quality
           <mdq:measureIdentification>
 measures can be cataloged for sharing across a community.
            <mcc:MD_Identifier>
            A number of types of data quality reports are available. The  <mcc:code>
    DQ_QuantitativeAttributeAccuracy is the most general and
            most broadly applicable of these.
       <gco:CharacterString>measureIdentifier</gco:CharacterString>
     
            ISO 19115 quality reports include three  </mcc:code>
          elements that are used to describe the quality measure. The nameOfMeasure and
           </mcc:MD_Identifier>
                  </mdq:measureIdentification>
 measureDescription are used to provide enough information for a user to understand the measure being used if they are
            familiar with the measures used in a community. The <mdq:nameOfMeasure>
measureIdentifier is used to support a search for more information.            <gco:CharacterString>nameOfMeasure</gco:CharacterString>
            -->

      </mdq:nameOfMeasure>
   <!--
            ESDIS Data Quality <mdqInformation:measureDescription> 
            
         <gco:CharacterString>measureDescription</gco:CharacterString>
   The ECHO metadata model includes several kinds of quality information: QAStats     </mdq:measureDescription>and QAFlags.
            These measures have  </mdq:DQ_MeasureReference>
      standard names. The QAStats are QAPercentMissingData, QAPercentOutOfBoundsData, QAPercentInterpolatedData,
      </mdq:measure>
      QAPercentCloudCover and the QAFlags are  <!--
    AutomaticQualityFlag, OperationalQualityFlag, ScienceQualityFlag. In the ISO
            Theimplementation evaluationthese methodare providesmeasure anames.
 description of how the measure was used in the context of a
 particular dataset
          Currently the measure names serve as inglobally orderunique toidentifiers generatefor the ESDIS quality report.measures ISOso 19157nameOfMeasure includes= aidentifier.
 new DQ_DataEvaluation class that   includes three elements that are relevant
 to the evaluationMethod:
         The QAStats have self-explanatory names so they thedo typenot isrequire a codelistdescription. withThe valuesQAFlags ofare directInternal,more directExternal,general orand indirect;have themission evaluationMethodDescriptionor
            product specific explanations. In isECHO athese textare descriptioncalled that is available to a user along with the metadata record; the evaluationProceedure providesAutomaticQualityFlagExplanation, OperationalQualityFlagExplanation,
            ScienceQualityFlagExplanation. In the ISO aimplementation, citationthese toexplanations moreare detailed informationmeasureDescriptions.
            -->
            <mdqOther quality information:evaluationMethod>
            
   <mdq:DQ_FullInspection>
         Many ESDIS products include quality indicators that are specific <!--
to a particular product and not in the general ECHO
            model. In some Thecases dateTimethis givesquality theinformation dateis andin timeproduct ofspecific theattributes quality(or testadditional inattributes)
 ISO1601 compliant text format
        with names that include "PERCENT" or start with "QA", e.g. PERCENTSHAPEFIXEDBRDFS,  PERCENTLOWSUN, -->
            QAPERCENTPOOROUTPUT250MBAND1, QAPERCENTPOOROUTPUT250MBAND2. In the ISO implementation <mdq:dateTime>
these are measure names. 
            
     <gco:DateTime>2012-10-02T15:44:00</gco:DateTime>
       In some cases these names are self-explanatory, but in many  </mdq:dateTime>
      cases, more detailed description of how they are
            <mdq:evaluationMethodDescription>
calculated would benefit users. Those descriptions could be measure descriptions or references to how they
       <gco:CharacterString>evaluationMethodDescription</gco:CharacterString>
     were calculated could be provided as evaluation procedure   citations.
   </mdq:evaluationMethodDescription>
         -->
         <mdq:evaluationProcedure>measure>
                     <cit:CI_Citation><mdq:DQ_MeasureReference>
               <mdq:measureIdentification>
         <cit:title>
         <mcc:MD_Identifier>
                  <gco:CharacterString>title of reference material</gco<mcc:CharacterString>code>
                        <<gco:CharacterString>measureIdentifier</citgco:title>CharacterString>
                        <cit:date gco:nilReason="missing"/>
</mcc:code>
                  </mcc:MD_Identifier>
               </citmdq:CI_Citation>measureIdentification>
                  </mdq:evaluationProcedure><mdq:nameOfMeasure>
                  <mdq:evaluationMethodType><gco:CharacterString>nameOfMeasure</gco:CharacterString>
               </mdq:nameOfMeasure>
           <mdq:DQ_EvaluationMethodTypeCode codeList="codeListLocation#DQ_EvaluationMethodTypeCode" codeListValue="direct_external">direct_external</mdq:DQ_EvaluationMethodTypeCode>    <mdq:measureDescription>
                  <<gco:CharacterString>measureDescription</mdqgco:evaluationMethodType>CharacterString>
               </mdq:DQ_FullInspection>measureDescription>
            </mdq:evaluationMethod>DQ_MeasureReference>
         </mdq:measure>
         <!--
                The resultevaluation ismethod theprovides actuala resultdescription of how the qualitymeasure test.was Thereused arein fourthe typescontext of results: DQ_QuantitativeResult,a particular dataset
                DQ_ConformanceResult, QE_CoverageResult (from ISO 19115-2), and DQ_DescriptiveResult (from ISO 19157). in order to generate the quality report. ISO 19157 includes a new abstract DQ_DataEvaluation class that can be implemented
               -->
 as DQ_FullInspection, DQ_SampleBasedInspection, or DQ_IndirectEvaluation. It includes three elements that are relevant to the <mdqevaluationMethod:result>
               <mdq:DQ_QuantitativeResult>
   the type is a codelist with values of directInternal, directExternal, or indirect; the evaluationMethodDescription
  <mdq:value>
              is a text description that is  <gco:Record/>
          available to a user along with the metadata record; the evaluationProceedure provides
        </mdq:value>
        a citation to more detailed information.
     <mdq:valueUnit xlink:href="AnyValidURI"/>
      -->
         </mdq:DQ_QuantitativeResult><mdq:evaluationMethod>
            </mdq:result>
<mdq:DQ_FullInspection>
             <mdq:result>  <!--
               <mdq:QE_CoverageResult>
         The dateTime gives the date and time of  <mdq:spatialRepresentationType/>
      the quality test in ISO1601 compliant text format
            <mdq:resultSpatialRepresentation/>
   -->
               <mdq:resultContentDescription/>dateTime>
                  <mdq:resultFormat/><gco:DateTime>2012-10-02T15:44:00</gco:DateTime>
                  <mdq:resultFile/></mdq:dateTime>
               </mdq:QE_CoverageResult>
<mdq:evaluationMethodDescription>
                </mdq:result>
  <gco:CharacterString>evaluationMethodDescription</gco:CharacterString>
               <mdq</mdq:result>evaluationMethodDescription>
               <mdq:DQ_ConformanceResult>evaluationProcedure>
                  <mdq:specification/>
<cit:CI_Citation>
                     <mdq<cit:explanation/>title>
                  <mdq:pass/>
      <gco:CharacterString>title of reference material</gco:CharacterString>
      </mdq:DQ_ConformanceResult>
               </mdqcit:result>title>
            <mdq:result>
               <mdq:DQ_QuantitativeResult><cit:date gco:nilReason="missing"/>
                  <mdq:value></cit:CI_Citation>
                     <gco:Record/></mdq:evaluationProcedure>
                  </mdq:value><mdq:evaluationMethodType>
                  <mdq:valueUnit xlink:href="AnyValidURI"/>DQ_EvaluationMethodTypeCode codeList="codeListLocation#DQ_EvaluationMethodTypeCode" codeListValue="direct_external">direct_external</mdq:DQ_EvaluationMethodTypeCode>
               </mdq:DQ_QuantitativeResult>evaluationMethodType>
            </mdq:result>DQ_FullInspection>
            <mdq:result></mdq:evaluationMethod>
         <!--
      <mdq:QE_CoverageResult>
          The result is the actual result of  <mdq:spatialRepresentationType/>
         the quality test. There are four types of results: DQ_QuantitativeResult,
         <mdq:resultSpatialRepresentation/>
       DQ_ConformanceResult, QE_CoverageResult (from ISO 19115-2), and DQ_DescriptiveResult (from ISO 19157). A <mdq:resultContentDescription/>single
                report  <mdq:resultFormat/>can contain one or two results.
            -->
         <mdq:resultFile/>result>
            <mdq:DQ_QuantitativeResult>
   </mdq:QE_CoverageResult>
            </mdq:result>
!-- 
             <mdq:result>
               <mdqgmd:DQ_ConformanceResult>QuantitativeResult:
                  <mdq:specification/>
          
        <mdq:explanation/>
                  <mdq:pass/>
  Results of many quality reports are single simple numbers (%'s or counts).  </mdq:DQ_ConformanceResult>
  In those cases a
          </mdq:result>
         </mdq:DQ_QuantitativeAttributeAccuracy>
      </mdq:report>
   </mdq:DQ_DataQuality>
</mdb:dataQualityInfo>

DQ_QuantitativeResult can be used to hold the result.
                            
                            Unit definitions generally come from an accepted source that can be referenced for an authoritative 
                            definition. In Earth Science the UDUNITS package is commonly used (http://www.unidata.ucar.edu/software/udunits/). 
                            A more general source for unit definitions is "The Unified Code for Units of Measure" (http://unitsofmeasure.org).
                            See https://coastwatch.pfeg.noaa.gov/erddap/convert/units.html for a comparison of the two approaches.
                            
                            The xlink included in the valueUnit is designed to provide an unambiguous identifier for the definition of the
                            unit. Neither UCUM not UDUNITS support such URIs. UCUM does have a table of unit abbreviations and definitions
                            at http://unitsofmeasure.org/ucum.html#section-Alphabetic-Index. These can be referenced as
                            degrees Celsius = xlink:href="http://unitsofmeasure.org/ucum.html#Cel"                           
                        -->
               <mdq:value>
                  <!--
                                A Record is a string of value(s) with a given type. In most quantitative quality reports the type is a simple
                                primative type (gco:Real_PropertyType, gco:Integer_PropertyType). In other cases, it could be a string
                                (gco:CharacterString_PropertyType) that includes multiple numbers.                               
                            -->
                  <gco:Record xsi:type="gco:Integer_PropertyType">
                     <gco:Integer>999</gco:Integer>
                  </gco:Record>
               </mdq:value>
               <mdq:valueUnit xlink:href="AnyValidURI"/>
            </mdq:DQ_QuantitativeResult>
         </mdq:result>
         <mdq:result>
            <mdq:QE_CoverageResult>
               <!--
                            gmi:QE_CoverageResult:
                            
                            The gmi:QE_CoverageResult is used to provide a quality report that is in the form of a coverage (e.g. a
                            timeseries or grid). It therefore shares a number of elements with coverage descriptions. In cases where
                            these elements are repeated in a single metadata record, these can be references to elements that are
                            completely described elsewhere in the record (e.g. xlink:href="#datasetspatialRepresentation").
                            
                            The resultFile and resultFormat can be used to describe a coverage result that is in a different file.
                        -->
               <mdq:spatialRepresentationType/>
               <mdq:resultSpatialRepresentation/>
               <mdq:resultContentDescription/>
               <mdq:resultFormat/>
               <mdq:resultFile/>
            </mdq:QE_CoverageResult>
         </mdq:result>
         <mdq:result>
            <mdq:DQ_ConformanceResult>
               <!--
                            gmd:DQ_ConformanceResult:
                            
                            The gmd:DQ_ConformanceResult is used to provide a quality report on conformance of a dataset to a
                            particular standard, e.g. an OGC Web Service or OPeNDAP.
                            
                            The result in this case is a Boolean, i.e. True or False.
                        -->
               <mdq:specification/>
               <mdq:explanation/>
               <mdq:pass/>
            </mdq:DQ_ConformanceResult>
         </mdq:result>
         <mdq:result>
            <mdq:DQ_DescriptiveResult>
               <!--
                  DQ_DescriptiveResult
                  The DQ_DescriptiveResult provides an opportunity to include a character string describing the quality test. 
                  These are similar to the dataQuality element in the DIF metadata standard.
            -->
               <mdq:statement/>
            </mdq:DQ_DescriptiveResult>
         </mdq:result>
      </mdq:DQ_QuantitativeAttributeAccuracy>
   </mdq:report>
</mdq:DQ_DataQuality>