Thanks for the reply,
> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Monday, May 23, 2005 9:02 AM > To: [email protected] > Subject: Re: Handling of schemaLocation attribute > > > The schemaLocation attribute whose value syntax is pairs of namespace > > names/xsd file locations only works correctly when there are no space > > characters in the xsd file location. Is this a bug or a feature? > > It's a feature, because the pairs are URIs. Also, since there can be more > than one pair, how is that you expect the parser to determine the > boundaries, if the individual elements can contain space characters? See my second post on this issue. The URI is formed correctly, but when expanded it contains spaces in the path part of the URI. And it has to be expanded because it does not reside in the current working directory, rather in a directory relative to the location of the xml file. So my only question is what library/library call is commonly used to patch up file names to conform to the URI format? Thanks, Elisha > > > Under Win32 I can't predict or count on when the full path to the xsd > > filename will have space characters so something seems broken here. > > That's why the pairs are URIs. > > Dave > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
