How can I put two multiple-occurring elements that both have the same parent element into one view? For example, I need to put all the elements of EMPLOYEE in one view:

<!ELEMENT EMPLOYEE (EID, EMAIL+, PHONE+)>

Create an EMPLOYEE view.

Add the EID and EMAIL elements to the EMPLOYEE view.

Pivot the number of occurrences of EMAIL that you want to include in the view. Each EMAIL occurrence becomes a single occurring element in the view.

Add the PHONE element.

I have the following element definition in my DTD:

<!ELEMENT EMPLOYEE (EMPNO, SALARY)+>

How can I match the EMPNO and SALARY in the same view?

<!ELEMENT EMPLOYEE (EMPNO+, SALARY+)>

Rewrite the element definition to make the definition unambiguous.
You might define the EMPLOYEE element as follows:
<!ELEMENT EMPLOYEES (EMPLOYEE+)>
<!ELEMENT EMPLOYEE (EMPNO, SALARY)>
When you use this syntax, you define one EMPNO and one SALARY for each EMPLOYEE. The EMPLOYEE view contains both elements. Include EMPLOYEE as a multiple-occurring element in EMPLOYEES.
Leave the elements in separate views and use the source definition twice in a mapping.
When EMPNO and SALARY are in different views, you can still combine the data in a mapping. Use two instances of the same source definition and use a Joiner transformation.
I imported an XML file with the following structure:
<Bookstore>
				 	<Book>Book Name</Book>
	 	 	 <Book>Book Name</Book>
	 	 	 	 	 	 	 	 <ISBN>051022906630</ISBN>
</Bookstore>
When I import this XML file, the Designer drops the ISBN element. Why does this happen? How can I get the Designer to include the ISBN element?
Use the schema to import the XML definition
. When you use an XML file to import an XML definition, the Designer reads the first element as simple content because the element has no child elements. The Designer discards the ISBN child element from the second Book instance. If you use a schema to import the definition, the Designer uses the schema definition to determine how to read XML data.
Verify the XML file accurately represents the associated schema
. If you use an XML file to import a source definition, verify the XML file is an accurate representation of the structure in the corresponding XML schema.