• Chapter 1: Getting Started with Stylus Studio®
• Chapter 2: Editing and Querying XML
• Chapter 3: Converting Non-XML Files to XML
• Chapter 4: Working with XSLT
• Chapter 5: Creating XSLT Using the XSLT Mapper
• Chapter 6: Debugging Stylesheets
• Chapter 7: Defining XML Schemas
• Chapter 8: Defining Document Type Definitions
• Chapter 9: Writing XPath Expressions
• Chapter 10: Working with XQuery in Stylus Studio
• Chapter 11: Composing Web Service Calls
• Chapter 12: Accessing Relational Data as XML
• Chapter 13: Building XML Pipelines
• Chapter 14: Publishing XML Data
  • The Stylus Studio XML Publisher
  • Building an XML Publisher Report
  • Working with Data Sources
    • How Data Sources are Represented in XML Publisher
      • Working with Namespaces
    • Adding a Data Source
    • Specifying a Default Data Source
    • Data Source Required for XSLT
    • Using XML Schema or DTD as a Data Source
  • Adding Data to a Report
  • Working with Report Components
  • Generating Code for an XML Publisher Report
  • Example: Building an XML Publisher Report
  • Properties Reference
• Chapter 15: Integrating with Third-Party File Systems
• Chapter 16: Extending Stylus Studio
• Chapter 17: The Stylus Studio Java API
• Chapter 18: Stylus Studio GUI Reference

Home > Online Product Documentation > Table of Contents > How Data Sources are Represented in XML Publisher

How Data Sources are Represented in XML Publisher

When you add a data source to the data sources panel, Stylus Studio displays the schema representation, or the data model, for that source. The following illustration shows how the videos.xml document from the VideoCenter folder in the examples project appears after it has been added as a data source:

Figure 441. XML Document in the Data Sources Panel

Working with Namespaces

If the document you have selected as a source uses a namespace prefix, Stylus Studio displays the prefix and the URI at the bottom of the data sources panel, as shown in Figure 442.

Figure 442. Namespace Prefix and URI

You can edit the value in the Namespace field, which can simplify the process of typing XPath expressions you might use when defining a property. For example, you could change books to simply b to shorten and simplify XPath expressions. See Example: Using Context and XPath Sub-Properties to Format Text to learn more about using XPath expressions when building XML Publisher reports.