xmlns="http://schemas.microsoft.com/client/2007"
The second declaration maps a separate XML namespace for XAML, mapping it (typically) to the x: prefix:
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
The relationship between these declarations is that XAML is a language definition, and Silverlight is one implementation that uses XAML as a language. Silverlight in particular uses a strict subset of XAML. The XAML language specifies certain language elements, and each of these should be accessible through XAML processor implementations working against the XAML namespace.
The Silverlight implementation of XAML and its intended programming model generally uses the default XML namespace for its own XAML vocabulary and uses a separate mapped prefix for the markup syntax expected in the Silverlight subset of the XAML namespace. By convention that prefix is x:, and this same x: convention is followed by project templates, sample code, and the documentation of language features within this documentation set. The XAML namespace defines several commonly used features that are necessary even for basic Silverlight-based applications. For instance, in order to join any code-behind to a XAML file through a partial class, you must name that class as the The Silverlight and XAML Namespace Declarations
Mapping to Custom Classes and Assemblies

Join the conversation! Your thoughts help the community grow.