aip descriptor: namespace declaration for docmd.xsd is incorrect?

[lydiam]

When an AIP descriptor is archived as a content file in a new SIP XMLResolution currently can't download the docmd.xsd schema referenced in the file. I believe that the namespace declaration for docmd.xsd is incorrect in AIP descriptors.

An example of how AIP descriptors currently reference docmd.xsd:

ripple IEID EN4HCFV1P_V0BPS0:

 <doc xmlns="http://www.fcla.edu/dls/md/docmd" xsi:schemaLocation="http://www.fcla.edu/docmd http://www.fcla.edu/dls/md/docmd.xsd">

When the AIP descriptor from ripple IEID EN4HCFV1P_V0BPS0 is archived as a content file in ripple IEID EEO151GRN_L3JL3R, the manifest says:

 schema status="unresolved" namespace="http://www.fcla.edu/dls/md/docmd"

The actual docmx.xsd targetNamespace="http://www.fcla.edu/docmd"

When the schema reference is changed to the following XMLResolution downloads the schema:

 <doc xmlns="http://www.fcla.edu/docmd"  xsi:schemaLocation="http://www.fcla.edu/docmd http://www.fcla.edu/dls/md/docmd.xsd">

Is the namespace declaration for docmd in AIP descriptors wrong?

[cchou]

Yes, I will work on this.

[lydiam]

Carol,

Try the following in the AIP descriptor:

 <doc  xmlns="http://www.fcla.edu/docmd"  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.fcla.edu/docmd http://www.fcla.edu/dls/md/docmd.xsd">

[jonpitts]

This issue should not come up in Resolver. XML Resolution did not handle targetNamespace and did not properly handle processing instructions. Sometimes XML Resolution would process a namespace as a resource when it shouldn't.