Markup and Web Languages

Canonical XML is a W3C specification that defines a standardized form of XML documents to enable logical equivalence comparison. Two XML documents with different formatting/whitespace but identical logical content produce the same canonical form, allowing equivalence testing. It is NOT for encryption or signing.

In WSDL 1.1, global schema types are referenced using the 'type' attribute in part elements, while global schema elements are referenced using the 'element' attribute. Mixing these (using 'element' for types or 'type' for elements) is incorrect.

In ASP.NET, the Page.User.Identity object contains the authentication information for the current user, including their name. The User property exposes an IPrincipal interface, and its Identity property holds the IIdentity object with details like Name and IsAuthenticated. IsInRole is a method for checking role membership, not a container for user name.

The section in ASP.NET configuration contains both and elements for controlling access rules. These elements define which users or roles are permitted or denied access to specific resources. Both elements work together to create comprehensive authorization rules.

COBOL requires user-defined names to contain at least one alphabetic character (A-Z or a-z) in any position. Names can be up to 30 characters (not 10), can be mixed case (not required lowercase), and multiple-word names typically use hyphens not underscores in COBOL convention.

xPression supports multiple data source formats for customer data including XML files, relational database systems (RDB), and XQuery files. This allows flexibility in integrating with different data storage systems and formats.

In QTP's descriptive programming, Index is 0-based, so Index:=1 refers to the second occurrence of a WebEdit object on the page. Index:=0 would be the first WebEdit. This indexing allows selecting specific instances when multiple objects with similar descriptions exist on the same page.

ClassPathXmlApplicationContext loads bean definitions from XML files on the classpath. Unlike FileSystemXmlApplicationContext (which uses file system paths), it treats paths as class path resources (e.g., 'applicationContext.xml' finds it anywhere on classpath).

XML stands for eXtensible Markup Language. It was designed to be both human-readable and machine-readable, allowing users to define their own tags and document structure. The 'extensible' refers to the ability to create custom tags.

XML comments use the syntax . This is inherited from SGML and HTML. The comment cannot contain nested comments and must not contain -- within the comment text except at the end.

The XML declaration is . It's a processing instruction that must be at the very beginning of the document. The version is the only required attribute, and it uses the special and ?> delimiters characteristic of processing instructions.

A well-formed XML document must have exactly one root element that contains all other elements. This hierarchical structure ensures the document can be properly parsed. The root element acts as the container for the entire document content.

CDATA sections are delimited by and tell the XML parser to treat the enclosed content as literal character data, not markup. This is useful for including code, scripts, or text containing special characters like < and > without escaping them.

XSLT (Extensible Stylesheet Language Transformations) IS a W3C Recommendation. It has been since 1999. The statement claiming it's not a W3C Recommendation is false. XSLT is indeed a subset of XSL, uses XPath for navigation, and is written in XML syntax.

XSLT uses to iterate over node sets in an XML document. The syntax requires the xsl namespace prefix. Option A lacks the namespace prefix, while options B and D use incorrect element names (xsl:for and xsl:foreach are not valid XSLT elements).