aip descriptor: no schemalocation for textMD schema, others? Are we validating AIP descriptors against format-specific schemas?

[lydiam]

This is related to #713:

Currently our AIP descriptors appear to reference some schema namespaces without including a schemalocation.

An example from ripple IEID EN4HCFV1P_V0BPS0:

 <textMD xmlns="http://www.loc.gov/standards/textMD">

http://www.loc.gov/standards/textMD/textMD.xsd itself doesn't appear to include a targetNamespace:

 <xs:schema elementFormDefault="qualified" attributeFormDefault="unqualified">

Would that prevent us from validating the AIP descriptor against this schema?

Is our objective to be able to validate AIP descriptors against all relevant format-specific schemas?

In this example we do reference another format-specific schema in the AIP descriptor (although we seem to be missing a namespace declaration):

 <?xml version="1.0" encoding="UTF-8"?>
 <mets xmlns="http://www.loc.gov/METS/" 
 xmlns:xlink="http://www.w3.org/1999/xlink" 
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"    
 OBJID="info:fda/E88XBTT1Q_J3OL1H" 
 xsi:schemaLocation="http://www.loc.gov/METS/ http://www.loc.gov/standard/mets/mets.xsd                           
 http://www.aes.org/tcf http://schema.fcla.edu/tcf.xsd                           
 http://www.aes.org/audioObject http://schema.fcla.edu/audioObject.xsd                             
 http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-3.xsd                            
 info:lc/xmlns/premis-v2 http://www.loc.gov/standards/premis/premis.xsd">
 http://www.aes.org/tcf http://schema.fcla.edu/tcf.xsd                          
 http://www.aes.org/audioObject http://schema.fcla.edu/audioObject.xsd          

Would AIP descriptor validation be able to validate against audioObject.xsd in the above AIP descriptor?

Elsewhere in that same AIP descriptor file:

 <aes:audioObject xmlns:aes="http://www.aes.org/audioObject" 
 xmlns:tcf="http://www.aes.org/tcf" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
 ID="J4.1" analogDigitalFlag="FILE_DIGITAL" disposition="Validated by JHOVE" schemaVersion="1.02b">
 <aes:format specificationVersion="">WAVE</aes:format>
              <aes:audioDataEncoding>PCM audio in IEEE floating-point format</aes:audioDataEncoding>

Carol and I discussed this issue, and she thinks that ideally we do want to be sure to validate AIP descriptors against format-specific schemas.

[lydiam]

Note that AIP descriptor references to the mix20.xsd schema appear to be correct.

From AIP descriptor for EBTXAMF29_Z4UYNY on darchive:

 <mix:mix xmlns:mix="http://www.loc.gov/mix/v20" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.loc.gov/mix/v20 http://www.loc.gov/standards/mix/mix20/mix20.xsd">
              <mix:BasicDigitalObjectInformation>
                <mix:ObjectIdentifier>

XMLResolution is able to download the mix20.xsd from the above schema reference, so presumably the AIP descriptor is validated against the schema during the ingest process.

[cchou]

It looks like the template generating the AIP descriptor does not put the schema location in for daitss and textMD. For DocMD, it's missing the xmlns prefix. I will work on fixing them.

Per PREMIS schema, sub-schema wrapped inside PREMIS are validated as long as correct schema location is provided.