[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

XSD Schema type derived by restriction problem

• From: "Christopher Loschen" <closchen@stanfordalumni.org>
• To: <xml-dev@lists.xml.org>
• Date: Fri, 20 Nov 2009 13:10:51 -0500

Hi all,

This seemed like a good case to ask the experts about.

I'm working with a schema that defines a type by restricting the simple
dateTime type. Our mapping rules (based on the JAX-RPC spec) map this to the
class of the parent type (in this case, java.util.Calendar) rather than
creating a new class to represent the derived type. Consequently, when we
generate an XML message we specify that this element is of
xsi:type="xs:dateTime" (that is, the parent type).

However, when we do that, the schema validator flags the XML as invalid: it
cites an invalid QName at the xsi:type="xs:dateTime" attribute.

It makes sense to me that if the derived type is valid, the parent type should
also be valid: after all, any instance of the derived type will also be of the
parent type by polymorphism. Is that the case in the XML Schema spec? If so,
we should change our schema validator so that it accepts the parent as well as
the child in this situation. If not, I'm not sure how we can implement JAX-RPC
as specified.

Thanks for your insight!

Best regards,
Chris Loschen


____________________________________________________________________
   

• Follow-Ups:
  • RE: XSD Schema type derived by restriction problem
    • From: "Michael Kay" <mike@saxonica.com>
  • Re: XSD Schema type derived by restriction problem
    • From: "G. Ken Holman" <gkholman@CraneSoftwrights.com>