W3C home > Mailing lists > Public > xmlschema-dev@w3.org > January 2003

Re: Validating lax ANY content with W3C XML Schema validators

From: Paul Kiel <paul@hr-xml.org>
Date: Wed, 15 Jan 2003 10:14:45 -0500
Message-ID: <001301c2bca8$d74eaba0$6601a8c0@paul>
To: "Anthony B. Coates" <abcoates@londonmarketsystems.com>, <xmlschema-dev@w3.org>

We ran across this inconsistency in parser handling as well.  Very
frustrating.  We ended up eliminating the processContents attribute
altogether.  Without it, one can predict what parsers will do, with it -
there is inconsistency.  This is a very useful feature that is not usable
because of this inconsistency.

BTW - we plan on dropping the "namespace=##other" as well in our extension
elements, as we found that some implementers wanted to put additional
HR-XML-defined components inside the ANY extension.  For example, say we
have a PostalAddress element defined in our namespace.  Some implementers
wanted an additional PostalAddress inside the extension (whether it was for
some legacy reason or missed at design time or some other reason).  In order
to do this, they would need to use the HR-XML defined PostalAddress in
another namespace in order to extend.  Not what we had in mind for sure.  So
we erred on the side of allowing the possibility of other "stuff" inside the
ANY extension in our namespace (although documented as not to be done)
rather than prevent HR-XML objects from being used in the extensions
(without a work around).

Paul Kiel
HR-XML


----- Original Message -----
From: "Anthony B. Coates" <abcoates@londonmarketsystems.com>
To: <xmlschema-dev@w3.org>
Sent: Wednesday, January 15, 2003 6:04 AM
Subject: Validating lax ANY content with W3C XML Schema validators


>
> This is an issue that came out of a discussion on the public "newsml"
list.
> NewsML has a "DataContent" element which can contain any non-NewsML
content,
> and the "xsd:any" validation is set to "lax".  Some NewsML users were
unclear
> how to add a Schema for the non-NewsML content, so I posted some examples
(270K
> ZIP file):
>
> http://www.londonmarketsystems.com/newsml/newml-embedded-content.zip
>
> In one of my examples, "invalidContent.xml", the "xsd:any" content has a
> Schema, and the content is intentionally invalid.  As I read the W3C XML
Schema
> spec, the "xsd:any" content should be validated using the Schema, and the
error
> should be flagged.  Turbo XML & XSV both flag the error as I would expect,
but
> XML Spy doesn't.  Xerces is ruled out because it ignores
> "xsi:noNamespaceSchemaLocation" if there is also an "xsi:schemaLocation",
and
> so it can't validate my examples correctly.
>
> Am I right in my expectation here, that lax "xsd:any" content should be
able to
> cause real validation errors whenever a Schema for that content can be
found?
>
> Cheers,
> Tony.
> ====
> Anthony B. Coates
> London Market Systems Limited
> 33 Throgmorton Street, London, EC2N 2BR
> http://www.londonmarketsystems.com/
> mailto:abcoates@londonmarketsystems.com
> Mobile/Cell: +44 (79) 0543 9026
> [MDDL Editor (Market Data Definition Language), http://www.mddl.org/]
> [FpML Arch WG Member (Financial Products Markup Language),
http://www.fpml.org/]
> -----------------------------------------------------------------------
> This Email may contain confidential information and/or copyright material
and is intended for the use of the addressee only.
> Any unauthorised use may be unlawful. If you receive this Email by mistake
please advise the sender immediately by using the reply  facility in your
e-mail software.
> Email is not a secure method of communication and London Market Systems
Limited cannot accept responsibility for the accuracy or completeness of
this message or any attachment(s). Please examine this email for virus
infection, for which London Market Systems Limited accepts no
responsibility. If verification of this email is sought then please request
a hard copy. Unless otherwise stated any views or opinions presented are
solely those of the author and do not represent those of London Market
Systems Limited.
>
>
Received on Wednesday, 15 January 2003 10:19:52 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 11 January 2011 00:14:35 GMT