I've just tried validating the XSD for new draft "Business Process Execution Language for Web Services" and Stylus kicked a stink apparently because the import declaration doesn't include a schemaLocation attribute.
So I tried changing the import declaration, stuffing in a schemaLocation with any old URI. After which the schema promptly validated.
Checking the XMLSchema structures specification it states that a schemaLocation is completely optional for an import declaration.
Subject:Re: SS Bug: Can't validate legal XSD Author:(Deleted User) Date:22 Aug 2002 05:40 AM
At 21.27 21/08/2002 -0400, you wrote:
>From: "Lee Humphries"
>
>I've just tried validating the XSD for new draft "Business Process
>Execution Language for Web Services" and Stylus kicked a stink apparently
>because the import declaration doesn't include a schemaLocation attribute.
>
>So I tried changing the import declaration, stuffing in a schemaLocation
>with any old URI. After which the schema promptly validated.
>
>Checking the XMLSchema structures specification it states that a
>schemaLocation is completely optional for an import declaration.
Hi Lee,
thanks for reporting this; even if it's a feature that is not mandatory
(the specs state "When no schemaLocation [attribute] is present, the schema
author is leaving the identification of that schema to the instance,
application or user..."), I think it's generic enough to be incorporated in
the Xerces parser.
The patch should be available shortly.