FlexDoc/XML - XSDDoc - Parameter Tree

About XSDDoc parameters

«Show» parameter group

This parameter group controls the generation of various small fragments (like parts of component names, specific sections etc.)

Parameter Name / Type / Description
Link Titles (Tooltips) show.linkTitle : boolean

Specify whether to generate hyperlink titles.

In HTML, hyperlink titles are specified using title attribute, like this:

<a ... title="link tooltip text"> ... </a>
Most browsers will interpret it as a hyperlink tooltip (a tiny window with the text that appears near the hyperlink when the mouse cursor is moved over it).

Component Name

show.linkTitle.name : boolean

Specify whether the component link title (tooltip) will include the name of the component. This will look as on the screenshot:

The component's name might be helpful in the link tooltips over diagrams (as well as in other cases).

Namespace URI

show.linkTitle.namespace : boolean

When a hyperlink appears on a schema component name, it would be helpful to use the link tooltip to quickly see what a namespace this component belongs to.

This might be particularly useful when the XML schemas you document define many components with equal local names, however, in different namespaces and no prefixes are defined for those namespaces at that.

This parameter allows you to generate such tooltips. When it is selected (true), the titles of hyperlinks leading from component names will include the namespace URI of those components, as shown on the following screenshot:
But note that since the namespace URIs are typically rather long strings, when added to each hyperlink, they may considerably blow out the generated HTML files. That's why this parameter was introduced: to be able to switch them off.

Defined in Schema

show.linkTitle.schema : boolean

Specify whether the component link title (tooltip) will include the name of the XML schema file, where the component is defined.

For global components, that will add a text like this:

defined in XMLSchema.xsd
For unified local elements, the additional text may be more complex:
File Locations show.fileLocation : boolean

Specify whether to show the location of schema source files (or URLs)

Relative Path

show.fileLocation.relative : boolean

Specify whether to display the schema location as relative pathname.

When this parameter is selected (true) and the schema file resides on the local system, the file pathname will be converted to a relative one against the documentation destination directory.


show.fileLocation.hyperlink : boolean

Specify whether to generate a hyperlink to the schema file.

When this parameter is selected (true), the schema location text will be hyperlinked to the actual schema file.

When the displayed schema location is a relative pathname, the hyperlink is generated relatively to the location of the given document file. Otherwise, the hyperlink is generated to an absolute URL either on the local system or remote one.

Namespace Prefixes show.nsPrefix : boolean

Specify whether to add namespace prefixes to any XML names appearing in the generated documentation.

As you may know, each XML name is not just a string. Rather, it is a vector of two values: { namespace URI, local name }

Any namespace prefixes used in the output documentation originate from the namespace URI/prefix bindings declared in the source XSD files. For a particular XML name, its namespace prefix is generated according to the binding for the given namespace found the nearest to the documentation context where that XML name appears.


Suppose you generate documentation for two XML schemas: schema1 and schema2.

The schema1 is targeted to the namespace associated with 'namespace_uri_1' URI, which is bound to 'myns' prefix. This schema defines some MyType type component.

The schema2 is targeted to a different namespace, however, it also uses MyType, which it imports from the schema1. To reference to that type, the schema2 binds the 'namespace_uri_1' to the prefix 'ns1', so MyType looks in it as:

How will MyType look in the output documentation when this parameter is selected?

In the parts of the documentation related to schema1 you will see:

In parts related to schema2, you will see:
However, both names will be connected via hyperlinks to the same details of MyType type.
Element Name Extensions show.elementNameExt : enum {"always", "repeating", "never"}

Specify whether to generate extended names of local elements.

Local elements are the locally defined element components. For more information, please see: Documenting of local elements.

The extended name of a local element is made of its normal name extended with some short info about the possible element location or its type. For example:

configuration (in plugin in plugins in reporting)
xs:complexType (type xs:localComplexType)
here in the brackets are the local element name extensions.

The name extension is needed to distinguish that element in the documentation from other local elements, which share the same XML name, however have different content.

The name extensions may be not necessary for local element with unique names. For instance, some XML schemas are designed (or generated) so that almost all element components are declared locally, except only the root element. At that, all element names may be unique. So, the name extensions are not really needed and will only overload the documentation.

Possible Choices:

Generate name extensions for all local elements.
"for repeating names only"
Generate name extension only for local elements with non-unique names (i.e. whose XML names are shared by any other element components).
Do not generate the name extensions.
See Also:
Adding extensions to local element names
About (footer) show.about : enum {"full", "short", "none"}

Specify whether to generate the "About" section added at the bottom of each generated document.

This section shows certain information about FlexDoc/XML software and XSDDoc template set, which power this XML Schema Documentation Generator.

Possible Values:

Generate the detailed information.
Generate only a brief notice.
Do not generate the "About" section.
Actually, all what you can see in the "About" section is generated entirely by the about.tpl template.

Once you acquire a full license for FlexDoc/XML SDK, you will be able to modify this template as you wish (as well as all other XSDDoc templates) so as to generate in the "About" section something of your own. For instance, to insert you company info, logotype, copyright statement about your software (your XML schema), etc.