Which one of the proposals is possible using the HTDS REST?

Question

Options

• AFilter code from the WADL
• BInline XSDs files in the WADL
• COutline XSDs files in the WADL
• DQuery certain elements in the WADL

• A
  89% (40)
• B
  2% (1)
• C
  2% (1)
• D
  7% (3)

Explanation

In HTDS REST, filtering code from the WADL (option A) is a supported operation - it allows selective extraction of relevant descriptors from the WADL document, making it the valid proposal among the choices.

Why the distractors are wrong:

• B (Inline XSDs): WADL supports inline grammar definitions natively, but this is a general WADL feature - not something specifically proposed or added via HTDS REST.
• C (Outline XSDs): Similarly, referencing external XSD files (outlining) is standard WADL behavior, not an HTDS-specific proposal.
• D (Query certain elements): WADL is a description language - it documents service structure. It is not designed as a queryable data source, so element querying is outside its scope.

Memory tip: Think "HTDS adds a filter on top of WADL." The XSD options (B and C) sound plausible because XSDs and WADL go together naturally, but they describe what WADL already does on its own - not what HTDS proposes. If a choice sounds like a built-in WADL feature rather than something HTDS contributes, it's likely a distractor.

No community discussion yet for this question.