An XML processor performs entity resolution when requested to find a second file in the course of processing a current file. The XML processor knows labeling information about the entity which can include system identifier information and possibly a name, public identifier, and other information. The XML processor uses these identifiers to determine the location of a desired external entity. The process of mapping the known labeling information into an actual location is called entity resolution. The file that contains the mapping information is called the entity catalog.
Entity catalogs can use any arbitrary syntax when that syntax is recognized by a processor. Common systems of notation you can use include TR9401, OASIS XML Catalog, XML Catalogs, or simple Java properties files.
The XML module supports the integration of XML catalogs of these types into the IDE. You can use XML entity catalogs by mounting a catalog file in the Runtime tab of the Explorer. When performing external entity resolution, the XML module consults your mounted catalogs while resolving references in a document. The XML module supports the OASIS XML Catalog format, the XML-related sections of TR9401, and deprecated formats such as XCatalog v0.2 and XMLCatalog v0.4. You can also use implementations from other vendors.
Using a catalog in this manner enables you to avoid using an Internet connection for your XML document. Instead, the XML module remaps the identifiers to local resources.
For more information on the OASIS XML Catalog specification, see http://www.oasis-open.org/committees/entity/spec.html.
See also | |
---|---|
The XML Module |