Standards bodies: Is the World Wide Web Consortium (W3C) the primary standards body for HTML, while HTTP is primarily standardized elsewhere?

Difficulty: Easy

Correct Answer: Incorrect

Explanation:


Introduction / Context:
Web technologies are standardized by different organizations. Understanding who owns which standard helps avoid confusion about protocol versus markup languages.



Given Data / Assumptions:

  • HTML is standardized by the W3C (and WHATWG for the living standard in modern practice).
  • HTTP, the transport protocol for the web, is standardized by the Internet Engineering Task Force (IETF).
  • The statement claims W3C is the chief standards body for both HTTP and HTML.


Concept / Approach:
Separate concerns: markup vs. protocol. W3C focuses on web standards like HTML, CSS, DOM, and accessibility guidelines. HTTP specifications (methods, headers, status codes, semantics) are IETF RFCs. Therefore, attributing HTTP standardization to W3C is incorrect, even though W3C is central to HTML.



Step-by-Step Solution:

Identify HTML steward: W3C (historically; modern living standard maintained with WHATWG).Identify HTTP steward: IETF via RFCs.Evaluate claim: “W3C is chief standards body for HTTP and HTML.”Conclude: false, because HTTP is IETF; statement over-assigns to W3C.


Verification / Alternative check:
Check the provenance of HTTP/1.1, HTTP/2, and HTTP/3 (RFCs by IETF) versus HTML specs (W3C/WHATWG).



Why Other Options Are Wrong:

  • Correct or XHTML-only would still incorrectly credit HTTP to W3C.
  • Browser choice does not affect the standards bodies.


Common Pitfalls:
Assuming a single body governs all web technologies; conflating HTML (content) with HTTP (transport).



Final Answer:
Incorrect

Discussion & Comments

No comments yet. Be the first to comment!
Join Discussion