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
3.7.3.2: This section reads as if schema types generally are put in their own namespaces pertaining to areas and services (5.2), but the corresponding XML elements for use as body parts are put in the malxml-prefixed namespace. This allows name collisions, although it does not impede processability: Names are irrelevant when knowing the service specification and what element to expect (and in case multiple elements are allowed due to a defined abstract type, the "type" attribute suffices to choose the correct MAL type). Still, it makes it impossible to perform a proper validation using XML Schema. Therefore, the namespace rules for XML elements for use as body parts should be exactly the same as for XML types corresponding to MAL types (i.e. 5.2.1 to 5.2.3 adapted to XML elements). 3.7.3.2.1 should be removed and the XML namespace for Body in 3.7.3.2.2 explicitly mentioned.
The text was updated successfully, but these errors were encountered:
3.7.3.2: This section reads as if schema types generally are put in their own namespaces pertaining to areas and services (5.2), but the corresponding XML elements for use as body parts are put in the
malxml
-prefixed namespace. This allows name collisions, although it does not impede processability: Names are irrelevant when knowing the service specification and what element to expect (and in case multiple elements are allowed due to a defined abstract type, the "type" attribute suffices to choose the correct MAL type). Still, it makes it impossible to perform a proper validation using XML Schema. Therefore, the namespace rules for XML elements for use as body parts should be exactly the same as for XML types corresponding to MAL types (i.e. 5.2.1 to 5.2.3 adapted to XML elements). 3.7.3.2.1 should be removed and the XML namespace forBody
in 3.7.3.2.2 explicitly mentioned.The text was updated successfully, but these errors were encountered: