ISSUE 186: Missing normative statements in section 4.13.2

[Bryan Aupperle <aupperle@us.ibm.com>]

We had some discussion about moving this
to chapter 8.  I think a discussion in 4.13 is still appropriate...

4.13.2        Using XSDHelper for Types Without an XSD Definition

The XSDHelper can generate a new XSD for Types that do not already have an XSD definition. This is useful when the source of the Types come from services in another domain, such as relational databases, programming languages and UML. The XSD MUST be generated according to the rules in 8:  Generation of XSD from SDO Type and Property. [COR04130201]

If an XML Schema was originally used to define the Types, the original XSD SHOULD be used instead of generating a new XSD. [COR04130202] An XSD can contain more information than a Type definition so a generated XSD is not guaranteed to be compatible the original XSD and might validate different documents. The XMLHelper MUST use the original XSD if one exists, otherwise it will use a generated XSD. [COR04130203]

Bryan Aupperle, Ph.D.
STSM, WebSphere Enterprise Platform Software Solution Architect
WW Center of Excellence for Enterprise Systems & Banking Center of Excellence Application Integration Architect

Research Triangle Park,  NC
+1 919-254-7508 (T/L 444-7508)
Internet Address: aupperle@us.ibm.com