While it should be possible for someone working in MODS in a standalone
environment to save local copies of the schemata and configure the
environment to use those, exactly how depends on the platform and tools
being used, and on user choices. The MODS schema imports the schema for
http://www.w3.org/XML/1998/namespace from its standard location at
the W3C. From where would it import a local copy? That depends on the
local host's file system, web server, environment variables, and so
forth. This is a user issue, not LoC's problem.

As for Barzilai's original problem, that's what caching HTTP clients
are for.

--Andy

>>> [log in to unmask] 02/02/05 11:11 AM >>>
From: "Bruce D'Arcus" <[log in to unmask]>
> On Jan 29, 2005, at 11:16 PM, Barzilai Spinak wrote:
>
> > The thing is, I dont want to download the schemas from the web
*every
> > time*
> > I need validation or a web service is called, etc. I should be
able
> > to store local copies and do relative schemaLocation.
>
> This I absolutely agree with, and would go even further: I think the
> LoC should be releasing totally self-contained schemas, regardless
of
> whether the development process using a bunch of different included
> files.  I should download a single file.

Well we want to do the right thing, but before we do  .....  does
anyone
else feel strongly about this?

Take xlink for example .... when we release a mods schema we should
make
available a (zipped) file that includes the xlink schema, etc?   Why?

When I validate with xmlspy, there is an import statement. If the
schema
isn't where I say it is I get an error, but if the schema is there,
xmlspy
gets it, it's totally transparent, and it happens very quicky --
xmlspy
validates a schema as quickly with imports as without. Is this really
a
hardship?

--Ray