Oracle8i Application Developer's Guide - XML Release 3 (8.1.7) Part Number A86030-01 |
Library | Service | Contents | Index

B2B: How iProcurement Uses XML to Offer Multiple Catalog Products to Users, 3 of 16

## iProcurement: XML Parser for Java

iProcurement includes Oracle's XML Parser for Java (installed on the middle tier but separate from the Internet Application Server (iAS). This parser checks if an XML document is well-formed, and optionally, if it is valid.

#### Internationalization

iProcurement is fully NLS compliant, however, the product does not support multiple languages in releases 10.7 and 11. For this reason, XML document data must be specified in the base language of the installation.

Note: To avoid character set conversion data loss between the XML document and the database, specify a character set encoding that is both supported by the Oracle XML Parser and compatible with the database installation character set.

#### Language Identification

Both XML documents support language specification using the `xml:lang` attribute as described in the Extensible Markup Language (XML) 1.0 W3C recommendation. Refer to http://www.w3.org/TR for all published, draft, or proposed recommendations.

The following table, extracted from the XML 1.0 specification, describes in general terms how language is identified:

    LanguageID:=Langcode (- Subcode)*
    Langcode:=ISO639Code | IanaCode | UserCode
    ISO639Code:=([a-z] | [A-Z]) ([a-z] | [A-Z])
    IanaCode:= (`i' | `I') `-` ([a-z] | [A-Z]) +
    UserCode:= (`x' | `X') `-` ([a-z] | [A-Z]) +
    SubCode:=([a-z] | [A-Z]) +

According to the XML 1.0 specification, Langcode can be any of the following:

- A two-letter language code as defined by ISO 639, "Codes for the representation of the names of languages"

- A language identifier registered with the Internet Assigned Numbers Authority (IANA)

- A language identifier agreed on between parties in private use

There may be any number of Subcode segments, however, if the first subcode exists and consists of two letters then it must be a country code from ISO 3166, "Codes for the representation of names of countries."

#### iProcurement Language Identification

To convert from the XML document language specification to Oracle Applications language codes, specify the following:

- An ISO 639 language code

- An ISO 3166 country code

The following example shows how to set the language to English and the country to the United States:

    <e xml:lang="EN-US">

The `xml:lang` declaration applies all attributes and content of the element where it is specified, unless overridden with another instance of `xml:lang` on a specific attribute. Since releases 10.7 through 11i of iProcurement expect a single language, this should be specified for the root element in each document type.

#### iProcurement Character Set Encoding

The XML Parser processor is informed of the character set used in an XML document via the encoding parameter of the XML declaration:

    <?xml . . . encoding='UTF-8' . . . ?>

If no document encoding is specified in the XML declaration, UTF-8 is assumed.

Any other ASCII or EBCIDIC based encodings supported by the JDK can be used, however, they must be specified in the format required by JDK instead of as official character set names defined by IANA.

See http://OTN.oracle.com/tech/xml for the latest XML Parser supported character sets. Current support character sets and other Parser specifications also listed in Appendix C, "XDK for Java: Specifications and Cheat Sheets".

| Copyright © 1996-2000, Oracle Corporation. All Rights Reserved. |
Library | Service | Contents | Index