Challenge 1: Read a SOAP Envelope — Possible Solution
====================================================================

HEADER
------------------------------
  <AuthToken>abc123</AuthToken>

This is metadata about the request, not part of the actual operation
being asked for — in this case, an authentication token identifying
who's making the call. The Header is optional in SOAP generally, but
when present, it typically carries this kind of cross-cutting
information (auth, session IDs, tracing info) rather than the
operation's actual data.

BODY
------------------------------
  <GetWeather>
    <City>London</City>
  </GetWeather>

This is the actual payload — the real content of the request.

THE OPERATION BEING INVOKED
------------------------------
The operation is GetWeather, and it's being called with one
parameter: City = "London". This is the SOAP equivalent of asking
"what's the weather in London?" — the same underlying request as
Chapter 1's original weather example, just expressed in SOAP's
XML envelope/header/body structure instead of a plain JSON body.

WHY THIS WORKS AS AN ANSWER
------------------------------
The key skill here is not getting overwhelmed by the XML tags and
instead recognizing the three-part shape every SOAP message shares:
Envelope wraps everything, Header carries metadata ABOUT the request
(separate from what's actually being asked), and Body carries the
actual operation name and its parameters. Once you can reliably spot
those three parts, reading an unfamiliar SOAP message becomes much
less intimidating.