Which language displays your rule in a color-coded, prose-style outline format?

Which language displays your rule in a color-coded, prose-style outline format?

• A. Rich Text
• B. XML
• C. Native HTML
• D. Session Information Report

Answer: (B)

Think of representing rules as a structured outline where each rule and its subrules are wrapped in clearly labeled tags. XML is built for exactly that kind of hierarchical, data-centric organization. Its tag-based format makes the structure explicit, so you can easily traverse or transform the rules. When you want to present them as a color-coded, prose-style outline, you can apply styling with CSS or use XSLT to render different levels with colors and indentation while keeping the underlying data intact. This separation of content from presentation is what makes XML so flexible for displaying rules in a readable, outline-like format. Rich Text focuses on how text looks within a document, but doesn’t provide the robust, portable hierarchical structure, making it less ideal for encoding rules as reusable data. Native HTML can present content well, but it’s primarily a presentation language and isn’t the best way to encode a structured rule set for multiple renderings. Session Information Report isn’t a markup language at all, so it wouldn’t serve as the language for modeling the rules.

Think of representing rules as a structured outline where each rule and its subrules are wrapped in clearly labeled tags. XML is built for exactly that kind of hierarchical, data-centric organization. Its tag-based format makes the structure explicit, so you can easily traverse or transform the rules. When you want to present them as a color-coded, prose-style outline, you can apply styling with CSS or use XSLT to render different levels with colors and indentation while keeping the underlying data intact. This separation of content from presentation is what makes XML so flexible for displaying rules in a readable, outline-like format. Rich Text focuses on how text looks within a document, but doesn’t provide the robust, portable hierarchical structure, making it less ideal for encoding rules as reusable data. Native HTML can present content well, but it’s primarily a presentation language and isn’t the best way to encode a structured rule set for multiple renderings. Session Information Report isn’t a markup language at all, so it wouldn’t serve as the language for modeling the rules.