Manage component schemas

In the Components browser, the rules defined in your schema report errors and warnings during automatic and manual validations. This validation helps authors maintain the structural integrity of XML documents. Inspire provides three schemas for basic XML validation, but you can also specify a customized schema.

Before you can create a new schema, do the following:

  • Follow the steps in Allow the use of a custom schema.
  • Contact support to enable the use of a custom schema by sending an email to: GlobalLinkCCMS-Support@TransPerfect.com.
  • Inspire provides a definition of the following schema standards:
    • DITA 1.2
    • DITA 1.3
    • DocBook 5.0
  • If you use a schema standard that is not provided by Inspire, you must add it. Follow the steps in: Manage schema standards.

Tips and tricks

  • Multiple active schemas. All schemas marked as Active can be used for validation at the same time. Make a custom schema active
  • Use Schematron. You can upload Schematron files to use for validation in the Components browser and projects. Add a Schematron validation configuration
  • Use validation configurations. If you have multiple active schemas, you can let users choose which set of standards they want to use to validate their content. Create a validation configuration
  • Component type configurations. If no validation configurations exist, instead of prompting the user, Inspire looks in the component type's configuration in the public identifier field.
    • To set the component type's public identifier, read Configure component types.
    • For example, if you have a different framework for each genre of book you publish, you would:
      1. Save each schema framework in Inspire (Create a custom schema).
        1. FictionBook schema
        2. NonFictionBook schema
        3. YouthBook schema
      2. Create a component type configuration for each structure in each schema.
        1. For the FictionBook schema, you can create a component type configuration called "Fiction Topic" with a public identifier of FictionBook.
        2. For the NonFictionBook schema, you can create a component type configuration called "Non-Fiction Topic" with a public identifier of NonFictionBook.
        3. For the YouthBook schema, you can create a component type configuration called "Youth Topic" with a public identifier of YouthBook.
      3. Let authors know which topic types to use:
        1. Authors writing a fiction book would create content in a "Fiction Topic". Using the public identifier, Inspire knows to validate a "Fiction Topic" with the FictionBook schema.
        2. Authors writing a non-fiction book would create content in a "Non-Fiction Topic". Using the public identifier, Inspire knows to validate a "Non-Fiction Topic" with the NonFictionBook schema.
        3. Authors writing a children's book would create content in a "Youth Topic". Using the public identifier, Inspire knows to validate a "Youth Topic" with the YouthBook schema.
        4. Authors writing a historical fiction book which is both fiction and non-fiction could create content in a generic "DITA-Topic" which uses a public identifier of Oasis. This is a default framework that Inspire provides.