- From: Martin Gudgin <marting@develop.com>
- Date: Fri, 8 Feb 2002 17:56:52 -0000
- To: "Donna Bergmark" <bergmark@CS.Cornell.EDU>, <xmlschema-dev@w3.org>
- Cc: <bergmark@CS.Cornell.EDU>, <Herbert.VandeSompel@bl.uk>, <lagoze@CS.Cornell.EDU>
How a schema processor finds a schema for a given namespace is it's own business. Dereferencing namespace URIs is one way, schema processors can ( and do ) use other ways. I believe that XSV dereferences namespace URIs as a 'last resort' iff it cannot find a schema any other way. How are you specifying to XSV where to find the schema documents? Using xsi:schemaLocation? Passing schema documents on the command line ( as extra arguments to the web form )? Martin Gudgin ----- Original Message ----- From: "Donna Bergmark" <bergmark@CS.Cornell.EDU> To: <xmlschema-dev@w3.org> Cc: <bergmark@CS.Cornell.EDU>; <Herbert.VandeSompel@bl.uk>; <lagoze@CS.Cornell.EDU> Sent: Friday, February 08, 2002 5:32 PM Subject: XSV - xmlns errors > We are still happily using XSV to validate potention OAI repositories > against the OAI protocol specification. We have one recurring problem > with XSV: it tries to open and parse xmlns attribute values. > > It is my understanding that xmlns=foo is just a namespace. It does not > have to be a URL, it does not have to > be locatable. A repository I am currently looking at has an info.pdf > as its namespace! That is legal, but XSV > tries to fetch it and parse it as XML. > > I do not believe you should be checking the xmlns attribute values. > > Sincerely, Donna Bergmark >
Received on Friday, 8 February 2002 12:57:52 UTC