XSD Validations

The system performs the validations of the ACES XML schema based on the XSD standards. The ACES XML format must follow a defined structure as per the XSD provided by the Auto Care industry. It must follow the syntax rules that are specified as per the XSD.

The system is enhanced to accept the XML version with latest ACES 4.1 XSD Schema. Currently, the system supports 3.2, 4.0, 4.1, and 4.2 XSD versions. If the ACES XML file is not compliant with the Auto Care standards, then the XSD Validation fails and an error is displayed. You must check the formatting of ACES XML file to make sure that it adheres to the ACES 3.2, 4.0, 4.1 and 4.2 XSD Schema standards.

The ACES XSD file:
ACES_4_1_XSDSchema.xsd

Scenario 1

Consider a scenario where ACES XML file is imported with the XSD version 4.2.

Result: The XSD Validation fails and error message is displayed.

{% highlight json %}
{% raw %}
<?xml version="1.0" encoding="UTF-8"?>
<ACES version="4.2"> ----> // Invalid //
	<Header>.....</Header>
    <App>..</App>
  <Footer>...</Footer>
</ACES>

Note:

Any file which is not compliant to 3.2, 4.0, and 4.1 XSD versions are rejected from the system with an error message.

Scenario 2

Consider a scenario where the mandatory attribute " BaseVehicleid" is not specified in XML file and is imported to the system.

Result: The XSD Validation fails and error message is displayed. If the error message section displays the following messages, then the ACES file uploaded is invalid or the failed XSD validation.

“Unable to parse file. Please ensure that it is a valid ACES file.”
“No valid header found. ACES header needs to be within
tags.
“Failed XSD validation. Example Value Error. Line Number: #; column number

// Invalid //

  <App action="A" id="1532" validate="yes">
    <!-- Evo_ID = "89830" --> 
    <DriveType id="7"/>
    <EngineBase id="396"/>
    <TransmissionMfrCode id="138"/>
    <TransmissionNumSpeeds id="6"/>
    <Note>tag id: 4MJP</Note>
    <Qty>1</Qty>
    <PartType id="8556"/>
    <Position id="1"/>
    <Part>PS287</Part>
  </App>
  
// Valid // 

  <App action="A" id="1531" validate="yes">
    <!-- Evo_ID = "89829" --> 
    <BaseVehicle id="17838"/>-----> Mandatory attribute
    <DriveType id="7"/>
    <EngineBase id="396"/>
    <TransmissionMfrCode id="138"/>
    <TransmissionNumSpeeds id="6"/>
    <Note>tag id: 4MJP</Note>
    <PartType id="8008"/>
    <Position id="1"/>
    <Qty>1</Qty>   
    <Part>PS287</Part>
  </App>

Scenario 3

Consider a scenario where the mandatory attribute "EquipmentBase id" is not specified in XML file and is imported to the system.

Result: The XSD Validation fails, and error message is displayed. If the error message section displays the following messages, then the ACES file uploaded is invalid or the failed XSD validation.

“Unable to parse file. Please ensure that it is a valid ACES file.”
“No valid header found. ACES header needs to be within tags.”
“Failed XSD validation.” Example Value Error. Line Number: #; column number.

//Invalid
<App action="A" id="2">
  <Qty>1</Qty>
  <PartType id="3768"/> 
  <Part>R-6104</Part>
</App>

//Valid
<App action="A" id="2">
  <EquipmentBase id=“7221”/> <!-- Mandatory attribute -->
  <Qty>1</Qty>
  <PartType id="3768"/> 
  <Part>R-6104</Part>
 </App>