Schema Locations

For the XML processor that receives the XML document to be able to validate the XML document

All xsd files must reside in the XML processor’s current directory, otherwise it will not be able to locate the xsd files. If you want to provide a URL and/or a local directory path for the xsd files, you have to give a specific schema location value. If the mapping uses custom namespaces, you also have to type the locations for all custom schemas for the used custom namespaces.

A schema (xsd file) can be located by a local file path, or an internet URL.

BOD instance example:

<SyncProductionOrder xmlns="http://schema.infor.com/InforOAGIS/2" 
xmlns:cust="http://schema.infor.com/InforOAGIS/Custom" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://schema.infor.com/InforOAGIS/2 SyncProductionOrder.xsd" 
releaseID="9.2" versionID="2.7.0">

Example with a custom namespace using two custom schemas:

<SyncProductionOrder xmlns="http://schema.infor.com/InforOAGIS/2" 
xmlns:cust="http://schema.infor.com/InforOAGIS/Custom" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://schema.infor.com/InforOAGIS/2 SyncProductionOrder.xsd 
http://schema.infor.com/InforOAGIS/Custom CustomHeader.xsd 
http://schema.infor.com/InforOAGIS/Custom CustomDetail.xsd" 
releaseID="9.2" versionID="2.7.0">

For the XML processor that receives the XML document to be able to validate the XML document

All xsd files must reside in the XML processor’s current directory, otherwise it will not be able to locate the xsd files. If you want to provide a URL and/or a local directory path for the xsd files, you have to give a specific schema location value. If the mapping uses custom namespaces, you also have to type the locations for all custom schemas for the used custom namespaces.

If you type the schema location in the field "Schema Location", you can use any file paths or internet URLs for the schema files.

Example schema location string and the resulting root tag:

http://schema.infor.com/2.7.0/InforOAGIS/BODs/Developer/SyncProductionOrder.xsd

<SyncProductionOrder xmlns="http://schema.infor.com/InforOAGIS/2" 
xmlns:cust="http://schema.infor.com/InforOAGIS/Custom" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://schema.infor.com/InforOAGIS/2  
http://schema.infor.com/2.7.0/InforOAGIS/BODs/Developer/SyncProductionOrder.xsd" 
releaseID="9.2" versionID="2.7.0">

The same example with a custom namespace using two custom schemas:

http://schema.infor.com/2.7.0/InforOAGIS/BODs/Developer/SyncProductionOrder.xsd

http://schema.infor.com/Custom Custom\UserAreaExtensions\Customer\CustomHeader.xsd

http://schema.infor.com/Custom Custom\UserAreaExtensions\Customer\CustomDetail.xsd

<SyncProductionOrder xmlns="http://schema.infor.com/InforOAGIS/2" 
xmlns:cust="http://schema.infor.com/InforOAGIS/Custom" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://schema.infor.com/InforOAGIS/2  
http://schema.infor.com/2.7.0/InforOAGIS/BODs/Developer/SyncProductionOrder.xsd 
http://schema.infor.com/Custom Custom\UserAreaExtensions\Customer\CustomHeader.xsd 
http://schema.infor.com/Custom Custom\UserAreaExtensions\Customer\CustomDetail.xsd" 
releaseID="9.2" versionID="2.7.0">