PUBLIC MARKS with search namespace

Note: This is the Official IANA Registry of URN Namespaces

object oriented programming in Javascript,… a small script which allows you to manage namespaces.

The http://www.w3.org/TR/REC-html40 namespace is no longer treated as an alias to http://www.w3.org/1999/xhtml

Namespaces. In the world of most Javascript, everything is global or function-scope, there seems to be no use of namespace or module-style development at all. It's possible to simulate namespaces by wrapping entire modules in an object definition, but this is usually too much of a hassle for practicality.

put something like the following into it:

@javax.xml.bind.annotation.XmlSchema(namespace = "http://wstypes.server.example.com", elementFormDefault = javax.xml.bind.annotation.XmlNsForm.QUALIFIED)

still a widespread problem with using atom: and xhtml: prefixes in Atom 1 feeds.

The XML Namespace specification adds qualified names to XML. A qualified name is a tag or attribute name that is associated with a given namespace. A namespace usually represents some kind of application domain, such as hypertext, graphics, resource descriptions, or type information. The Namespace specification allows a single XML document to contain tags and attributes from any number of namespaces, without conflicts.

# The lines output by Curly Logo weren’t being broken, everything was stuck together on one line. Turns out Firefox was letting me get away with creating (XHTML) p nodes by using “document.createElement” whereas I should really be using the XML approved “document.createElementNS” to create nodes from the XHTML namespace. So now I do.

I liked the final Namespace spec, even though it wasn't what I had originally argued for, but when you have a spec that almost *everyone* ignores or gets wrong (XSLT and SOAP excepted), it might be time to acknowledge that the problem is the spec instead of the implementors. I predict that the use of XML Namespaces will be an ongoing problem for Atom, even though it's not Atom's fault.