FlexDoc/XML - XSDDoc - Parameter Tree

About XSDDoc parameters

Root parameter group

Parameter Name / Type / Description
Documentation Profile docProfile : enum {"compact", "detailed", "all"}

This parameter allows you to select a predefined documentation profile.

Each documentation profile represents a certain documentation structure and content. Some of them may be more suitable for your needs or used as a starting point for further customization.

XSDDoc template set exposes ca. 500 parameters. There are so many of them, because every feature found in the documentation that can vary anyhow is controlled by some parameter. Those parameters allow you to customize the documentation structure and content in a very wide range of possibilities. However, that requires you to browse the template parameter tree, to understand what each parameter means and specify some of them accordingly.

The «Documentation Profile» parameter is intended to help you with that. It is used to calculate the default values of lots of other parameters, which allows you to switch at once the whole bunch of settings determined by a particular documentation profile.

Note that it will work only for those parameters specified to use their default values (the check-box in the «Default» column must be selected for them). If you have already changed some of the parameters manually, they won't be affected.

So, after changing the «Documentation Profile» parameter, you will be asked if all other switch parameters (i.e. those with boolean and enum type) must be reset to their default values. That will ensure that the new documentation profile actually takes effect.

If you refuse that, you can do it later via the local menu invoked over «Documentation Profile» parameter by selecting one of the items:

  • Reset All Switches
  • Reset All Affected
Possible Choices: "compact"
Everything about your XML schemas will be documented, however in the most minimal form. In particular:
  • Only top-level (global) XML schema components will be documented separately with Component Documentation pages/blocks.

    The global documenting of local elements is disabled. See also the parameter group:

    Generate Details | Components | Elements | Local Elements
  • All local elements and attributes will be documented in the Table Representations of Content Model of those components where a particular local element/attribute is declared or used.
  • Additionally, local elements with anonymous types will be documented locally (in the Component Documentation of their parent components) also together with the Table Representations of their Content Model.
    A rare possibility of local elements with anonymous complex types defined within other local elements is also taken into account. Such nested-nested local elements are documented recursively along with their parents, which is controlled by the parameter:
    Details | Component | Content Element Detail | Recursive
    See also parameters:
  • The same is for local attributes with anonymous types. They will be documented in more detail in the Attribute Detail section of the Component Documentation of their parent components. See also the parameter:
    Details | Component | Attribute Detail | Include | Local
  • The content model defined by XSD components (i.e. attributes and child elements) will be documented with special Table Representations as well as diagrams (when their generation is enabled).
    In the case of XSD elements, the diagrams will be generated only for elements with anonymous types.

    If the element type is a named (global) one, the element's diagram is essentially the same as for its type. So, you can look at it by the type link.

  • The simple content derivation details will be disabled. All these parameters will be set to none:
  • XML source will not be reproduced anywhere at all. All these parameters will be set false:
  • The summary of all components is generated only once in the All Component Summary page/block. It is not generated for every XML schema and namespace. See also the parameter group:
    Details | Schema | Component Summary
"detailed"
This kind of documentation may be suitable for most schema design patterns:
  • All top-level (global) XML schema components will be documented separately with Component Documentation pages/blocks.
  • All local elements are documented globally (on separate pages referenced from all navigation lists). See also the parameter group:
    Generate Details | Components | Elements | Local Elements
  • The content model defined by XSD component (i.e. attributes and child elements) will be documented with:
    If so many ways are too much for you, you can disable what you don't need by unselecting corresponding parameters. See details by the links above.
  • Additionally, all local attributes with anonymous types will be documented in more detail in Attribute Detail section of the Component Documentation of their parent components. See also the parameter:
    Details | Component | Attribute Detail | Include | Local
  • XML source is reproduced in the documentation only once for each entire XML schema. See also the parameter group:
    Details | Schema | XML Source
  • The summary of all components is generated only once in the All Component Summary page/block. It is not generated for every XML schema and namespace. See also the parameter group:
    Details | Schema | Component Summary
"all features"
All implemented features are enabled.

All local elements are documented globally and without unifying by type.

Each local element on a separate Component Documentation pages/block referenced from all navigation lists. The corresponding HTML/diagram files will be stored according the parent components.

The parameters that control this will be set as follows:

Generate Details | Components | Elements | Local Elements = "all"
Such documentation may be redundant for you.