|
Follow-on questions should really go to the list
rather than individuals. (The individual you ask may not be able to
answer the question, or they might not have time to look into it, which puts
them in a difficult position. Also, others on the list like to know
what has been exchanged - sometimes!)
In this case, if you make the suggested changes
(when you get them!) the elements should be members of input and
output.
BTW - you should consider making aliasLookUpType a global type at the top level
(i.e. not nested within another element declaration). e.g. straight after
the xs:schema start tag do:
<xs:complexType
name="aliasLookUpType">
<xs:sequence>
<xs:element name="name_last_lookup"
type="xs:string"/>
<xs:element name="id_ssn_lookup"
type="xs:string"/>
<xs:element name="arrestee_dob_lookup"
type="xs:date"/>
</xs:sequence>
</xs:complexType>
and where you want the elements,
do:
<xs:element
name="aliasLookUpType" type="aliasLookUpType"/>
HTH,
----- Original Message -----
Sent: Tuesday, February 05, 2008 7:49
PM
Subject: Re: [xml-dev] xs:complexType
node element invalid inside another complexType?
hi
Is it possible to redesign this new element so that it is part of the
<xs:element name="input"> and
<xs:element name="output"> respectively.
thanks
ilango
Pete Cordell <petexmldev@codalogic.com>
wrote:
Hi,
The
boldness seems to have been lost so it's not clear which is the element
in question. Also, what error messages are you getting?
If it's
the bit you've commented out, then the correct XML schema for that
is
something like:
i.e.
your defining an element that is a complexType, not a complexType on
its
own.
HTH,
Pete Cordell
Codalogic
Visit
http://www.codalogic.com/lmx/ for XML C++ data binding
----- Original
Message -----
From: "XGuy"
To:
<XML-DEV@LISTS.XML.ORG>
Sent: Tuesday, February 05, 2008 5:30
PM
Subject: [xml-dev] xs:complexType node element invalid inside another
complexType?
>
> Hi
> I have the following
schema. Recently I have introduced a new element (the
> one shown in
bold) and I am getting errors. I am not sure how or where to
>
introduce this element. I am trying to model a "repeat-structure" in
an
> XForm that is composed of elements "name_last_lookup" (or
"name_list" is
> preferred because it is already there),
"id_ssn_lookup" (id_ssn is
> preferred
> because it is already
defined), "arrestee_dob_lookup" (arrestee_dob" is
> preferred because
it is already defined).
>
> Why are these errors being
generated? How would I design this new element
> to
> avoid any
errors?
>
>
> --------
>
>
> >
xmlns:fe="http://www.i.com/bpms/workflow/xforms/MyForms/CComplaint"
>
>
xmlns:CreateComplaint="http://www.i.com/bpms/workflow/xforms/MyForms/CComplaint"
>
targetNamespace="http://www.i.com/bpms/workflow/xforms/MyForms/CComplaint"
>
elementFormDefault="qualified">
| 
