> Transforming Data Using the XQuery Mapper > Transforming Data Using XQuery Mapper

Transforming Data Using the XQuery Mapper

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Transforming Data Using XQuery Mapper

You can use the graphical interface of XQuery Mapper to create data transformations, by mapping elements in source schemas to elements in a target schema. XQuery Mapper generates an XQuery, which is saved as an .xq file.

The procedure to transform data using XQuery Mapper is described in the following sections:

Launching XQuery Mapper

  1. Choose Start > Programs > BEA > WorkSpace Studio.

    2. The Workspace Launcher dialog box is displayed.

    Figure 2-1 Workspace Launcher


    Workspace Launcher

  2. In the Workspace field, specify the folder in which the project files must be stored.
    3. Note: If required, select the Use this as the default and do not ask again check box, and click OK.
  3. Open the XQuery transformation perspective by choosing Window > Open Perspective > XQuery Transformation from the WorkSpace Studio menu.

    4. The XQuery transformation perspective launches automatically when you open an XQuery file. If, however, XQuery Mapper is open and no XQuery file is open, you must launch the XQuery transformation perspective manually.

Creating the XQuery Mapper Sample Project

The XQuery Mapper sample project includes sample schema and XML files, which you can use to create XQuery transformations as described in Examples: Data Transformation Using XQuery Mapper.

You can create the sample project by using a wizard from within the XQuery transformation perspective.

  1. From the WorkSpace Studio menu bar, choose File > New > Other > Data Transformation > Tutorial: XQuery Transformation, and click Next.
  2. Enter a name for your sample project and click Finish.

    3. The sample project is created and displayed in the Navigator view. The project contains the following folders:

    • schemas folder: Contains the XML schema (.xsd) files of the sample project.
    • XML folder: Contains test XML files required by some of the samples.
    • XQueryTransformations folder: This is the folder in which you will create the XQuery files for the samples.

To learn more about creating projects and importing the files you need for those projects, see the following:

Note: You can import project-specific XML schemas, Web Service Definition Language (WSDL) files, and Message Format Language (MFL) files from any location. Before you import the files, it is recommended that you create a folder structure that meets your business needs. For more information, see Importing and Creating Schema Files.

Creating an XQuery Mapper Project

  1. Switch to the XQuery transformation perspective by choosing Window > Open Perspective > XQuery Transformation.
  2. Choose File > New > Project.

    3. The New Project wizard is displayed.

  3. Choose General > Project and click Next.
  4. Enter a name for the project.
  5. Ensure that the Use default location check box is selected.
  6. Click Finish.

Importing and Creating Schema Files

Schema files can be created in and imported from any location. The following schema types are supported:

Importing XML Schemas and MFL Files

  1. Switch to the XQuery transformation perspective by choosing Window > Open Perspective > XQuery Transformation.
  2. In the Navigator view, select the project into which you want to import the XML schema or MFL file.
  3. Choose File > Import.

    4. The Import wizard is displayed.

  4. You can import XML schemas and MFL files from a variety of sources. Select the appropriate source and click Next.
  5. Browse for and select the required file, and click Finish.

After the schemas files or MFL files are imported, they are available in the New XQuery Transformation wizard.

The following figure shows how the imported XML schemas are displayed in the New XQuery Transformation wizard.

Figure 2-2 New XQuery Transformation

New XQuery Transformation

Creating XML Schemas

You can create XML schemas by using the XML Schema Editor.

  1. Switch to the XQuery transformation perspective by choosing Window > Open Perspective > XQuery Transformation.
  2. In the Navigator view, select the project in which you want to create the schema files.
  3. Select File > New > Other ...

    4. The New screen is displayed.

    Figure 2-3 Select a Wizard


    Select a Wizard

  4. Expand the XML node.
  5. Select XML Schema and click Next.
  6. Select the parent folder in which you want to create the schema file.
  7. Enter a name for the schema file and click Finish.

The schema file is created in the specified project. You can now specify the details of the schema and save the file.

For information about using the XML Schema Editor, see Introduction to the XSD Editor at http://www.eclipse.org/webtools/community/tutorials/XMLSchemaEditor/XMLSchemaEditorTutorial.html.

Creating XML Files from XML Schemas

  1. Switch to the XQuery transformation perspective by choosing Window > Open Perspective > XQuery Transformation.
  2. In the Navigator view, select the project in which you want to create the schema files.
  3. Select File > New > Other ...

    4. The New screen is displayed.

    Figure 2-4 Select a Wizard - XML File


    Select a Wizard - XML File

  4. Expand the XML node.
  5. Select XML and click Next.

    6. The Create XML File dialog box is displayed.

    Figure 2-5 Create XML File


    Create XML File

  6. Select the Create XML file from an XML schema file option and click Next.
  7. Select the parent folder in which you want to create the XML file.
  8. Enter a name for the XML file and click Next.
  9. Select the XML schema based on which you want to create the XML file and click Next.
  10. Select the root element of the XML file and click Finish.

The XML file is created in the specified folder. You can now specify the details of the file and save it.

For information about using the XML Editor, see Creating XML files Tutorial at http://www.eclipse.org/webtools/community/tutorials/XMLWizards/XMLWizards.html.

Creating WSDL Files

  1. Switch to the XQuery transformation perspective by choosing Window > Open Perspective > XQuery Transformation.
  2. In the Navigator view, select the project in which you want to create the WSDL files.
  3. Select File > New > Other ...

    4. The New wizard is displayed.

  4. Expand the XML node, select WSDL, and click Next.
  5. Select the parent folder in which you want to create the WSDL file.
  6. Enter a name for the WSDL file and click Next.
  7. Enter the target namespace and prefix of the WSDL file.
  8. If required, select the Create WSDL Skeleton check box.
  9. Select the protocol and the binding option and click Finish.

The WSDL file is created in the specified project.

For information about using the WSDL Editor, see Introduction to the WSDL Editor at: http://www.eclipse.org/webtools/community/tutorials/WSDLEditor/WSDLEditorTutorial.html.

Creating MFL Files

You can create MFL files by using the Format Builder tool (Start > Programs > BEA Products > Tools > Format Builder).

For more information about the Format Builder tool, see Format Builder Online Help.

Selecting Source and Target Data Types

Before you create a data transformation, you must define the source target types and a target data type. The source and target types can be non-XML, XML, and simple data types.

  1. Select the project for which you want to select source and target data types.
  2. Right-click and choose New > XQuery Transformation.

    3. The New XQuery Transformation wizard is displayed.

  3. Enter a name for the .xq file.
  4. Click Next.

    5. The Source Types dialog box is displayed.

  5. In the Available Source Types pane select the source data types.
    • If the source is XML data, choose XML.
    • If the source is MFL data, choose Non-XML.
    • If the source data is of standard types, such as boolean, String, and int, then choose Simple.
  6. Select the required source data elements.
    7. Note: For schemas to be displayed in the Available Source Types and Available Target Types pane, the XML and non-XML files that contain these schemas must first be imported into or created in WorkSpace Studio.
    Note: The Available Source Types and Available Target Types panes show only schemas that exist in the schemas folder of the XQuery Transformation project. If you prefer to keep your schemas in any other folder, you must specify the path to that folder in the XMLBeans settings for the project (by choosing Project > Properties, the XMLBeans page, and then the Source Paths tab).

    For example, to add input data from schemas/Dates.xsd, select the date element in the schema as the input element and click Add, as shown in the following figure.

    Figure 2-6 Selecting Source Types


    Selecting Source Types

    The elements and attributes that make up the selected element are displayed in the Selected Source Types pane.

  7. After selecting the required source types, click Next.

    8. The Target Types dialog box is displayed.

  8. In the Available Target Types pane, select the target data type, and click Add.

    9. The elements and attributes that make up the selected element are displayed in the Selected Target Type pane.

    Note: You can specify only one target data type.
  9. Click Finish.

The .xq file is displayed in the Design view. It shows the source and target data types that you selected.

Creating Data Transformations

You can perform the following types of data transformations:

Creating Basic Element Transformations

Basic element transformation involves mapping a source element to a target element. The source and target elements may have the same name, type, or scope.

The following are some examples of the types of basic element transformation that you can perform:

Prerequisite

The XQuery file is created as described in Selecting Source and Target Data Types.

Creating Element-to-Element Links

  1. Select the project for which you want to create element-to-element links, and open the XQuery file in which the transformation must be stored.
  2. Drag the required element from the Source pane to the target element in the Target pane.

    3. For example, to create a link between the customer-name element in the source schema and the customer-name element in the target schema, drag customer-name from the Source pane to the Target pane. An arrow connects the two elements, as shown in the following figure.

    Figure 2-7 Element-to-Element Links


    Element-to-Element Links

Note: While dragging from the Source pane to the Target pane, a dashed line appears temporarily between the two elements. For more information about link patterns, Link Patterns.
  1. After creating the required element-to-element links, save the changes.

Creating Basic Attribute Transformations

Basic attribute transformation involves mapping a source attribute to a target attribute. The source and target attributes may have the same name, type, or scope.

The following are some examples of basic attribute transformations:

Prerequisite

The XQuery file is created as described in Selecting Source and Target Data Types.

Creating an Attribute-to-Element Link

  1. Select the project for which you want to create attribute-to-element links, and open the XQuery file in which the transformation must be stored.
  2. Drag the required attribute from the Source pane to the appropriate element in the Target pane.

    3. For example, to create a link between the street attribute of the address element in the source schema and the street element of the target schema, drag the street attribute from the Source pane to the Target pane, as shown in the following figure.

    Figure 2-8 Attribute-to-Element Link


    Attribute-to-Element Link

  3. After creating the required links, save the changes.

Similarly, you can create element-to-attribute and attribute-to-attribute links.

Creating Complex Transformations

Complex transformations involve mapping a complex source (for example, a repeating element) to a complex target (for example, a nonrepeating element). The following are some examples of complex transformations:

Prerequisite

The XQuery file is created as described in Selecting Source and Target Data Types.

Creating a Complex Transformation

  1. Select the project for which you want to create the links, and open the XQuery file in which the transformation must be stored.
  2. Drag the required element or attribute from the Source pane to the appropriate element or attribute in the Target pane.

    3. For example, to create a link between product (a repeating group in the source schema) and product (a repeating group in the target schema), drag product from the Source pane to the Target pane, as shown in the following figure.

    Figure 2-9 Repeating-Group– to– Repeating-Group Link


    Repeating-Group– to– Repeating-Group Link

  3. After creating the required links, save the changes.

Editing Data Transformations

After creating a data transformation in the Design view, you can add, change, and delete XQuery code either by editing code directly in the Source view or by adding complex expressions in the Design view.

Note: For information about the XQuery language, see http://www.w3.org/XML/Query.

This section contains information about the following topics:

Viewing and Editing XQuery Files

  1. Select the project containing the XQuery file that you want to edit.
  2. Double-click the XQuery file.
    3. Note: If the XQuery file is XQuery 2002-compliant, it opens automatically in the XQuery 2002 Transformation Editor, which has only Source and Test views. For more information, see Support for XQuery 2002 and 2004.
  3. Select the Source view.

    4. The XQuery code is displayed. Invalid code is underlined in red.

  4. Make the required changes.
    5. Note: If necessary, you can delete the data transformations in the Source view by deleting all the code within the function except the root element.
  5. Save the changes.

Creating Joins and Unions

The Constraints view in the XQuery transformation perspective allows you to constrain or manipulate the relationship between source and target repeating elements.

The following Constraint Type options are available in the Constraints view:

Creating If-Then-Else Expressions

The Target Expression view allows you to create if-then-else expressions.

When a query that contains an if-then-else expression is executed, the conditions that make up the if expression are evaluated. Depending on the result, different values are returned for the target node.

Figure 2-10 shows XQuery code that can be used to implement the following logic:

You can add multiple expressions to the If condition, as shown in the following figure.

Figure 2-11 If-Then-Else Expression in Target Expression View

If-Then-Else Expression in Target Expression View

You can change the position of a condition by selecting it and then clicking the Move Up or Move Down button. You can also remove a condition by selecting it and then clicking Remove.

Note: In the Edit If Condition pane, even if you remove all the expressions by using the Remove button, the if-then-else expression is not removed entirely in the Source view. The expressions associated with the if condition are removed, but the then and else expressions are retained, as shown in the following listing.
Note: <ns0:partId>
{
if (fn:boolean("true"))
then 4554
else 5894
}
</ns0:partId>
Note: The XQuery always returns the then expression. The else expression is retained in the code so that you can reuse it in the future, if required.

For more information, see Creating Nested If-Then-Else Expressions.

Creating For-Let-Where-Order By-Return (FLWOR) Expressions

The Target Expression view allows you to create FLWOR expressions, as shown in the following figure.

Figure 2-12 FLWOR Expression

FLWOR Expression

The following table describes the components of FLWOR expressions.

Table 2-1 Clauses of FLWOR Expressions
Component
Description
Optional or Mandatory
Allowed Nested Expressions
For clause
The For clause iterates over a sequence of input items and returns a value for each item.
At least one For or Let clause
  • If-Then-Else
  • FLWOR
  • Typeswitch
Let clause
The Let clause declares a variable and assigns a value to the variable.
At least one For or Let clause
  • If-Then-Else
  • FLWOR
  • Typeswitch
Where clause
The Where clause specifies the basis for filtering input data. It is similar to the If clause.

Note: Where clauses within a Let clause are valid only if they contain aggregate operations on the sequence of values created by the Let clause. So Where clauses in a Let clause must contain aggregate functions (example: where fn:count(let_var)=3) and not simple comparisons (example: let_var=3).
Optional
 
Order By clause
The Order By clause specifies the basis for sorting the output of the query.
Optional
  • If-Then-Else
  • FLWOR
  • Typeswitch
Return expression
The Return expression defines the output of the query.
Mandatory (only one)
  • If-Then-Else
  • FLWOR
  • Typeswitch

You can insert nested expressions under For, Let, Order By, and Return by right-clicking on them and selecting the required expression from the menu.

Note: In the Design view, if you create a link between repeating elements, a For...Return expression (implicit FLWOR expression) is generated automatically in the Source view. You can add Where clauses to this FLWOR expression by using the Constraints view, but you cannot add Let and Order By clauses. Implicit FLWOR expressions are not shown in the Target Expression view.

For more information, see Creating FLWOR Expressions.

Creating Typeswitch Expressions

Typeswitch expressions may be required in the following situations:

The Target Expression view lets you create typeswitch expressions, as shown in the following figure.

Figure 2-13 Typeswitch Expression

Typeswitch Expression

The following table describes the components of typeswitch expressions.

Table 2-2 Clauses of Typeswitch Expressions
Component
Description
Optional or Mandatory
Allowed Nested Expressions
Operand expression
The Operand is the expression for which the type is to be evaluated.
Mandatory (only one)
 
Case clause
Each Case clause specifies the name of the type to be evaluated and the expression to be returned if the evaluation is true.
Mandatory (at least one)
  • If-Then-Else
  • FLWOR
  • Typeswitch
Default clause
The Default clause specifies the return expression that must be used if the value of the operand expression matches none of the types specified in the Case clauses.
Mandatory (only one)
  • If-Then-Else
  • FLWOR
  • Typeswitch

Inserting XQuery Functions

A set of standard W3C XQuery functions and operators is provided in XQuery Mapper. You can add standard XQuery or user-defined functions in XQuery files and data transformation files. For example, you can, use the upper-case XQuery String function to convert the characters in an XML String value to uppercase characters.

Note: For more information about XQuery 1.0 and XPath 2.0 functions and operators (W3C Working Draft 23 July 2004), see http://www.w3.org/TR/2004/WD-xpath-functions-20040723/.
  1. Switch to the XQuery transformation perspective by choosing Window > Open Perspective > XQuery Transformation.

    2. The Expression Functions view is part of the XQuery transformation perspective.

  2. Open the XQuery file in which you want to insert XQuery functions.
  3. In the Design view, select or create a link to add the function call.

    4. The link becomes green.

  4. Select the Target Expression view.

    5. If the Target Expression view is not visible, choose Window > Show View > Target Expression.

    In the General Expression pane, the XQuery code linking the selected target and source node is displayed and is selected. Keep this selected for the next step.

  5. Delete the existing XQuery code in the General Expression pane.
  6. Find the function that you want to insert in the Expression Functions view.

    7. For this example, from the String Functions folder, select the upper-case function, which converts all the characters of the source element to upper case.

  7. Drag the upper-case function to the General Expression pane.

    8. Leave the parameter of the selected function (the $string-var parameter of the upper-case function in this example) in the General Expression pane selected.

    Note: XQuery functions that are defined by BEA (example: trim-left) are prefixed with fn-bea:.
    Note: XQuery functions that are not listed in the Expression Functions view but defined in the XQuery specification can be used with the fn: prefix.
  8. Select a source parameter for the function using one of the following options:
    • From the Source pane of the Design view, select a source element, drag it to the General Expression pane and drop it over the $string-var parameter.
    • From the Expression Variables view, select a source variable, drag it to the General Expression pane and drop it over the $string-var parameter.
  9. After inserting the required functions and assigning parameters to the functions, click Apply in the General Expression pane.

Inserting Expression Variables

The variables (and their subelements) that you can use in an XQuery are displayed in the Expression Variables view.

Note: If the Expression Variables view is not displayed, choose Window > Show View > Expression Variables.

The following types of variables are displayed in the Expression Variables view:

You can insert expression variables in the following ways:

Viewing Schema Properties

While editing an XQuery file in the Design view, you can view the schema properties of nodes in the current transformation in the Properties view, without opening the source and target XSD or MFL files.

To display the Properties view, choose Window > Show View > Properties.

Note: To change the schema properties of an element or attribute, edit the corresponding schema file (XSD for XML schema and MFL for non-XML schema).

Restricting Output of Optional Elements

If the target schema in a data transformation contains an optional element (minOccurs=“0”), you can design the link to the element such that the element is included in the output XML file only if it contains a value (that is, the element is not empty in the source XML file).

Consider the source XML data in the following listing.

Listing 2-1 XML Data with Optional Element 
<address>
<Address_Line_1>1 Elm Street</Address_Line_1>
<Address_Line_2/>
<City>San Jose</city>
<State>California</State>
<Country>US</Country>
</address>

The Address_Line_2 element is optional and empty. If Address_Line_2 is mapped to a corresponding element in the target schema, then, by default, the output XML file contains an empty Address_Line_2 element.

You can restrict output of such optional elements by right-clicking on the link and selecting Remove Empty Node, as shown in the following figure.

Figure 2-14 Remove Empty Node

Remove Empty Node

The XQuery code underlying the link is enclosed in an if-then-else expression that causes the target element to be produced only if the transformation results in a nonempty value.

You can remove the if-then-else expression by right-clicking on the link and selecting Retain Empty Node, as shown in the following figure.

Figure 2-15 Retain Empty Node

Retain Empty Node

Note: The Remove Empty Node (or Retain Empty Node) option is displayed only when you right-click on a link to an optional target element.

Testing Data Transformations

After creating an XQuery transformation in the Design view, you can test whether the expected XML or non-XML output is generated properly in the Test view.

You can use the autogenerated XML files or your own custom XML and non-XML files for testing the transformations.

Features of the Test View

The following figure shows the features of the Test view.

Figure 2-16 Test View

Test View

Related Topics

Restrictions Applicable to the XQuery Test View

Graphical Features in Design View

This section provides information to help you use the graphical features of XQuery Mapper and interpret the graphical representations in the Design view of XQuery Mapper.

Right-Click Menu Options

The following table lists the options available in the Design view of XQuery Mapper when you right-click on a link or element.

Table 2-3 Right-Click Menu Options
Menu Option
Appears When You ...
Result ...
View Code
Right-click on any link or target element
The view switches to the Source view, and the XQuery code for the link is selected.
Create Constant
Right-click on any simple-type target element
Lets you assign a constant value to the target element.
Disable Target Node
Right-click on any link or target element
Blocking XQuery code is added around the XQuery code of the selected link. The blocking code prevents the XQuery code for the link from being executed at run time.

Note: The Disable Target Node menu option is not available for the root node of the target type.
Enable Target Node
Right-click on a disabled link or target element
The blocking XQuery code is removed from around the selected link so that, at run time, the XQuery code for the link is executed.
Remove Empty Node
Right-click on a link to an optional target element.
Surrounds the link with an if-then-else expression that causes the target element to be produced only if the transformation results in a nonempty value.
Retain Empty Node
Right-click on a link (to an optional target element) for which you selected the Remove Empty Node option earlier.
Removes the if-then-else expression that causes the target element to be produced only if the transformation results in a nonempty value.
Redefine Wildcard Node
Right-click on a wildcard (any type) source or target element
Lets you define a specific data type for a wildcard element.

Note: After you redefine a wildcard node (that is, define a specific data type), you cannot use Ctrl+Z to revert to the any type.
Revert to Wildcard Node
Right-click on a wildcard (any type) source or target element, for which you defined a specific data type earlier by using the Redefine Wildcard Node option.
Changes the data type of the element from the specific type that you defined earlier to wildcard (any type).
Induce Map
Right-click on a structural link.
Data links or data structural links are created between the child nodes of the selected structural link if source and target child elements of the link are the same subschema type.

Note: For the Induce Map option to create child links, the target and source child elements must have the same name and data type, and must be in the same order.
Delete Link
Right-click on any link.
  • Design view: The link is deleted.
  • Source view: The XQuery code underlying the link is deleted.
Delete All Links
Right-click anywhere in the empty pane between the Source and Target panes.
  • Design view: The lines representing the transformation between source and target elements/attributes are deleted.
  • Source view: The generated XQuery code is deleted.

Note: Right-clicking anywhere in the empty pane between the Source and Target panes causes all the nodes to be deselected.

Link Patterns

Links in XQuery Mapper are shown in different colors and patterns to help you distinguish easily between different link types. The following table describes the graphical representation of the links that you create in XQuery Mapper.

Table 2-4 Link Patterns
Link Type
Description
Link Currently Selected?
Representation
Data Link
A link that converts the value of the source node directly to the value of the target node.
Not Selected

Test View
Selected

Test View
Implied Link
A data link for which you modified the underlying XQuery code.
A link for which the XQuery code cannot be interpreted by the XQuery Mapper.
Examples:
  • A link for which you inserted the fn:upper-case XQuery function by using the General Expression section of the Target Expression view.
  • The data links generated between a second set of child nodes when a union constraint is applied to a set of two structural links. The child nodes must be of the same subschema.
Not Selected

Test View
Selected

Test View
Structural Link
A link between two parent structures and that does not map data directly.
Not Selected

Test View
Selected

Test View
Data Structural Link
A data structural link is a combination of a data link and a structural link.
Example: A link between the optional child nodes of a repeating element.
Not Selected

Test View
Selected

Test View
Constraint Link
A link that constrains or limits the resulting data of a join between source parent structures. The constraint link is created with two source nodes.
Example: A a join between two source repeating elements to return the data only when the values of a particular source element are equal to each other.
Not Selected

Test View
Selected

Test View
Copy Link
A link between two identical schema substructures. At run time, the source data is copied directly, as a block, to the target data.
A copy link is also generated when you map an untyped XML node to a typed XML complex-type node.
Not Selected

Test View
Selected

Test View

Link Colors

When you drag a node from the Source pane to the Target pane, a temporary link (dashed line) appears between the two nodes. The color of the line changes depending on the compatibility between the source and target nodes.

When you finish creating the link, a dotted or dashed line (depending on the source and target nodes) is displayed.

XML Global Elements, Global Types, Local Elements, and Attributes

An XML schema type or element is considered global if it is a direct child of the schema element and local if it is not a direct child of the schema element (that is, the element is nested within another element).

The following example XML schema illustrates this difference.

Listing 2-2 XML Schema with Global and Local Elements 
<?xml version="1.0"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" 
targetNamespace="http://www.acme.org/globalExample" 
xmlns="http://www.acme.org/globalExample" 
elementFormDefault="qualified" 
attributeFormDefault="unqualified">
	<xs:element name="globalElement">
		<xs:complexType>
			<xs:sequence>
				<xs:element name="localElement"
					minOccurs="1" maxOccurs="1"
					type="xs:string" />
			</xs:sequence>
			<xs:attribute name="attribute"
				type="xs:string" use="required"/>
		</xs:complexType>
	</xs:element>
	<xs:complexType name="globalType"> 
		<xs:sequence>
			<xs:element name="anotherLocalElement"
			minOccurs="0" maxOccurs="unbounded" 
			type="xs:string" />
		</xs:sequence>
	</xs:complexType>
</xs:schema>

In the preceding XML schema, globalElement is global because it is a direct child of the schema element, whereas localElement is local because it is a child of globalElement.

You can also define a global type, as shown by the globalType element toward the end of the preceding XML schema. While you can have only one global element in an XML schema, you can declare many elements (with different names) of the same global type in a single XML schema.

The following table shows the graphical representations of the different XML components in XQuery Mapper.

Table 2-5 Graphical Representation of XML Components
Component
Graphical Representation
Name in Preceding Example XML Schema
Global Element

Test View
globalElement
Local Element

Test View
localElement
Global Type

Test View
globalType
Attribute

Test View
attribute defined for globalElement


  Back to Top       Previous  Next