Silverlight XAML - does the XMLNS actually go external?

XML namespaces are URLs, but in most cases, they don't correspond to actual websites, or documentation or anything. They basically serve to provide a unique identifier for XML elements, as long as everyone cooperates an uses a domain name that they own as part of the URL. In the early days, whoever came up with using URLs for xmlns's may have intended for people to post documentation at the URLs, but nobody really does that XML parsers do not visit these URLs at any point, they are basically just identifiers.

XML namespaces are URLs, but in most cases, they don't correspond to actual websites, or documentation or anything. They basically serve to provide a unique identifier for XML elements, as long as everyone cooperates an uses a domain name that they own as part of the URL. In the early days, whoever came up with using URLs for xmlns's may have intended for people to post documentation at the URLs, but nobody really does that.

XML parsers do not visit these URLs at any point, they are basically just identifiers.

It's generally considered polite to put something useful to humans at a namespaceURI, and many do, but not Microsoft. (For some reason, their openxmlformats. Org domain kicks me out to an advertisement for XBoxes at MSN Entertainment.In Spanish.

Handy. ) – bobince Oct 8 '10 at 0:21.

No, it does not go out to microsoft. Com (those folders don't even exist), and yes, that makes these basically constants.

Your question has already been answered, but nobody mentioned why they are used. Not mentioned is that you can also specify a namespace via an assembly reference, but that would mean you would need one namespace per assembly. The Silverlight libraries are spread out over multiple assemblies (more than just the example xmls entries above indicates).

Using a "constant" as you rightly call them as the namespace means that multiple assemblies can be referenced with a single shared namespace. This saves on a large number of separate xmlns entries, but does introduce the problem of figuring out what assemblies a namspace refers to if you only have the page source :).

XML namespaces are URLs, but in most cases, they don't correspond to actual websites, or documentation or anything. They basically serve to provide a unique identifier for XML elements, as long as everyone cooperates an uses a domain name that they own as part of the URL. In the early days, whoever came up with using URLs for xmlns's may have intended for people to post documentation at the URLs, but nobody really does that.

No, it does not go out to microsoft.com (those folders don't even exist), and yes, that makes these basically constants.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.