Oracle8i Application Developer's Guide - XML Release 3 (8.1.7) Part Number A86030-01 |
|
B2B: How iProcurement Uses XML to Offer Multiple Catalog Products to Users, 4 of 16
This section describes the XML specification for loading the iProcurement unified catalog from external sources. The specification supports the following functionality:
Special characters and non-XML markup must be escaped for the XML parser to function correctly. Specifically, the & and <> characters must be escaped with a CDATA tag.
<![CDATA[ your data here ]]> inserted in any tag for special characters. <SCHEMA> <CATEGORY ACTION="DELETE"> <NAME><![CDATA[Pen & Pencil Gifts Sets]]></NAME> </CATEGORY> </SCHEMA>
Also, if there are any " (double quote) characters within the data itself, these should be replaced by the following character sequence: "
For example:
<itemDescription><![CDATA[6" diameter pipe]]></itemDescription>
Catalog information is divided into three main categories:
Figure 10-3 shows the DTD hierarchical diagram of the catalog:
Here is the Buyer-Hosted catalog DTD:
<?xml version="1.0"?> <!DOCTYPE CATALOG [ <!ELEMENT CATALOG ( ADMIN, SCHEMA?, DATA? ) > <!ATTLIST CATALOG xml:lang NMTOKEN #IMPLIED > <!ELEMENT ADMIN ( NAME, INFORMATION) > <!ELEMENT SCHEMA (CATEGORY | The DESCRIPTOR)* > <!ELEMENT DATA (ITEM)*> <!ELEMENT NAME (#PCDATA) > <!ELEMENT INFORMATION ( DATE, SOURCE ) > <!ELEMENT DATE (#PCDATA) > <!ELEMENT SOURCE (#PCDATA) > <!ELEMENT CATEGORY (NAME | KEY | TYPE | UPDATE )* > <!ATTLIST CATEGORY ACTION (ADD|DELETE|UPDATE) #REQUIRED> <!ELEMENT DESCRIPTOR (NAME | KEY | UPDATE | OWNER | TYPE )* > <!ATTLIST DESCRIPTOR ACTION (ADD|DELETE|UPDATE) #REQUIRED> <!ELEMENT OWNER (NAME?, KEY? ) > <!ELEMENT KEY (#PCDATA) > <!ELEMENT TYPE (#PCDATA) > <!ELEMENT ITEM (OWNER?, NAMEVALUE*, UPDATE ) > <!ATTLIST ITEM ACTION (ADD | DELETE | UPDATE) #REQUIRED> <!ELEMENT UPDATE (NAME | KEY | NAMEVALUE )* > <!ELEMENT NAMEVALUE ( NAME, VALUE ) > <!ELEMENT VALUE (#PCDATA)* > ]>
|
![]() Copyright © 1996-2000, Oracle Corporation. All Rights Reserved. |
|