<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss' xmlns:gd='http://schemas.google.com/g/2005' xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-9104713783556241305</id><updated>2012-01-14T22:12:17.548-08:00</updated><title type='text'>XML Schema Blog</title><subtitle type='html'>The blog about everything XML and XML Schema.</subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://xmlschemablog.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9104713783556241305/posts/default?max-results=100'/><link rel='alternate' type='text/html' href='http://xmlschemablog.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>Utiware Software Associate</name><uri>http://www.blogger.com/profile/00501485612132258936</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>1</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>100</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-9104713783556241305.post-4119450711342893010</id><published>2007-07-24T09:49:00.000-07:00</published><updated>2007-07-23T22:40:21.192-07:00</updated><title type='text'>Welcome to SchemaXplainer's Blog</title><content type='html'>Greetings, and thanks for visiting.&lt;br /&gt;&lt;br /&gt;This Blog is run by the hardworking and dedicated staff at &lt;a href="http://www.schemaxplainer.com/"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_0"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_0"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_0"&gt;Utiware&lt;/span&gt;&lt;/span&gt;&lt;/span&gt; &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_1"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_1"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_1"&gt;SchemaXplainer&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/a&gt;. Our main goal it to provide information regarding the challenges surrounding XML and XML &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_2"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_2"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_2"&gt;Schemas&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;. Our other goal is to plug our website and make our bosses happy -- so that they will give us big raises, or at least send out for pizza more often.&lt;br /&gt;&lt;br /&gt;The reality is that XML &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_3"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_3"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_3"&gt;Schemas&lt;/span&gt;&lt;/span&gt;&lt;/span&gt; can be a source of great professional suffering. They are becoming an increasingly common means of business-to-business communication and e-government functionality. But, because they are relatively new, many highly skilled professionals lack experience with them. In fact, you may have had the experience of having a schema-related project dumped in your lap at work. There you sit, with a big pile of mysterious XML code... just &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_4"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_4"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_4"&gt;lookin&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;' back at you. And, of course, your boss thinks it all ought to be easy. In fact, that's how we got involved with XML &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_5"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_5"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_5"&gt;Schemas&lt;/span&gt;&lt;/span&gt;&lt;/span&gt; ourselves...&lt;br /&gt;&lt;br /&gt;But, there is no reason for you to have to suffer like we did... XML &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_6"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_6"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_6"&gt;Schemas&lt;/span&gt;&lt;/span&gt;&lt;/span&gt; don't need to be big ugly piles of mystery XML code. In fact, they really do make perfect sense, once you get to know them. Indeed, that's why &lt;a href="http://www.schemaxplainer.com/"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_7"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_7"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_7"&gt;SchemaXplainer&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/a&gt; exists (see... two plugs in one post!). Because we feel your pain, &lt;a href="http://www.schemaxplainer.com/"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_8"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_8"&gt;SchemaXplainer&lt;/span&gt;&lt;/span&gt;&lt;/a&gt; is totally free and provides a host of XML Schema analyses (not just documentation) to help you gain control over your XML &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_9"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_9"&gt;Schemas&lt;/span&gt;&lt;/span&gt; and make you look extra cool. &lt;a href="http://www.schemaxplainer.com/"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_10"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_10"&gt;SchemaXplainer&lt;/span&gt;&lt;/span&gt;&lt;/a&gt; has &lt;a href="http://www.schemaxplainer.com/Analytics.aspx"&gt;60 Analytic criteria&lt;/a&gt; which lets you analyze your XML &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_11"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_11"&gt;Schemas&lt;/span&gt;&lt;/span&gt; from a variety of angles, and answer any question that can be asked of them.&lt;br /&gt;&lt;br /&gt;But, enough about &lt;a href="http://www.schemaexplainer.com/"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_8"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_12"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_12"&gt;SchemaXplainer&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/a&gt;... this Blog will actually focus on everything XML and XML Schema. Our first series will examine some of the most common troublesome aspects of XML &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_9"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_13"&gt;&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_13"&gt;Schemas&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;.&lt;br /&gt;&lt;br /&gt;Thanks for visiting... and come back soon.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9104713783556241305-4119450711342893010?l=xmlschemablog.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://xmlschemablog.blogspot.com/feeds/4119450711342893010/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=9104713783556241305&amp;postID=4119450711342893010' title='31 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9104713783556241305/posts/default/4119450711342893010'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9104713783556241305/posts/default/4119450711342893010'/><link rel='alternate' type='text/html' href='http://xmlschemablog.blogspot.com/2007/07/welcome-to-schemaxplainers-blog.html' title='Welcome to SchemaXplainer&apos;s Blog'/><author><name>Utiware Software Associate</name><uri>http://www.blogger.com/profile/00501485612132258936</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>31</thr:total></entry></feed>
