<?xml version="1.0" encoding="UTF-8" ?>
<html 
	xmlns="http://www.w3.org/1999/xhtml" 
	xmlns:html="http://www.w3.org/1999/xhtml" 
	xmlns:abstract="http://unique-url/abstract">

	<head>
		<link rel="stylesheet" href="html.css" type="text/css" />
		<link rel="stylesheet" href="article.css" type="text/css" />
		<link rel="stylesheet" href="general.css" type="text/css" />
	</head>

	<body>
		<div id="wrapper">
			<div class="box">
				<h2>This is an example of very cool XHTML/CSS markup</h2>
				<p>Below is custom XML in an XHTML page for which I have defined a namespace and then targeted that 
				namespace in the CSS.</p>
			</div>
			
			<abstract:article id="cssNamespaces" class="box" xml:lang="en">
				<abstract:title>CSS Namespaces</abstract:title>
			
				<abstract:introduction>
					<html:p>
						Why shouldn't we inject XML directly into webpages?  Is there even any point in transforming it?
					</html:p>
				</abstract:introduction>
			
				<abstract:body>
					<abstract:subtitle>Why XML combined with CSS namespaces will dominate in the years to come</abstract:subtitle>
					<html:p>
						If you observe the source code of this page, you will find that this box is merely an article
						that looks like a box.  It has content which is nicely HTML formatted, because in my markup I
						explicitly use the HTML namespace to declare paragraphs, lists, you name it.
					</html:p>
					<html:p>
						However, the <code>article</code> itself is of the <code>abstract</code> namespace and gives absolutely no
						inkling as to how it is to be displayed.  An <code>article</code> can contain a <code>title</code>, an
						<code>introduction</code> (full of HTML markup) and a <code>body</code> (which contains a 
						<code>subtitle</code> and HTML markup thereafter).  We do not run into problems with using 
						<code>body</code> more than once because the two <code>body</code> tags belong to separate namespaces
						(HTML and <code>abstract</code>).
					</html:p>
				</abstract:body>
				
				<abstract:conclusion>
					<html:p>
						So next time you are writing up XSLT perhaps you should ask yourself - how many browsers support
						CSS namespaces?
					</html:p>
				</abstract:conclusion>
			</abstract:article>
			
			<abstract:article id="flyingCats" class="box" xml:lang="en">
				<abstract:title>Flying Cats</abstract:title>
			
				<abstract:introduction>
					<html:p>Introduction to my idea</html:p>
				</abstract:introduction>
			
				<abstract:body>
					<abstract:subtitle>Why I like my idea</abstract:subtitle>
					<html:p>I like the idea of flying cats because they would be fun and probably a little bit dangerous</html:p>
				</abstract:body>
			</abstract:article>
			
			<abstract:article id="cheapToasters" class="box" xml:lang="en">
				<abstract:title>Cheap Toasters</abstract:title>
			
				<abstract:introduction>
					<html:p>Have you ever been pissed off at the price of toasters?  I have...</html:p>
				</abstract:introduction>
			
				<abstract:body>
					<abstract:subtitle>Why toasters should be cheaper</abstract:subtitle>
					<html:p>Not everyone can afford toasters.  Paying alot for a toaster leads to the following:</html:p>
					<html:ul>
						<html:li>No money for Icy Poles</html:li>
						<html:li>Excessive angst</html:li>
						<html:li>General disillusion regarding toast</html:li>
					</html:ul>
				</abstract:body>
			</abstract:article>
		</div>
	</body>
</html>
