There is currently no portable way to handle the locations of XSD
Schema files imported from WSDL using schemaLocation.
When you use yaws_soap_srv:setup/2 to add a SOAP web service it
uses yaws_soap_lib:initModel/1 to compile the internal representation.
The yaws priv directory is determined and included in the path to
import the SOAP schema however my application's priv dir is where I
have my files.
I looked at yaws_soap_lib:initModelFile/1 however it looks like that
would have the reverse problem and I'd have to hard wire the location
I'm thinking we need a yaws_soap_srv:setup/3 and yaws_soap_lib:initModel/3.