You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Complex types defined in common.xsd make use of types defined in measure.xsd but the file is not included.
Attempt to perform schema validation on common.xsd
Types "iwxxm:LengthWithNilReasonType" and "iwxxm:DistanceWithNilReasonType" are undefined
These missing types are defined in "measure.xsd"
Schema files are expected to pass schema validation.
Adding an <include schemaLocation="measures.xsd"/> directive near the top of common.xsd file resolves the errors.
If implemented, this makes the include directives of "measure.xsd" and "common.xsd" in iwxxm.xsd unnecessary as individual product schemas all include common.xsd again. This may be due to EA production. However, repeated calls to include schemas do not seem to have harmful effects.
The text was updated successfully, but these errors were encountered:
Adding an directive near the top of common.xsd file resolves the errors.
If implemented, this makes the include directives of "measure.xsd" and "common.xsd" in iwxxm.xsd unnecessary as individual product schemas all include common.xsd again. This may be due to EA production. However, repeated calls to include schemas do not seem to have harmful effects.
True and agreed with the suggested changes.
A more drastic change is to incorporate them into common.xsd, just like StringWithNilReasonType. @mgoberfield any views on this?
Complex types defined in common.xsd make use of types defined in measure.xsd but the file is not included.
Schema files are expected to pass schema validation.
Adding an
<include schemaLocation="measures.xsd"/>
directive near the top of common.xsd file resolves the errors.If implemented, this makes the include directives of "measure.xsd" and "common.xsd" in iwxxm.xsd unnecessary as individual product schemas all include common.xsd again. This may be due to EA production. However, repeated calls to include schemas do not seem to have harmful effects.
The text was updated successfully, but these errors were encountered: