Schema Validation Schema validation involves validating the schema native

6-50 Oracle Fusion Middleware Users Guide for Technology Adapters The following is a sample nxsd file: ?xml version= 1.0 encoding= UTF-8 ? xsd:schema xmlns:xsd=http:www.w3.org2001XMLSchema xmlns:nxsd=http:xmlns.oracle.compcbpelnxsd xmlns:tns=http:TargetNamespace.comInboundService targetNamespace=http:TargetNamespace.comInboundService elementFormDefault=qualified attributeFormDefault=unqualified nxsd:parseBom=true nxsd:version=NXSD nxsd:stream=chars nxsd:encoding=UTF8 xsd:element name=Root-Element xsd:complexType xsd:sequence xsd:element name=mydata minOccurs=1 maxOccurs=unbounded nxsd:style=array nxsd:cellSeparatedBy={eol} xsd:complexType xsd:sequence xsd:element name=C1 type=xsd:string nxsd:style=fixedLength nxsd:length=3 xsd:sequence xsd:complexType xsd:element xsd:sequence xsd:complexType xsd:element xsd:schema

6.3 Translator XPath Functions

The translator XPath functions can translate data from a native format such as CSV, fixed-length, tab-delimited, and COBOL Copybook formats to an XML format and from an XML format to a native format. The translator XPath functions are of two types, streaming and non-streaming. The difference is that the streaming translator XPath functions implement the batching transformation approach while the non-streaming XPath functions do not implement the batching transformation approach. With the batching transformation approach, files that are of the order of a few gigabytes GB can be processed without running into memory issues. This section includes the following topics: ■ Section 6.3.1, Terminologies ■ Section 6.3.2, Translator XPath Functions

6.3.1 Terminologies

This section describes the terminologies that you must understand for using translation XPath functions. Attachment Element An attachment element unusually refers to the actual content elsewhere by using an href attribute. The actual content may be present in a file system or in a database table. An attachment is usually represented by using the following schema construct: element name=hrefelement complexType attribute name=href type=string