|  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
 | | |  |  |  | This package contains the implementations of the W3C XML 
        Schema 1.0 and 1.1 Languages, that are recommendation of the Worldwide Web Consortium.
        The XML Schema 1.0 Language is available in three parts:  
        XML Schema:  Primer  and
        XML Schema:  Structures  and
        XML Schema:  Datatypes.        
        The XML Schema 1.1 Language is available in two parts:
        Structures and
        Datatypes.
        The XML Schema 1.1 features supported by this release are listed below.
        In this document we also discuss our interpretation of the
        specifications where it seems to us particularly likely that
        others might arrive at a different interpretation.
        We consider this implementation to be complete except for the
        limitations cited below. The implementation has been
        extensively tested and known problem areas are set out below.
        Please read this document before using this package.
         | 
 
 
 | |  |  |  |  |  |  Supported XML Schema 1.1 Features |  |  |  |  |  | 
 |  |  | 
           All Groups
              maxOccurs may now be >1Wildcards are now allowedDerivation by extensionxs:group is allowed as a child of xs:all AssertionsConditional Type AssignmentSimplified Complex Type restriction rules (also known as Subsumption)Open Content and Default Open ContentDefault attribute groupTarget namespace on local element/attribute declarationsElement declarations allowed in more than one substitution groupWildcards
              not namespacenot QNamenot #definednot #definedSiblingRelaxation of UPA in the presence of wildcards Overriding component definitions (xs:override)Conditional Inclusion
              vc:minVersionvc:maxVersionvc:typeAvailablevc:typeUnavailablevc:facetAvailablevc:facetUnavailable Context property for local simple/complex type definitionsexplicitTimezone facet and dateTimeStamp derived typeyearMonthDuration and dayTimeDuration derived typesprecisionDecimal typeUnion types not expandedID/IDREF
              Lists of IDUnions involving IDMultiple attributes of type IDDefault values of type IDREFDefault values for elements or attributes of type ID | 
 
 |  |  |  | 
             Length, minLength, and maxLength facets are limited to the value 
            2147483647. Items larger than this limit will not be validated 
            correctly. The values of minOccurs and maxOccurs attributes are limited to
            the value 2147483647. Items larger than this limit will not be
            validated correctly. The values of minimum and maximum quantifiers in the pattern
            regular expressions are limited to the value 2147483647.
            Items larger than this limit will not be validated correctly. The absolute values of the fraction portion of the second values
            in date/time datatypes are limited to the value 2147483647.
            Items larger than this limit will not be validated correctly.
            i.e. 11.2147483648 is not supported as a second value.  Leap seconds are not supported in the values of date/time datatypes. | 
 
 |  |  |  | 
             For larger values of maxOccurs, an OutOfMemoryError may occur.
            The workaround for this problem, if your application permits it, 
            is to change the maxOccurs value to unbounded. If you are unable to
            change the schema you can configure Xerces-J so that it fails more
            gracefully by enabling the JAXP secure processing feature. See the
            Javadoc for javax.xml.XMLConstants.FEATURE_SECURE_PROCESSING for
            more details.
             The JAXP class javax.xml.validation.Schema is defined to be thread 
            safe. That is, applications are encouraged to share javax.xml.validation.Schema objects 
            across multiple threads. Some Xerces users have reported that, while doing XML Schema 1.1 
            validation javax.xml.validation.Schema is seen to be not thread safe. This problem was 
            observed in certain use cases, while using the XSD 1.1 construct <assert> in the 
            XSD documents. But there are also, various cases observed while using XSD 1.1 
            construct <assert>, when thread safety of javax.xml.validation.Schema is 
            seen to be working correctly.
             | 
 
 |  |  |  | 
         As of version 2.2.1, it is hoped that Xerces-J will always 
        be able to parse the Schema for Schemas current at the time of the product's release.  As of version
        2.2.1, this implies inserting special logic to permit the presence of
        the built-in Schema datatypes in this particular schema; an
        issue has been raised with the Schema Working Group, in hopes the document
        will be modified so that the built-in types are no
        longer presented as global components.  Thus, anyone planning
        to rely on the Schema for Schemas should be aware that the
        possibility exists that a change of this sort might be made in the future. In the original XML Schema recommendation, the lexical space of
        the simple type gMonthis--MM--. An erratum E2-12
        changed that to--MM. For compatibility reasons, Xerces currently
        supports both forms. To align with the recommendation, we have decided to
        deprecate the old form, and plan to discontinue support for that form
        in a future release. | 
 
 | 
 |