Configuration on Java

• Feature ResolverFeature.URI_FOR_SYSTEM (type: Boolean)

• System property xml.catalog.uriForSystem

• Property file property uri-for-system

Configuration on .NET

• Feature ResolverFeature.URI_FOR_SYSTEM (type: bool)

• Environment variable XML_CATALOG_URI_FOR_SYSTEM

• Property file property uriForSystem

Ignore the distinction between system identifiers and URIs. The distinction between external identifiers (the public and system identifiers that are used in DTDs) and general URIs (as might be used to load a RELAX NG Grammar or XML Schema, for example), is not supported uniformly by the parser APIs. The Xerces XML Schema implementation, for example, users the resolveEntity API to load XML Schema imports.

Ordinarily, system identifier resolution interrogates the system and public entries (and their related entries), but not the uri entries. If this property is true, the resolver will attempt to resolve system identifiers with uri entries (after attempting to resolve them with the system and public entries.