External definitions: is xsd:include schemaLocation="..."/ allowed?

Hi everybody,
I guess to remember I read that <xsd:include> is not allowed. Do you have some information?
Regards Mario

http://help.sap.com/bp_bpmv130/Documentation/Operation/MappingXI30.pdf - ref page 33.

Similar Messages

  • Extenal Refence in External Definition

    Hi,
    I need to use an external WSDL as a External Definition. The WSDL contains this line:
    <b><xsd:include schemaLocation="../service/FordringModtagSAP38Interface.xsd" /></b>
    How do i import the includet schema? It´s not allowed to call it <b>../service</b>
    How do i do it??
    /Jakob

    Let me try to explain it better.
    Assume the XSD A refers to XSD B.
    1. Import XSD A.
    2. In XSD A ( the main XSD ), you will find a tab EXTERNAL REFERENCES . In this you should find an entry for Source. Copy this.
    3. Import XSD B.
    4. When you import, you will find a field called Source after you import it. Paste the Copied Text of step 2 here.
    5. Save and activate.
    6. Now, XSD A, in External References should contain both Name and Source filled.
    Regards
    Bhavesh

  • Ant autotype does not seem to recognize xsd:include

    Hi
    I am currently using WebLogic 7.0. I was trying to use ant autotype to generate
    java classes based on a schema. I ran into a problem that the autotype does not
    seem to include the other schema files listed with xsd:include. I could only get
    around the problem by literally copy and paste the complex types definition into
    the calling schema file. Below are the two schemas that illustrate the problem.
    x.xsd includes y.xsd but however the EmployeeBean listed in y.xsd results in a
    unresolve type with autotype. Problem only goes away if EmployeeBean definition
    is listed in x.xsd.
    Any help is much appreciated.
    ==========================================================
    x.xsd
    ==========================================================
    <?xml version="1.0" encoding="utf-8" standalone="no"?>
    <xsd:schema xmlns:ofx="http://ofx.net/v3.0"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    targetNamespace="http://ofx.net/v3.0">
    <xsd:include schemaLocation="y.xsd" />
    <xsd:complexType name="Company">
    <xsd:sequence>
    <xsd:element name="XYZ" type="ofx:EmployeeBean" />
    </xsd:sequence>
    </xsd:complexType>
    </xsd:schema>
    ==========================================================
    y.xsd
    ==========================================================
    <?xml version="1.0" encoding="utf-8" standalone="no"?>
    <xsd:schema targetNamespace="http://ofx.net/v3.0"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:ofx="http://ofx.net/v3.0">
    <xsd:complexType name="EmployeeBean">
         <xsd:sequence>
         <xsd:element name="name"
              type="xsd:string"
              nillable="true"
              minOccurs="1"
              maxOccurs="1">
         </xsd:element>
         <xsd:element name="id"
              type="xsd:int"
              minOccurs="1"
              maxOccurs="1">
         </xsd:element>
         </xsd:sequence>
    </xsd:complexType>
    </xsd:schema>
    =============================================================

    Actually imports will work in most cases, though some bug fixes have
    been made since and will show up in future releases.
    --Scott
    In article <[email protected]>,
    Bruce Stephens <[email protected]> wrote:
    Hello,
    At the moment, we handle wsdl imports as done by SOAPBuilders Round
    3, but not schema imports. Look for this in the upcoming release;
    Contact Michael Bamford ([email protected]) if you would like
    to be on the Beta.
    Thanks,
    Bruce
    Sooleng Lau wrote:
    Thank you for the response and info. What about schema import, is
    it handled by weblogic 7.0 at the moment ? What is the upcoming
    release, is it WebLogic 7.1 ?
    Thank you.
    Soo Leng
    Bruce Stephens <[email protected]> wrote:
    Hello,
    Schema include is a known problem that will be corrected in the upcoming
    release.
    The workaround at this point is the cut and paste :-( you described.
    Bruce
    Sooleng Lau wrote:
    Hi
    I am currently using WebLogic 7.0. I was trying to use ant autotypeto generate
    java classes based on a schema. I ran into a problem that the autotypedoes not
    seem to include the other schema files listed with xsd:include. I couldonly get
    around the problem by literally copy and paste the complex types definitioninto
    the calling schema file. Below are the two schemas that illustratethe problem.
    x.xsd includes y.xsd but however the EmployeeBean listed in y.xsd resultsin a
    unresolve type with autotype. Problem only goes away if EmployeeBeandefinition
    is listed in x.xsd.
    Any help is much appreciated.
    ==========================================================
    x.xsd
    ==========================================================
    <?xml version="1.0" encoding="utf-8" standalone="no"?>
    <xsd:schema xmlns:ofx="http://ofx.net/v3.0"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    targetNamespace="http://ofx.net/v3.0">
    <xsd:include schemaLocation="y.xsd" />
    <xsd:complexType name="Company">
    <xsd:sequence>
    <xsd:element name="XYZ" type="ofx:EmployeeBean" />
    </xsd:sequence>
    </xsd:complexType>
    </xsd:schema>
    ==========================================================
    y.xsd
    ==========================================================
    <?xml version="1.0" encoding="utf-8" standalone="no"?>
    <xsd:schema targetNamespace="http://ofx.net/v3.0"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:ofx="http://ofx.net/v3.0">
    <xsd:complexType name="EmployeeBean">
    <xsd:sequence>
    <xsd:element name="name"
    type="xsd:string"
    nillable="true"
    minOccurs="1"
    maxOccurs="1">
    </xsd:element>
    <xsd:element name="id"
    type="xsd:int"
    minOccurs="1"
    maxOccurs="1">
    </xsd:element>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:schema>
    =============================================================

  • Validation Framework & xsd:include

    I'm having some problems using the new Validation Framework with schemas that have <xsd:include> dependancies.
    Assume this schema (TestSchema.xsd):
    <?xml version="1.0" encoding="UTF-8"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
         <xsd:include schemaLocation="TestInclude.xsd"/>
         <xsd:element name="RootElement">
              <xsd:complexType>
                   <xsd:sequence>
                        <xsd:element name="SubElement1" type="xsd:string"></xsd:element>
                        <xsd:element name="SubElement2" type="xsd:string"></xsd:element>
                        <xsd:element ref="IncludedElement"/>
                   </xsd:sequence>
              </xsd:complexType>
         </xsd:element>
    </xsd:schema>...Which relies on this dependancy (TestInclude.xsd)
    <?xml version="1.0" encoding="UTF-8"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
         <xsd:element name="IncludedElement" type="xsd:string"></xsd:element>
    </xsd:schema>And a simple document based on this Schema (TestDoc.xml)
    <?xml version="1.0" encoding="UTF-8"?>
    <RootElement>
      <SubElement1>Hello</SubElement1>
      <SubElement2>World</SubElement2>
      <IncludedElement>Include me too!</IncludedElement>
    </RootElement>My validation code looks like this:
    public class ValidatorTest
         public ValidatorTest()
              SchemaFactory factory = SchemaFactory.newInstance(
                        XMLConstants.W3C_XML_SCHEMA_NS_URI);
              StreamSource source = new StreamSource(
                        getClass().getResourceAsStream("/TestSchema.xsd"));
              StreamSource includeSource = new StreamSource(
                        getClass().getResourceAsStream("/TestInclude.xsd"));
              Schema schema;
              try
    //By the javadocs, this is the proper way of compiling schemas w/ dependancies
                        schema = factory.newSchema(new StreamSource[]{includeSource,source});
                        System.out.println("Schema compiled.");
                        Validator v = schema.newValidator();
                        StreamSource document = new StreamSource(getClass().getResourceAsStream("/TestDoc.xml"));
                        v.validate(document);
                        System.out.println("Document validated.");
                   catch(Exception ex)
                        ex.printStackTrace();
         }This schema compiles correctly (I see my first log message). But an exception occurs when I call v.validate(document).
    Cannot find the declaration of element 'RootElement'.
    I should also point out that this code works when I test against an xsd that doesn't have an external dependancy.
    Any advice?

    Sigh
    Looks like this is a bug.
    Sigh

  • Specifying Relative pathname with include schemaLocation

    Hi,
    I would like to know how to specify relative path name when including other
    schema definitions. For eg.
    <?xml version="1.0" encoding="UTF-8"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <xsd:include schemaLocation="test.xsd"/>
    gives me an error saying test.xsd not found . If I specify full path like below,
    then it works fine. Any work around for this?.
    <?xml version="1.0" encoding="UTF-8"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <xsd:include schemaLocation
    ="file:///d:/xml/xsdTest/tmx_schema_lib.xsd"/>
    thanks,
    Pat

    Hi,
    Isn't there a way to specify the relative location?
    Thanks,
    Pat.
    Deepak Vohra <[email protected]> wrote:
    >
    >
    The schemaLocation attribute in <xs:include> specifies the schema document
    location
    URI.
    Patrick wrote:
    Hi,
    I would like to know how to specify relative path name when includingother
    schema definitions. For eg.
    <?xml version="1.0" encoding="UTF-8"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <xsd:include schemaLocation="test.xsd"/>
    gives me an error saying test.xsd not found . If I specify full pathlike below,
    then it works fine. Any work around for this?.
    <?xml version="1.0" encoding="UTF-8"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <xsd:include schemaLocation
    ="file:///d:/xml/xsdTest/tmx_schema_lib.xsd"/>
    thanks,
    Pat<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
    <html>
    The schemaLocation attribute in <xs:include> specifies the schema
    document
    location URI.
    <p>Patrick wrote:
    <blockquote TYPE=CITE>Hi,
    <p>     I would like to know how to specify relative
    path name when including other
    <br>schema definitions. For eg.
    <p>     <?xml version="1.0" encoding="UTF-8"?>
    <br>     <xsd:schema xmlns:xsd="<a href="http://www.w3.org/2001/XMLSchema">http://www.w3.org/2001/XMLSchema</a>">
    <br>     <xsd:include schemaLocation="test.xsd"/>
    <p>gives me an error saying  test.xsd not found . If I specify full
    path like below,
    <br>then it works fine. Any work around for this?.
    <p>     <?xml version="1.0" encoding="UTF-8"?>
    <br>     <xsd:schema xmlns:xsd="<a href="http://www.w3.org/2001/XMLSchema">http://www.w3.org/2001/XMLSchema</a>">
    <br>     <xsd:include schemaLocation
    <br>="<a href="file:///d:/xml/xsdTest/tmx_schema_lib.xsd" /">file:///d:/xml/xsdTest/tmx_schema_lib.xsd"/</a>>
    <p>thanks,
    <br>Pat</blockquote>
    </html>

  • Autotype support for xsd import and xsd include statement

    Hi,
    I am using Weblogic 7.0.1. While using autotype for a Schema, I get the error unable to resolve element ref: "qb:WireCenterCLLI. This element exists in an xsd imported in the main XSD which in turn includes a few XSD's. I saw few posts which indicated there were issues with autotype recognising xsd:import and xsd:include statements. Were these issues fixed? If so, what SP were they fixed in?
    My XSD:
    <?xml version = "1.0" encoding = "UTF-8"?>
    <xsd:schema xmlns = "http://www.qwest.com/XMLSchema"
    targetNamespace = "http://www.qwest.com/XMLSchema"
    xmlns:qb = "http://www.qwest.com/XMLSchema/BIM"
    xmlns:xsd = "http://www.w3.org/2001/XMLSchema"
    elementFormDefault = "qualified">
    <xsd:import namespace = "http://www.qwest.com/XMLSchema/BIM" schemaLocation = "/u/skarani/sia_code/xsd/ProjectSpecific/SIA/BIM/AddressValidationInclude_v01_00.xsd"/>
    <xsd:include schemaLocation = "/u/skarani/sia_code/xsd/ProjectSpecific/SIA/Common/AddressValidationCommon_v01_00.xsd"/>
    <xsd:include schemaLocation = "/u/skarani/sia_code/xsd/ProjectSpecific/SIA/Common/RequestMessage_v02_01.xsd"/>
    <xsd:element name = "AddressValidationByServiceIdRequest">
    <xsd:complexType>
    <xsd:complexContent>
    <xsd:extension base = "WebServiceRequestT">
    <xsd:sequence>
    <xsd:element name = "InputData" type = "AddressValidationByServiceIdInputDataT">
    </xsd:element>
    </xsd:sequence>
    </xsd:extension>
    </xsd:complexContent>
    </xsd:complexType>
    </xsd:element>
    <xsd:complexType name = "AddressValidationByServiceIdInputDataT">
    <xsd:sequence>
    <xsd:element ref = "qb:WireCenterCLLI" minOccurs = "0"/>
    <xsd:element ref = "qb:WireCenterPrimaryNPANXX" minOccurs = "0"/>
    <xsd:element ref = "AdministrativeArea" minOccurs = "0"/>
    <xsd:element ref = "qb:PostalCode" minOccurs = "0"/>
    <xsd:element ref = "qb:BTN"/>
    <xsd:element name = "ParsedAddressFlag" type = "xsd:boolean" minOccurs = "0">
    </xsd:element>
    <xsd:element ref = "qb:CCNA" minOccurs = "0"/>
    <xsd:element name = "CompanyCode" type = "xsd:string" minOccurs = "0">
    </xsd:element>
    <xsd:element ref = "AssignedHouseNumberFlag" minOccurs = "0"/>
    <xsd:element ref = "GSGRqmtFlag" minOccurs = "0"/>
    <xsd:element ref = "TNStatus" minOccurs = "0"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:schema>
    Thanks
    Shekhar

    Hmmmm.... No answers!!!
    Has anyone had success using autotype with an xsd having include and import statements???
    Thanks
    Shekhar

  • Error importing xsd as external definition

    I'm importing a wsdl file as external definition and it references some xsd files that I'm trying to import too. Specifically there are 2 of them that I can't import in PI, as I get the next error:
    Error when loading XML document (Failed to load resource from the context classloader of the current thread! Loading from classloader was caused by: java.net.UnknownHostException: www.w3.org)
    XSD files might be found under next urls:
    [XAdES.xsd|https://www3.aeat.es/ADUA/internet/es/aeat/dit/adu/xades/XAdES.xsd]
    [xmldsig-core-schema.xsd|https://www3.aeat.es/ADUA/internet/es/aeat/dit/adu/xades/xmldsig-core-schema.xsd]
    and are meant to be used to sign the document.
    I have validated the files using the service in the next url:
    [http://www.w3.org/2001/03/webdata/xsv|http://www.w3.org/2001/03/webdata/xsv] as well as in Altova XML Spy.
    Has anyone any idea of what the problem might be? It is really interfering in my development.
    Thanks in advance.

    Ok I think I might have solved it. First there was a pair of problems with the file xmldsig-core-schema.xsd.
    1. The name couldn't be used in PI as '-' characters are not allowed.
    I changed the name to xmldsig_core_schema.xsd
    2. The file had these lines at the start:
    <!DOCTYPE schema PUBLIC "-//W3C//DTD XMLSchema 200102//EN" "http://www.w3.org/2001/XMLSchema.dtd" [
         <!ATTLIST schema
         xmlns:ds CDATA #FIXED "http://www.w3.org/2000/09/xmldsig#"
    >
         <!ENTITY dsig 'http://www.w3.org/2000/09/xmldsig#'>
         <!ENTITY % p ''>
         <!ENTITY % s ''>
    ]>
    PI doesn't like that if you import the file as XSD because I guess that is DTD not XSD format.
    I removed those lines.
    With these two changes this file could be imported.
    However I still had problems with the XAdES.xsd file. PI couldn't recognize the import of xmldsig-core-schema.xsd file:
    <xsd:import namespace="http://www.w3.org/2000/09/xmldsig#" schemaLocation="http://www.w3.org/TR/2002/
    REC-xmldsig-core-20020212/xmldsig-core-schema.xsd"/>
    It didn't like the URL, so I changed it to make reference to my local file.
    After this, it all worked. The question is, will it also work in runtime when I'll make use of these external definitions created? Or will my changes have an impact on the results? I guess it will work fine but perhaps I'm wrong.
    Besides, when activated I got the next warning:
    Name of '/schema/complexType("TimeStampType")/sequence/choice/element("XMLTimeStamp")' starts with 'xml'
    There's an element name that starts by XML. Is this forbidden? Will I have problems if I activate and use it just as it is?
    Thanks for the answers.

  • PI does not keep sequence of XSD for external definition

    Hi,
    currently I face following problem. I have an XSD which decribes a MSCONS market message that contains following sequence:
         <xs:complexType name="MSCONS">
              <xs:sequence>
                   <xs:element name="UNH" type="UNH"/>
                   <xs:element name="BGM" type="BGM"/>
                   <xs:element name="DTM" type="DTM"/>
                   <xs:element name="NAD" type="NAD" minOccurs="2" maxOccurs="2"/>
                   <xs:element name="UNS" type="UNS"/>
                   <xs:element name="NAD" type="NAD" maxOccurs="unbounded"/>
                   <xs:element name="CNT" type="CNT" minOccurs="0" maxOccurs="99"/>
                   <xs:element name="UNT" type="UNT"/>
              </xs:sequence>
         </xs:complexType>
    There are 2 NAD elements, followed by an UNS element, followed by an NAD element again. When I upload that XSD to PI as an external definition, the message is described as:
    MSCONS     Message                         
    -> MSCONS     Element     MSCONS     1               Metered services consumption report message
    -> -> UNH     Element     UNH     1               
    -> -> BGM     Element     BGM     1               
    -> -> DTM     Element     DTM     1               
    -> -> NAD     Element     NAD     1..unbounded               
    -> -> UNS     Element     UNS     1               
    -> -> CNT     Element     CNT     0..99               
    -> -> UNT     Element     UNT     1     
    All the NAD elements are summarized before UNS element. After mapping I will get an message which is not valid to XSD, because sequence is not correct.
    Does anyone knows a solution/workaround for that issue. Would appreciate you help.
    Thank you and Best Regards,
    Nico

    > All the NAD elements are summarized before UNS element. After mapping I will get an message which is not valid to XSD, because sequence is not correct.
    >
    > Does anyone knows a solution/workaround for that issue. Would appreciate you help.
    No. There is no way. The way how graphical mapping works internally makes it impossible to achieve your requirement.
    As work around use two different nodes NDA and NAD1 and rename it with a simple Java mapping as second mapping step.

  • "Messages" problem after importing .xsd file as external definition

    Hello,
    I received an .xsd file from a customer and need to import it as an "External Definition" in order to create the "Message Interface". The structure of the xsd looks like this:
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:px="http://www.opentrans.org/XMLSchema/1.0" targetNamespace="http://www.opentrans.org/XMLSchema/1.0" elementFormDefault="qualified">
    <xsd:element name="ORDER">
    </xsd:element>
    <xsd:element name="ADDRESS">
    </xsd:element>
    <xsd:element name="ARTICLE_ID">
    </xsd:element>
    </xsd:schema>
    After importing and looking at the tab "Messages" I get numerous entries, for each <xsd:element> I get one message! But I basically only need one "Message" that holds my complete xsd-file.
    I tried inserting <xsd:element name="COMPLETEORDER"> right after the <xsd:schema>-Tag but that didn't work either. Somehow I need to sum up all the <xsd:elements>.
    Does anyone have an idea? Thank you very much!
    Peter

    Hello Prateek, Hello everyone,
    I now know what the problem is. I downloaded XMLspy and checked on the structure:
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:px="http://www.opentrans.org/XMLSchema/1.0" targetNamespace="http://www.opentrans.org/XMLSchema/1.0" elementFormDefault="qualified">
    <xsd:element name="ORDER">
    </xsd:element>
    <xsd:element name="ADDRESS">
    </xsd:element>
    <xsd:element name="ARTICLE_ID">
    </xsd:element>
    <xsd:simpleType name="dtBOOLEAN">
    </xsd:simpleType>
    <xsd:simpleType name="dtCOUNTRIES">
    </xsd:simpleType>
    <xsd:element name="SUPPLIER_AID">
    </xsd:element>
    <xsd:simpleType name="typeSUPPLIER_AID">
    </xsd:simpleType>
    </xsd:schema>
    Between the long list of <xsd:element> tags there are some simpleTypes on the same
    level. Now if I insert
    <xsd:element name="COMPLETEORDER">
    <xsd:complexType>
    <xsd:sequence>
    on top, the <xsd:sequence> would be on the same level as the simpleTypes - which is not valid!
    But can I just move all the simpleTypes, e.g. into an <xsd:element>??
    That would be changing the customer's structure which I think is not a good thing!?
    Thank you again for your help! I really appreciate it!
    Best regards,
    Peter

  • External Definition (wsdl) with abstract xsd element

    Hello All,
    we are trying to call a webservice, here is the wsdl:
    https://www.1link.com/fr/demo-sn/site/gaiwebservice.asmx?WSDL
    the problem is that the GAIJobLine element is defined as abstract:
    <s:complexType name="GAIJobLine" abstract="true">
    and there several elements which are extending GAIJobLine, for example:
    <s:complexType name="GAITyreLine">
                        <s:complexContent mixed="false">
                             <s:extension base="tns:GAIJobLine">
    So in our mapping we need to map to those element which are extending base element and not to the abstract one, but Graphical mapping displays only GAIJobLIne base element.
    Does anybody know how we can map to extended elements without mannually changing wsdl?
    Best Regards,
    Artsiom Anichenka

    thanks for your reply!
    the extended elements are seen when I open wsdl in XMLSpy.
    they are also visible in external definition object, but the main problem is that in the mapping only the base lement is displayed and there is no possobility to choose the extension.
    Maybe this kind os XSDs (with abstract base types and extended elements) are just not supported by PI711?

  • Unable to see Messages in External Definitions

    I imported the WSDL below and created a Message Interface based on JobSubmitRequest but, when I come to map to it, all I see in the tree structure is node 'JobSubmitRequest' with elements 'parameter' and 'request_header'.
    I also cannot see any messages in External Definitions.
    Can anyone help with a solution?
    <?xml version="1.0" encoding="UTF-8"?>
    <definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xoa="http://xoa.xpedite.com/2004/11/xoa" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://xoa.xpedite.com/2004/11/xoa">
         <types>
              <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://xoa.xpedite.com/2004/11/xoa" xmlns="http://xoa.xpedite.com/2004/11/xoa">
                   <!-- address type enum -->
                   <xs:simpleType name="AddressType">
                        <xs:restriction base="xs:string">
                             <xs:enumeration value="fax"/>
                             <xs:enumeration value="internet"/>
                             <xs:enumeration value="mbox"/>
                             <xs:enumeration value="x400"/>
                             <xs:enumeration value="telex"/>
                             <xs:enumeration value="cablegram"/>
                             <xs:enumeration value="mailgram"/>
                             <xs:enumeration value="ddd"/>
                             <xs:enumeration value="dedLine"/>
                             <xs:enumeration value="softswitch"/>
                             <xs:enumeration value="voice"/>
                             <xs:enumeration value="sms"/>
                             <xs:enumeration value="fod"/>
                             <xs:enumeration value="list"/>
                             <xs:enumeration value="smQuery"/>
                        </xs:restriction>
                   </xs:simpleType>
                   <!--includes for standalone validation
         <xs:include schemaLocation="StatusType.xsd"/>
         ================ -->
                   <xs:element name="AuthenticateRequest">
                        <xs:complexType>
                             <xs:sequence>
                                  <xs:element minOccurs="0" name="Domain" type="xs:string"/>
                             </xs:sequence>
                        </xs:complexType>
                   </xs:element>
                   <!-- The authenticate result (used to send back results for synchronous and asynchronous requests) -->
                   <xs:element name="AuthenticateResult">
                        <xs:complexType>
                             <xs:sequence>
                                  <xs:element name="Status" type="xoa:StatusType"/>
                             </xs:sequence>
                        </xs:complexType>
                   </xs:element>
                   <!-- includes for standalone validation
         <xs:include schemaLocation="StatusType.xsd"/>
         ================ -->
                   <xs:element name="CFSCreateDirRequest">
                        <xs:complexType>
                             <xs:sequence>
                                  <xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
                                  <xs:element name="RelativePath" type="xs:string"/>
                             </xs:sequence>
                        </xs:complexType>
                   </xs:element>
                   <xs:element name="CFSCreateDirResult">
                        <xs:complexType>
                             <xs:sequence>
                                  <xs:element name="Status" type="xoa:StatusType"/>
                                  <xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
                                  <xs:element minOccurs="0" name="RelativePath" type="xs:string"/>
                             </xs:sequence>
                        </xs:complexType>
                   </xs:element>
                   <!-- includes for standalone validation
         <xs:include schemaLocation="StatusType.xsd"/>
         ================ -->
                   <xs:element name="CFSDeleteRequest">
                        <xs:complexType>
                             <xs:sequence>
                                  <xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
                                  <xs:element name="RelativePath" type="xs:string"/>
                                  <xs:element minOccurs="0" name="DeleteDir" type="xs:boolean"/>
                             </xs:sequence>
                        </xs:complexType>
                   </xs:element>
                   <xs:element name="CFSDeleteResult">
                        <xs:complexType>
                             <xs:sequence>
                                  <xs:element name="Status" type="xoa:StatusType"/>
                                  <xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
                                  <xs:element minOccurs="0" name="RelativePath" type="xs:string"/>
                             </xs:sequence>
                        </xs:complexType>
                   </xs:element>
                   <!-- includes for standalone validation
         <xs:include schemaLocation="OwnershipLevelType.xsd"/>
         <xs:include schemaLocation="StatusType.xsd"/>
         <xs:include schemaLocation="Document.xsd"/>
         ================ -->
                   <xs:element name="CFSDownloadRequest">
                        <xs:complexType>
                             <xs:sequence>
                                  <xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
                                  <xs:element name="RelativePath" type="xs:string"/>
                             </xs:sequence>
                        </xs:complexType>
                   </xs:element>
                   <xs:element name="CFSDownloadResult">
                        <xs:complexType>
                             <xs:sequence>
                                  <xs:element name="Status" type="xoa:StatusType"/>
                                  <xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
                                  <xs:element minOccurs="0" name="RelativePath" type="xs:string"/>
                                  <xs:element minOccurs="0" name="FileData" type="xoa:DocDataType"/>
                             </xs:sequence>
                        </xs:complexType>
                   </xs:element>
                   <!-- includes for standalone validation
         <xs:include schemaLocation="OwnershipLevelType.xsd"/>
         <xs:include schemaLocation="StatusType.xsd"/>
         <xs:include schemaLocation="Document.xsd"/>
         ================ -->
                   <xs:element name="CFSListRequest">
                        <xs:complexType>
                             <xs:sequence>
                                  <xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
                                  <xs:element name="RelativePath" type="xs:string"/>
                                  <xs:element minOccurs="0" name="IncludeSubDir" type="xs:boolean"/>
                             </xs:sequence>
                        </xs:complexType>
                   </xs:element>
                   <xs:simpleType name="EntryType">
                        <xs:restriction base="xs:string">
                             <xs:enumeration value="file"/>
                             <xs:enumeration value="directory"/>
                        </xs:restriction>
                   </xs:simpleType>
                   <xs:element name="CFSListResult">
                        <xs:complexType>
                             <xs:sequence>
                                  <xs:element name="Status" type="xoa:StatusType"/>
                                  <xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
                                  <xs:element minOccurs="0" name="RelativePath" type="xs:string"/>
                                  <xs:element maxOccurs="unbounded" minOccurs="0" name="DirectoryEntry" type="xoa:DirectoryEntryType">
                                       <xs:annotation>
                                            <xs:documentation>content of
                                        DirectoryEntry is path relative to
                                        the RelativePath</xs:documentation>
                                       </xs:annotation>
                                  </xs:element>
                             </xs:sequence>
                        </xs:complexType>
                   </xs:element>
                   <xs:complexType name="DirectoryEntryType">
                        <xs:simpleContent>
                             <xs:extension base="xs:string">
                                  <xs:attribute name="type" type="xoa:EntryType" use="required"/>
                                  <xs:attribute name="modified" type="xs:dateTime" use="optional"/>
                                  <xs:attribute name="size" type="xs:integer" use="optional"/>
                             </xs:extension>
                        </xs:simpleContent>
                   </xs:complexType>
                   <!-- includes for standalone validation
         <xs:include schemaLocation="StatusType.xsd"/>
         ================ -->
                   <xs:element name="CFSRenameRequest">
                        <xs:complexType>
                             <xs:sequence>
                                  <xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
                                  <xs:element name="OldRelativePath" type="xs:string"/>
                                  <xs:element name="NewRelativePath" type="xs:string"/>
                             </xs:sequence>
                        </xs:complexType>
                   </xs:element>
                   <xs:element name="CFSRenameResult">
                        <xs:complexType>
                             <xs:sequence>
                                  <xs:element name="Status" type="xoa:StatusType"/>
                                  <xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
                                  <xs:element minOccurs="0" name="OldRelativePath" type="xs:string"/>
                                  <xs:element minOccurs="0" name="NewRelativePath" type="xs:string"/>
                             </xs:sequence>
                        </xs:complexType>
                   </xs:element>
                   <!-- includes for standalone validation
         <xs:include schemaLocation="OwnershipLevelType.xsd"/>
         <xs:include schemaLocation="StatusType.xsd"/>
         <xs:include schemaLocation="Document.xsd"/>
         ================ -->
                   <xs:element name="CFSUploadRequest">
                        <xs:complexType>
                             <xs:sequence>
                                  <xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
                                  <xs:element name="RelativePath" type="xs:string"/>
                                  <xs:element name="FileData" type="xoa:DocDataType"/>
                             </xs:sequence>
                        </xs:complexType>
                   </xs:element>
                   <xs:element name="CFSUploadResult">
                        <xs:complexType>
                             <xs:sequence>
                                  <xs:element name="Status" type="xoa:StatusType"/>
                                  <xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
                                  <xs:element minOccurs="0" name="RelativePath" type="xs:string"/>
                             </xs:sequence>
                        </xs:complexType>
                   </xs:element>
                   <!-- ===============================
         <xs:include schemaLocation="AddressType.xsd"/>
         <xs:include schemaLocation="Document.xsd"/>
         <xs:include schemaLocation="EncodableStringType.xsd"/>
         <xs:include schemaLocation="OwnershipLevelType.xsd"/>
         <xs:include schemaLocation="StatusType.xsd"/>
         =============================== -->
                   <!-- Type definitions -->
                   <!-- Phone element -->
                   <xs:element name="Phone">
                        <xs:simpleType>
                             <xs:restriction base="xs:string">
                                  <!-- <xs:pattern value="[0-9+x\-() ]{5,20}"/> -->
                             </xs:restriction>
                        </xs:simpleType>
                   </xs:element>
                   <!-- Email element -->
                   <xs:element name="Email">
                        <xs:simpleType>
                             <xs:restriction base="xs:string">
                                  <xs:minLength value="2"/>
                                  <!-- <xs:pattern value="[@]{1,64}@([@\.]{1,64}\.){1,10}[^@\.]{1,64}"/> -->
                             </xs:restriction>
                        </xs:simpleType>
                   </xs:element>
                   <!-- Eformat type -->
                   <xs:simpleType name="EformatType">
                        <xs:annotation>
                             <xs:documentation>      Only used in messageREACH.
                            Indicates the preferred email      format of the
                            message body the recipient will      receive.
                            Leaving the field empty or setting it to
                            "default" will send a multipart message body
                            rather than      just a single message body if
                            it would do so normally.   </xs:documentation>
                        </xs:annotation>
                        <xs:restriction base="xs:string">
                             <xs:enumeration value="text"/>
                             <xs:enumeration value="html"/>
                             <xs:enumeration value="htmllite"/>
                             <xs:enumeration value="default"/>
                        </xs:restriction>
                   </xs:simpleType>
                   <!-- insert list element -->
                   <xs:element name="InsertList">
                        <xs:complexType>
                             <xs:choice>
                                  <xs:element maxOccurs="unbounded" name="Insert">
                                       <xs:complexType>
                                            <xs:simpleContent>
                                                 <xs:extension base="xs:string">
                                                      <xs:attribute name="number" type="xs:integer"/>
                                                      <xs:attribute name="b64charset" type="xs:string" use="optional"/>
                                                 </xs:extension>
                                            </xs:simpleContent>
                                       </xs:complexType>
                                  </xs:element>
                             </xs:choice>
                        </xs:complexType>
                   </xs:element>
                   <!-- extension element -->
                   <xs:complexType name="SegmentType">
                        <xs:choice>
                             <xs:element maxOccurs="unbounded" name="Property">
                                  <xs:complexType>
                                       <xs:simpleContent>
                                            <xs:extension base="xs:string">
                                                 <xs:attribute name="name" type="xs:string"/>
                                                 <xs:attribute name="b64charset" type="xs:string" use="optional"/>
                                            </xs:extension>
                                       </xs:simpleContent>
                                  </xs:complexType>
                             </xs:element>
                        </xs:choice>
                        <xs:attribute name="name" type="xs:string"/>
                   </xs:complexType>
                   <xs:element name="Extension">
                        <xs:complexType>
                             <xs:choice maxOccurs="unbounded">
                                  <xs:element name="Segment" type="xoa:SegmentType"/>
                             </xs:choice>
                        </xs:complexType>
                   </xs:element>
                   <!-- field mapping type -->
                   <xs:complexType name="FieldMappingType">
                        <xs:annotation>
                             <xs:documentation>      Describes the correspondence
                            between the segment/keyword      pairs in the
                            XDDS header file and columns in a table. Only
                            two table formats currently supported: CSV
                            (comma-separated values) and XSL (Excel
                            spreadsheet).       The mapping may go either
                            from field name to the      segment/keyword pair
                            or vice versa. In both cases, the      same
                            structure may be used.   </xs:documentation>
                        </xs:annotation>
                        <xs:sequence>
                             <xs:element maxOccurs="unbounded" name="Map">
                                  <xs:complexType>
                                       <xs:sequence>
                                            <xs:element name="FieldName" type="xs:string"/>
                                            <xs:element minOccurs="0" name="SegmentName" type="xs:string"/>
                                            <xs:element name="PropertyName" type="xs:string"/>
                                            <xs:element minOccurs="0" name="IsBase64Encoded" type="xs:boolean"/>
                                       </xs:sequence>
                                  </xs:complexType>
                             </xs:element>
                        </xs:sequence>
                   </xs:complexType>
                   <!-- class definitions -->
                   <!-- delivery item base class -->
                   <xs:element abstract="true" name="DeliveryItem" type="xoa:DeliveryItemType"/>
                   <xs:complexType abstract="true" name="DeliveryItemType">
                        <xs:attribute name="ref" type="xs:string" use="optional"/>
                        <xs:attribute name="refb64" type="xs:string" use="optional"/>
                   </xs:complexType>
                   <!-- new branch -->
                   <!-- delivery item container class -->
                   <xs:element abstract="true" name="DeliveryItemContainer" type="xoa:DeliveryItemContainerType"/>
                   <xs:complexType abstract="true" name="DeliveryItemContainerType">
                        <xs:complexContent>
                             <xs:extension base="xoa:DeliveryItemType"/>
                        </xs:complexContent>
                   </xs:complexType>
                   <!-- list delivery item class -->
                   <xs:element name="List" type="xoa:ListType"/>
                   <xs:complexType name="ListType">
                        <xs:complexContent>
                             <xs:extension base="xoa:DeliveryItemContainerType">
                                  <xs:sequence>
                                       <xs:element name="Name" type="xs:string"/>
                                  </xs:sequence>
                                  <xs:attribute name="ownershipLevel" type="xoa:OwnershipLevelType"/>
                             </xs:extension>
                        </xs:complexContent>
                   </xs:complexType>
                   <!-- SmQuery delivery item class -->
                   <xs:element name="SmQuery" type="xoa:SmQueryType"/>
                   <xs:complexType name="SmQueryType">
                        <xs:complexContent>
                             <xs:extension base="xoa:DeliveryItemContainerType">
                                  <xs:sequence>
                                       <xs:element name="Name" type="xs:string"/>
                                  </xs:sequence>
                                  <xs:attribute name="ownershipLevel" type="xoa:OwnershipLevelType"/>
                             </xs:extension>
                        </xs:complexContent>
                   </xs:complexType>
                   <!-- External table delivery item class -->
                   <!-- This includes CSV and XLS files -->
                   <xs:element name="Table" type="xoa:TableType"/>
                   <xs:complexType name="TableType">
                        <xs:complexContent>
                             <xs:extension base="xoa:DeliveryItemContainerType">
                                  <xs:sequence>
                                       <xs:element minOccurs="0" name="FieldMapping" type="xoa:FieldMappingType"/>
                                       <xs:choice>
                                            <xs:element name="DocRef" type="xs:string"/>
                                            <xs:element name="Document" type="xoa:DocumentType"/>
                                       </xs:choice>
                                  </xs:sequence>
                             </xs:extension>
                        </xs:complexContent>
                   </xs:complexType>
                   <!-- new branch -->
                   <!-- delivery item simple class -->
                   <xs:element abstract="true" name="DeliveryItemSimple" type="xoa:DeliveryItemSimpleType"/>
                   <xs:complexType abstract="true" name="DeliveryItemSimpleType">
                        <xs:complexContent>
                             <xs:extension base="xoa:DeliveryItemType">
                                  <xs:sequence>
                                       <xs:element minOccurs="0" name="Alternate">
                                            <xs:complexType>
                                                 <xs:choice>
                                                      <xs:element ref="xoa:Fax"/>
                                                      <xs:element ref="xoa:Internet"/>
                                                      <xs:element ref="xoa:Voice"/>
                                                      <xs:element ref="xoa:Fod"/>
                                                      <xs:element ref="xoa:Mbox"/>
                                                      <xs:element ref="xoa:Sms"/>
                                                      <xs:element ref="xoa:Telex"/>
                                                      <xs:element ref="xoa:DeliveryItemGeneric"/>
                                                 </xs:choice>
                                            </xs:complexType>
                                       </xs:element>
                                  </xs:sequence>
                             </xs:extension>
                        </xs:complexContent>
                   </xs:complexType>
                   <!-- mbox delivery item class -->
                   <xs:element name="Mbox" type="xoa:MboxType"/>
                   <xs:complexType name="MboxType">
                        <xs:complexContent>
                             <xs:extension base="xoa:DeliveryItemSimpleType">
                                  <xs:sequence>
                                       <xs:element name="UserId" type="xs:string"/>
                                  </xs:sequence>
                             </xs:extension>
                        </xs:complexContent>
                   </xs:complexType>
                   <!-- telex delivery item class -->
                   <xs:element name="Telex" type="xoa:TelexType"/>
                   <xs:complexType name="TelexType">
                        <xs:complexContent>
                             <xs:extension base="xoa:DeliveryItemSimpleType">
                                  <xs:sequence>
                                       <xs:element name="Number" type="xs:string"/>
                                  </xs:sequence>
                             </xs:extension>
                        </xs:complexContent>
                   </xs:complexType>
                   <!-- FOD delivery item class -->
                   <xs:element name="Fod" type="xoa:FodType"/>
                   <xs:complexType name="FodType">
                        <xs:complexContent>
                             <xs:extension base="xoa:DeliveryItemSimpleType">
                                  <xs:sequence>
                                       <xs:element name="Address" type="xs:string"/>
                                  </xs:sequence>
                             </xs:extension>
                        </xs:complexContent>
                   </xs:complexType>
                   <!-- SMS delivery item class -->
                   <xs:element name="Sms" type="xoa:SmsType"/>
                   <xs:complexType name="SmsType">
                        <xs:complexContent>
                             <xs:extension base="xoa:DeliveryItemSimpleType">
                                  <xs:sequence>
                                       <xs:element ref="xoa:Phone"/>
                                  </xs:sequence>
                             </xs:extension>
                        </xs:complexContent>
                   </xs:complexType>
                   <!-- new branch -->
                   <!-- Complex delivery item class -->
                   <xs:element abstract="true" name="DeliveryItemComplex" type="xoa:DeliveryItemComplexType"/>
                   <xs:complexType abstract="true" name="DeliveryItemComplexType">
                        <xs:complexContent>
                             <xs:extension base="xoa:DeliveryItemSimpleType">
                                  <xs:sequence>
                                       <xs:element minOccurs="0" ref="xoa:InsertList"/>
                                       <xs:element minOccurs="0" ref="xoa:Extension"/>
                                  </xs:sequence>
                             </xs:extension>
                        </xs:complexContent>
                   </xs:complexType>
                   <!-- fax delivery item class -->
                   <xs:element name="Fax" type="xoa:FaxType"/>
                   <xs:complexType name="FaxType">
                        <xs:complexContent>
                             <xs:extension base="xoa:DeliveryItemComplexType">
                                  <xs:sequence>
                                       <xs:element ref="xoa:Phone"/>
                                       <xs:element minOccurs="0" name="Att" type="xoa:EncodableStringType"/>
                                       <xs:element minOccurs="0" name="From" type="xoa:EncodableStringType"/>
                                       <xs:element minOccurs="0" name="To" type="xoa:EncodableStringType"/>
                                       <xs:element minOccurs="0" name="Salutation" type="xs:string"/>
                                  </xs:sequence>
                             </xs:extension>
                        </xs:complexContent>
                   </xs:complexType>
                   <!-- voice delivery item class -->
                   <xs:element name="Voice" type="xoa:VoiceType"/>
                   <xs:complexType name="VoiceType">
                        <xs:complexContent>
                             <xs:extension base="xoa:DeliveryItemComplexType">
                                  <xs:sequence>
                                       <xs:element ref="xoa:Phone"/>
                                  </xs:sequence>
                             </xs:extension>
                        </xs:complexContent>
                   </xs:complexType>
                   <!-- internet delivery item class -->
                   <xs:element name="Internet" type="xoa:InternetType"/>
                   <xs:complexType name="InternetType">
                        <xs:complexContent>
                             <xs:extension base="xoa:DeliveryItemComplexType">
                                  <xs:sequence>
                                       <xs:element ref="xoa:Email"/>
                                       <xs:element minOccurs="0" name="Subject" type="xoa:EncodableStringType"/>
                                       <xs:element minOccurs="0" name="From" type="xoa:EncodableStringType"/>
                                       <xs:element minOccurs="0" name="Eformat" type="xoa:EformatType"/>
                                       <xs:element minOccurs="0" name="Password" type="xs:string">
                                            <xs:annotation>
                                                 <xs:documentation>    Only used in
                                        messageREACH. The password used
                                        by this recipient to retrieve
                                        pull    attachments.        </xs:documentation>
                                            </xs:annotation>
                                       </xs:element>
                                  </xs:sequence>
                             </xs:extension>
                        </xs:complexContent>
                   </xs:complexType>
                   <!-- fax delivery item class -->
                   <xs:element name="DeliveryItemGeneric" type="xoa:DeliveryItemGenericType"/>
                   <xs:complexType name="DeliveryItemGenericType">
                        <xs:complexContent>
                             <xs:extension base="xoa:DeliveryItemComplexType">
                                  <xs:sequence>
                                       <xs:element name="Address" type="xs:string"/>
                                  </xs:sequence>
                                  <xs:attribute name="type" type="xoa:AddressType" use="required"/>
                             </xs:extension>
                        </xs:complexContent>
                   </xs:complexType>
                   <!-- Finally, delivery item list -->
                   <!-- delivery item list type -->
                   <xs:complexType name="DeliveryItemListType">
                        <xs:choice maxOccurs="unbounded">
                             <xs:element ref="xoa:List"/>
                             <xs:element ref="xoa:SmQuery"/>
                             <xs:element ref="xoa:Table"/>
                             <xs:element ref="xoa:DeliveryItemGeneric"/>
                             <xs:element ref="xoa:Fax"/>
                             <xs:element ref="xoa:Internet"/>
                             <xs:element ref="xoa:Voice"/>
                             <xs:element ref="xoa:Fod"/>
                             <xs:element ref="xoa:Mbox"/>
                             <xs:element ref="xoa:Sms"/>
                             <xs:element ref="xoa:Telex"/>
                        </xs:choice>
                   </xs:complexType>
                   <!--remove includes later
         <xs:include schemaLocation="AddressType.xsd"/>
         ================ -->
                   <xs:complexType name="DestinationType">
                        <xs:simpleContent>
                             <xs:extension base="xs:string">
                                  <xs:attribute name="type" type="xoa:AddressType"/>
                             </xs:extension>
                        </xs:simpleContent>
                   </xs:complexType>
                   <!-- ===============================
         <xs:include schemaLocation="OwnershipLevelType.xsd"/>
         =============================== -->
                   <!-- Elementary definitions go first -->
                   <xs:element name="CharacterSet" type="xs:string">
                        <xs:annotation>
                             <xs:documentation>use ISO names</xs:documentation>
                        </xs:annotation>
                   </xs:element>
                   <!-- Document type -->
                   <xs:simpleType name="DocFormatType">
                        <xs:restriction base="xs:string">
                             <xs:enumeration value="text"/>
                             <xs:enumeration value="XMF"/>
                             <xs:enumeration value="TIFF"/>
                             <xs:enumeration value="XAR"/>
                             <xs:enumeration value="PS"/>
                             <xs:enumeration value="PCL"/>
                             <xs:enumeration value="PDF"/>
                             <xs:enumeration value="MSW"/>
                             <xs:enumeration value="WAV"/>
                             <xs:enumeration value="RTF"/>
                             <xs:enumeration value="XLS"/>
                             <xs:enumeration value="HTML"/>
                             <xs:enumeration value="HTMLLITE"/>
                             <xs:enumeration value="unspec"/>
                             <xs:enumeration value="GIF"/>
                             <xs:enumeration value="JPEG"/>
                             <xs:enumeration value="PPT"/>
                             <xs:enumeration value="BMP"/>
                             <xs:enumeration value="VSD"/>
                             <xs:enumeration value="PUB"/>
                             <xs:enumeration value="MPP"/>
                             <xs:enumeration value="empty"/>
                             <!-- We do not need to know the document type for the -->
                             <!-- email attachments. -->
                        </xs:restriction>
                   </xs:simpleType>
                   <!-- Document Encoding format -->
                   <xs:simpleType name="DocEncodingFormat">
                        <xs:restriction base="xs:string">
                             <xs:enumeration value="text"/>
                             <xs:enumeration value="base64"/>
                        </xs:restriction>
                   </xs:simpleType>
                   <!-- Document embedded into the request -->
                   <xs:complexType name="DocDataType">
                        <xs:simpleContent>
                             <xs:extension base="xs:string">
                                  <xs:attribute name="format" type="xoa:DocEncodingFormat" use="required"/>
                             </xs:extension>
                        </xs:simpleContent>
                   </xs:complexType>
                   <!-- All supported stored object types -->
                   <xs:simpleType name="SosObjectType">
                        <xs:restriction base="xs:string">
                             <xs:enumeration value="tts"/>
                             <xs:enumeration value="vcs"/>
                        </xs:restriction>
                   </xs:simpleType>
                   <!-- The types of the sos stored objects -->
                   <xs:complexType name="SosObjectIdType">
                        <xs:simpleContent>
                             <xs:extension base="xs:string">
                                  <xs:attribute name="sosType" type="xoa:SosObjectType" use="required"/>
                                  <xs:attribute name="ownershipLevel" type="xoa:OwnershipLevelType"/>
                             </xs:extension>
                        </xs:simpleContent>
                   </xs:complexType>
                   <!-- Another Document type -->
                   <xs:complexType name="DocumentType">
                        <xs:sequence>
                             <xs:element name="DocType" type="xoa:DocFormatType"/>
                             <xs:element minOccurs="0" name="Filename" type="xs:string"/>
                             <xs:choice>
                                  <xs:element name="DocData" type="xoa:DocDataType"/>
                                  <xs:element name="DocCfs" type="xs:string"/>
                                  <xs:element name="DocUrl" type="xs:anyURI"/>
                                  <xs:element name="SosObject" type="xoa:SosObjectIdType"/>
                             </xs:choice>
                             <xs:element minOccurs="0" ref="xoa:CharacterSet"/>
                        </xs:sequence>
                        <xs:attribute name="ref" type="xs:string" use="optional"/>
                   </xs:complexType>
                   <!-- The document set type -->
                   <xs:complexType name="DocumentSetType">
                        <xs:sequence>
                             <xs:element maxOccurs="unbounded" minOccurs="0" name="Document" type="xoa:DocumentType"/>
                        </xs:sequence>
                   </xs:complexType>
                   <!-- The document by value or by reference -->
                   <xs:complexType name="DocumentOrRefType">
                        <xs:choice>
                             <xs:element name="DocRef" type="xs:string">
                                  <xs:annotation>
                                       <xs:documentation>must refer to a document
                                    in document_set</xs:documentation>
                                  </xs:annotation>
                             </xs:element>
                             <xs:element name="Document" type="xoa:DocumentType"/>
                        </xs:choice>
                   </xs:complexType>
                   <xs:complexType name="EncodableStringType">
                        <xs:simpleContent>
                             <xs:extension base="xs:string">
                                  <xs:attribute name="b64charset" type="xs:string" use="optional"/>
                             </xs:extension>
                        </xs:simpleContent>
                   </xs:complexType>
                   <!--includes for standalone validation
         ================ -->
                   <xs:simpleType name="HistoryActionType">
                        <xs:restriction base="xs:string">
                             <xs:enumeration value="inserted"/>
                             <xs:enumeration value="updated"/>
                             <xs:enumeration value="deleted"/>
                        </xs:restriction>
                   </xs:simpleType>
                   <xs:complexType name="ItemCountType">
                        <xs:simpleContent>
                             <xs:extension base="xs:integer">
                                  <xs:attribute name="type" type="xoa:HistoryActionType"/>
                             </xs:extension>
                        </xs:simpleContent>
                   </xs:complexType>
                   <xs:complexType name="HistoryType">
                        <xs:sequence>
                             <xs:element name="Action" type="xs:string"/>
                             <xs:element name="Operator" type="xs:string"/>
                             <xs:element name="Agent" type="xs:string"/>
                             <xs:element name="Time" type="xs:dateTime"/>
                             <xs:element name="ItemCount" type="xoa:ItemCountType"/>
                        </xs:sequence>
                   </xs:complexType>
                   <!-- ================
         <xs:include schemaLocation="AddressType.xsd"/>
         <xs:include schemaLocation="DestinationType.xsd"/>
         <xs:include schemaLocation="Document.xsd"/>
         <xs:include schemaLocation="JobIdType.xsd"/>
         <xs:include schemaLocation="OwnershipLevelType.xsd"/>
         <xs:include schemaLocation="StatusType.xsd"/>
         <xs:include schemaLocation="RecStatusType.xsd"/>
         ================ -->
                   <xs:simpleType name="JobCancelType">
                        <xs:annotation>
                             <xs:documentation>The set of cancellation types/options</xs:documentation>
                        </xs:annotation>
                        <xs:restriction base="xs:string">
                             <xs:enumeration value="All"/>
                             <xs:enumeration value="Deliveries"/>
                             <xs:enumeration value="Reports"/>
                             <xs:enumeration value="AcceptanceReport"/>
                             <xs:enumeration value="CancellationNotice"/>
                             <xs:enumeration value="Pulls"/>
                             <xs:enumeration value="FriendDeliveries"/>
                        </xs:restriction>
                   </xs:simpleType>
                   <xs:complexType name="JobCancelItemType">
                        <xs:sequence>
                             <xs:element name="JobId" type="xoa:JobIdType">
                                  <xs:annotation>
                                       <xs:documentation>requested JobId</xs:documentation>
                                  </xs:annotation>
                             </xs:element>
                             <xs:element minOccurs="0" name="CancelType" type="xoa:JobCancelType"/>
                             <xs:element minOccurs="0" name="NotificationAddress" type="xoa:DestinationType"/>
                             <xs:choice minOccurs="0">
                                  <xs:element name="NotificationType" type="xs:string"/>
                                  <xs:element name="NotificationText" type="xoa:DocDataType"/>
                             </xs:choice>
                        </xs:sequence>
                   </xs:complexType>
                   &

    Hi,
    Not all data types from WSDL are supported during import. There is SAP Note about it.
    please read it:
    /people/kevin.liu/blog/2005/10/07/a-note-on-wsdl-and-xsd-imports--part-ii
    regards,
    wojtek
    Message was edited by: Wojciech Gasiorowski

  • DTD files as external Definition

    Hi ,
    Read lot of threads on this which are having same problem ,some of them got solved none of them posted how did they succeded on those.
    i am getting error like Name "ds:Signature" is incorrect, when i tried to inport the .dtd file as external definition,so I did try converting dtd file to XSD ,it is creating the 3 xsd files and none of them are valid each one of them are error.But however the DTD file is valid .
    Using Invoicedetail DTD file for my scenario.
    you can download the file from http://cxml.org
    Please let me knw on this.
    Thanks,
    Madhu

    Hi,
    Here are the errors for the 3 xsd's
    1.     Value 'ds:Signature' is not allowed for attribute 'ref'.
              Hint: A valid value would be 'xml:lang'.
              Error location: xs:schema / xs:element / xs:complexType / xs:sequence / xs:element / @ref
    2.     Value 'ds:Signature' is not allowed for attribute 'ref'.
              Hint: A valid value would be 'xml:lang'.
              Error location: xs:schema / xs:element / xs:complexType / xs:sequence / xs:element / @ref
    3.                   Value 'xades:Identifier' is not allowed for attribute 'ref'.
              Hint: A valid value would be 'xml:lang'.
              Error location: xs:schema / xs:element / xs:complexType / xs:sequence / xs:element / @ref
    these errors are coming in xml spy when i tried to validate .
    Thanks,
    Madhu
    Edited by: madhu204 on Jul 23, 2009 4:54 PM
    Edited by: madhu204 on Jul 23, 2009 4:55 PM

  • External definitions import into Message mapping

    Hi,
    I have a DTD message in external definitions to be imported into the message mapping. But I am not able to choose the object in the mapping editor. It does not allow even if the message is a valid WSDL. The only time it allows to import into the message editor is when its an XSD.I am not sure why the external definitions in DTD or WSDL formats are not able to be imported or am I missing something??
    -Ken

    Hi,
      A conversion of the downloaded cXML DTD into XSD by using XMLSPY yields 3 XSD files. Using the initial XSD(which has the major fields) yields the same error(i.e cannot create messages or valid WSDL) in external definitions.
    I also tried using one of the standard xml's from the cXML site and the funny part was XMLSPY validated them without errors and while importing them directly into the mapping editor, XI throws an error "XML NOT WELL FORMED". Its so weird.
      Also is there a possibility to write a script to manipulate the payload message after passing through the adapters? For eg : Creating a script which will delete a valid tag in payload before it reaches the 3rd party. ...By adding the DOCTYPE in the prolog, the message would look like this :
    "<?xml...utf-8>
    <!DOCTYPE......'Cxml.org'>
    <?xml.....utf-8>
    <start tag></start tag>”
    Therefore some kind of a script that would remove the second <?xml tag on line 3>..
    This is just a round about thinking…
    Any ideas..

  • How to remove namespaces in mapping when using External Definition

    Hi,
    I read in the blog (/people/sameer.shadab/blog/2005/12/05/how-to-remove-namespaces-in-mapping--xi) that you are able to remove namespaces in mapping by deleting the value from XML Namespace under the Message Type. However, is it possible to do this when you are using External Definition (xsd) ? The blog only describe how to do this if you define a Data Type.

    Hi ,
    No ..it is not possible to remove the namespace once you imported into IR of external defintion.You can remove your namesapce from external definition before importing into IR.
    Sekhar

  • Multi-Mapping Error in PI 7.1 - External Definitions

    Hi all,
    We have just upgraded to PI 7.1 from 7.0 and run into an issue with message multi-mappings, just wondered if anyone else had met the same issue and worked it out...
    When creating a message mapping, we are using as the target an external definition which is defined by an XSD generated by a third party tool (Seeburger).
    When I map 1:1 (1 source message to one target message) in the message mapper, all is fine but if I try to create a multi mapping, I get an error. The process is:
    a) I have a message mapping with one target message, defined as an External Definition.
    b) I then go to Signature tab and add a second target message as an External Definition
    c) Click back to Definition tab
    d) Get the error "Object XXXXX | YYYYY not found" - where XXXXX is the external def name and YYYYY is the namespace (the SWCV namespace that is, not the XML namespace)
    This only seems to happen with External Definitions which are autogenerated and I strongly suspect that is has to do with the fact that the tool that generates them always  does so without an XML namespace. I have not proved this though (other Ext Defs with namespaces work for multi-mappings but that is not the only difference so I can't be sure that is the issue but have a strong hunch. This problem did not occur in 7.0.
    Anyone got any ideas?
    Thanks,
    Chris

    Hi,
    This would not be of much help but, I was able to encounter this issue in XI 3.0.
    What we did was to manually edit the XSD and add a namespace to it. I'm not sure if PI 7.1 is able to handle mutiple namespaces, so we limited it to this value <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified"> and made sure that this value is used for all the External Definitions used in the multi-mapping.
    Regards,

Maybe you are looking for