Hi CJellick,
Unfortunately, you will have to manually edit it. This is one of the big limitations of developing a schema inside of InfoPath's content model editor (i.e. the datasource editor in the taskpane). You can export the files and do a search and replace in the xsf, xsd, and code for the namespace to replace it, but that's some work and if you make a mistake will result in a template that can't be opened. Usually, what we do is develop the xsd schema outside of InfoPath and then import. That way you can use your own namespace without much hassle. Take a look at the out-of-box samples that ship with InfoPath (for example, Absence Request). These all have their own namespace.
Patrick Halstead [InfoPath MVP]
InfoPathDev
Patrick Halstead
Project Manager at Qdabra