Re: Error validating MODS 3

So funny story about xml.xsd.  As part of National Digital Newspaper Project at the Library of Congress, we
validate tens of thousands of METS / MODS / PREMIS / MARCXML / DIGSIG / etc. documents in large batches.  Our
validation application uses local versions of the schemas, except, accidentally, xml.xsd (which is
referenced by the MODS schema).  Thus, our application was making huge numbers of requests to w3.org,
which did not make them happy.  They began sending emails to the Library threatening to cut off access from
the Library to w3.org.  (In our case, the Library's systems admins overreacted and disconnected our
entire lab from the network, but that's another story that isn't as funny.)

In any case, you may want to see if w3.org has blocked access to you or if in response to a request from w3.org, a
system admin at your institution has blocked access.

Best.
Justin Littman
Library of Congress

______________________________

As of just today, I'm receiving the following error even when validating
MODS that used to pass schema validation. Can anyone point me in the
right direction to fix this?

SystemID: http://www.loc.gov/standards/mods/v3/mods-3-2.xsd Location:
4:111 Description: W schema_reference.4: Failed to read schema document
'http://www.w3.org/2001/xml.xsd', because 1) could not find the
document; 2) the document could not be read; 3) the root element of the
document is not <xsd:schema>. URL:
http://www.w3.org/TR/xmlschema-1/#schema_reference  
SystemID: http://www.loc.gov/standards/mods/v3/mods-3-2.xsd Location:
1096:48 Description: E src-resolve: Cannot resolve the name 'xml:lang'
to a(n) 'attribute declaration' component. URL: