Markup and Web Languages

CSS syntax uses the format: selector { property: value; }. The correct form is 'body { color: black; }' where 'body' is the selector, 'color' is the property, and 'black' is the value.

CSS uses the 'color' property to set text color. Properties like 'text-color', 'font-color', and 'fgcolor' do not exist in CSS specification.

The correct CSS property for making text bold is font-weight with value bold. Option A uses the correct CSS syntax with a selector (p) and property-value pair (font-weight:bold). Options B and D incorrectly use inline style syntax with font-size or text-size, which are not properties for bold text. Option C uses the non-existent property text-size.

CSS is not limited to HTML - it can style XML documents, SVG graphics, and other markup languages. The statement claims CSS can only style HTML webpages, which is false. CSS is a general-purpose styling language.

Two main CSS properties can hide elements: display:none removes the element completely from the layout, while visibility:hidden hides it visually but maintains its space in the layout. Options A and C are both correct. The 'view' property doesn't exist, and z-index only controls stacking order.

The CSS z-index property determines the stack order of elements that overlap. Elements with a larger z-index cover those with a smaller z-index. The display and position properties control layout and placement, while depth is not a valid CSS property.

XML stands for eXtensible Markup Language, where the 'X' represents 'eXtensible' indicating that users can define their own custom tags and markup structures. This extensibility is what distinguishes XML from fixed markup languages like HTML. Options A, B, and C are made-up expansions.

XML is a meta-language for defining markup languages (option B), meaning it provides rules for creating custom tag sets rather than having fixed tags. XML is indeed a restricted form of SGML (option C), designed to be simpler while retaining SGML's extensibility. Option A is false because XML's tag semantics and tag sets are not fixed.

XML requires all elements to have closing tags (A) and be properly nested (C). Attribute values must be quoted (D). However, XML tags are case-sensitive but not required to be lowercase (B is false) - 'Name' and 'name' are different tags, but uppercase is valid. These rules ensure well-formed XML documents.

XML comments are not part of the document's textual content - they are metadata. XML processors are NOT required to pass comments to applications, and applications typically cannot access them through standard DOM/SAX parsing APIs. This distinguishes comments from actual document data.

The XML version declaration must use the processing instruction syntax with both opening and closing question marks: . Option A incorrectly closes with />, which is only used for empty elements. Option C omits the required question marks. The declaration must appear at the very start of an XML document.

XML parsers preserve whitespace in documents by default unless explicitly configured to trim it. The XML specification treats whitespace as significant content, not something to be automatically truncated. This is different from HTML where whitespace is often normalized.

XML element names must follow strict naming rules. They cannot start with a number (7lastname is invalid) and cannot contain spaces (last name is invalid). Valid names like lastname and last_name follow the rules: starting with a letter or underscore, and containing only letters, digits, hyphens, underscores, or periods.

XML element names must follow specific rules: they cannot start with numbers or punctuation characters (statement A is true), and they cannot start with 'xml' in any case combination as this is reserved (statement B is true). Statement C is false because spaces are not allowed in XML names. Therefore, 'All the above' (D) is incorrect.