Right now monitord does not set any local schema location to tell the XML parser to prefer a local copy of invocation schema from the etc file.
This means that whenever monitord runs , the xsd file is pulled down from the pegasus website location mentioned in the kickstart output.
Mats had noticed in the past week, schema was pulled 1600 times.

The JAVA XML parsers ensure that local schema files are loaded from PEGASUS_HOME/etc directory

Same should be the case for monitord

In Python you can use
http://docs.python.org/library/xml.sax.handler.html#entityresolver-objects

to set the local schema location