Example: Consolidated Schema Document - Analytics Database - Teradata Vantage

XML Data Type

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Analytics Database
Teradata Vantage
Release Number
17.20
Published
June 2022
ft:locale
en-US
ft:lastEdition
2023-10-30
dita:mapPath
tkc1628112506748.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
dgs1472251600184
lifecycle
latest
Product Category
Teradata Vantageā„¢

The following is a sample consolidated schema document:

<?xml version="1.0" encoding="UTF-8"?>
<ConsolidatedSchema
   schemaURI="http://www.example.com/schemauri" >
   <ComponentSchema locationURI="http://example.com/schemauri"
      targetNamespace="http://www.example.com/tns">
      <xs:schema xmlns:xs="..." xmlns:xsi="..."
         xmlns:tns="http://www.example.com/tns">
      ....
      </xs:schema>
   </ComponentSchema>
   <ComponentSchema locationURI="http://www.example.com/includedschema1.xsd"
      targetNamespace="http://www.example.com/tns">
      <xs:schema xmlns:xs="..." xmlns:xsi="..."
         xmlns:tns="http://www.example.com/tns">
      ....
      </xs:schema>
   </ComponentSchema>
   <ComponentSchema locationURI="../otherschema/importedschema1.xsd"
      targetNamespace="http://www.example.com/tns2">
      <xs:schema xmlns:xs="..." xmlns:xsi="..."
         xmlns:tns2="http://www.example.com/tns2">
      ....
      </xs:schema>
   </ComponentSchema>
</ConsolidatedSchema>

The ConsolidatedSchema element represents the envelope which will contain the individual schema documents that make up the schema. It identifies the schema in question through a schemaURI attribute, making it a complete self-identifying package.

The ComponentSchema element, which is a child of the ConsolidatedSchema element, will wrap each individual schema document that makes up the schema grammar. This element contains a locationURI attribute that is used to pick out the schema document when it is required during the processing of the root schema. For example, if a schema with a given location URI is imported in the root schema or one of the other imported/included schemas, the resolver will pick the ComponentSchema element with the appropriate locationURI attribute and take its xs:schema child element.