XSD bridge reference
Imported assets and parameter information for the XSD bridge.
About this bridge
The XSD bridge imports XML schema definition (XSD) files that are on the local computer. The bridge supports XSD version 1.0. New constructs that are added in XSD 1.1 are not supported.
You can import a single XSD file or multiple XSD files that are in a compressed file, such as a ZIP file. You can browse these files in InfoSphere® Information Governance Catalog.
Use the compressed-file import method if you are importing XSD files that have relationships to other XSD files. Any relationships between different XML schema definitions in the compressed file are preserved when they are imported. If an XSD has a relationship to an XSD that is not part of the import file, a warning is issued and that relationship remains unresolved on import. Use the Log unresolved objects import parameter to specify that detailed information about the unresolved objects is written to the log file.
During import, you specify a contract library to contain the XSD files.
XML schema definition- A framework document that defines the rules and constraints for XML data documents, which are instances of the XSD.
XSD element- Declares a named structure that can have instance data in XML documents. The structure of an XSD element can simple or complex. Elements can be declared globally or locally.
XSD attribute- Models data values in an XML schema. It assigns a name to an attribute and associates it with a simple type. XSD attributes can be declared globally or locally.
XSD simple type- A top-level schema component that defines reusable data types for attributes and simple, text-only elements. It constrains the value of an attribute or an element in an XML instance.
XSD complex type- A top-level schema component that defines reusable data types for complex elements. XSD complex types have child elements and attributes, and specify constraints on the content of elements.
XSD element group- A top-level schema component that defines a reusable fragment of content elements. It encapsulates a set of elements that are referenced together in many complex elements and types.
XSD attribute group- A top-level schema component that defines reusable set of attributes. It encapsulates a set of related attributes that appear in many different elements and complex types.
XSD bridge Import parameters
Specify values for the following import parameters
- File
- Browse to select an XSD file or a compressed file that contains XSD files, such as a ZIP file. The file must be on the local computer.
- Import keys
- By default, XSD keys are imported. Remove the check mark if you do not want to import keys.
- Import annotations
- By default, XSD annotations are imported. Remove the check mark if you do not want to import annotations.
- Log unresolved objects
- Select to write detailed information about any unresolved objects to the import event log. By default, only the number of unresolved objects is written to the import event log.
- Contract library name
- Name of the contract library.
Enter a name for the contract library. The name must start with a letter, underscore, or colon. The name can contain only letters, digits, underscores, colons, hyphens and periods. Other entered characters are removed from the name before the asset is saved to the metadata repository.
- Contract library description
- Enter a description of the contract library. The description
field cannot contain the following characters: ampersand (&),
less than (<), greater than (>), double quotation mark ("), or
single quotation mark ('). Characters of those types are removed from
the description before the asset is saved to the repository.
If the imported contract library already exists in the metadata repository, the description that you enter is ignored.
- Contract library category
- Category of the contract library.
Enter a name for the category. The name must start with a letter, underscore, or colon. The name can contain only letters, digits, underscores, colons, hyphens and periods. Other entered characters are removed from the name before the asset is saved to the metadata repository.
If the imported contract library already exists in the metadata repository, the category that you specify is ignored.
- If an asset description already exists
- Specify what action to take if an imported asset matches an existing asset in the metadata repository. You can keep the existing description, or overwrite the existing description with the description of the imported asset.