Web Technologies Quiz: HTML, XML, and Web Services

Standard XML defines exactly 5 predefined entity references for special characters: amp, lt, gt, apos, and quot. Any other entities must be explicitly declared in a DTD or schema.

XML stands for eXtensible Markup Language, not 'eXtensible Modeling Language'. The statement incorrectly substitutes 'Modeling' for 'Markup', so it's false.

Every well-formed XML document MUST have exactly one root element that contains all other elements. This is a fundamental requirement of XML structure.

Unlike HTML, which typically collapses whitespace, XML preserves all white spaces in element content. Applications parsing XML receive the exact spacing written by the author unless explicitly trimmed.

This XML has two errors: (1) the opening tag doesn't match the closing tag (XML is case-sensitive), and (2) it's not a complete document - missing root element and XML declaration.

XML element names cannot contain the $ character. Valid names can only contain letters, digits, underscores, hyphens, and periods, but must start with a letter or underscore. The $ makes this invalid.

The correct syntax for referring to a stylesheet is <xml-stylesheet type="text/xsl" href="new.xsl"?>, NOT 'stylesheet'. This is a processing instruction, not a regular element.

WSDL stands for Web Services Description Language. It is an XML-based language used to describe web services, including their location, available methods, and input/output parameters. Options B, C, and D are incorrect variations.

UDDI stands for Universal Description, Discovery, and Integration. It is an XML-based registry for businesses to publish and discover web services. Options B and C are incorrect - it's 'Universal' not 'Unit', and 'Integration' not 'Display'.

SOAP stands for Simple Object Access Protocol. It is a protocol for exchanging structured information in web services using XML. Options B and C are incorrect variations - it's 'Simple' and 'Access', not 'Sample' or 'Opposite'.

SOAP uses XML as its message format. SOAP envelopes are XML documents that contain the message data. HTML and DHTML are for web pages, CSS is for styling, and none of these are the message format for SOAP.

Interoperability is the ability of different systems or components to work together without restriction. When a service component is platform-free (can work on any platform), it enables interoperability across different systems and technologies.

Java Message Service (JMS) is a messaging API that allows Java applications to create, send, receive, and read messages asynchronously. It is a messaging middleware standard, not a web service protocol like SOAP or REST.

In data communication and programming, a 'message' is the unit of data transmitted between entities, containing the actual information or payload intended for the recipient.

In web services (specifically using XML and WSDL), namespaces serve the same purpose as packages in programming languages - they organize elements and prevent naming conflicts. Namespaces uniquely identify elements in XML documents.

HTML stands for HyperText Markup Language. It is the standard markup language for creating web pages and web applications, defining the structure and layout of a document.

SOAP and REST are the two most widely used protocols for web services. SOAP uses XML for structured messaging, while REST uses HTTP methods (GET, POST, PUT, DELETE) with various data formats. TCP and IP are lower-level networking protocols, not web service protocols.

While SOAP and REST are architectural styles, HTTP/HTTPS are the underlying protocols used for asynchronous communication in web services (often via AJAX or callbacks). However, JMS is also a common choice for enterprise async messaging.