<pre> 
&lt;?xml-stylesheet type="text/css" href="04article.css"?>
&lt;document xmlns:xlink="http://www.w3.org/1999/xlink">
&lt;banner>Recursions and Ruminations&lt;/banner>
  &lt;page>
    &lt;header>
      &lt;title>Will Web Services Break the Semantic Web?&lt;/title>
      &lt;author>Kurt Cagle&lt;/author>
      &lt;primaryLink>http://www.kurtcagle.net/articles/brokenSemantics.xml
                                                                 &lt;/primaryLink>
    &lt;/header>
    &lt;body>
      &lt;para>The Semantic Web has been a central concept in web development since
        Tim Berners Lee's seminal paper on the subject, &lt;jump 
        xlink:href="http://www.w3.org/DesignIssues/Semantic.html"
        xlink:type="simple" xlink:show="replace">A roadmap to the Semantic
        Web&lt;/jump> in 1998 (with a more popular description of the Semantic Web
        in &lt;jump xlink:href="http://www.scientificamerican.com/2001/0501issue/
       0501berners-lee.html" xlink:type="simple" xlink:show="replace">Scientific
        American&lt;/jump> in 1999.In it he posited that while the World Wide Web 
        has become largely readible to people, no consistent mechanism existed 
        for being able to create associations between different types of data 
        that could be used to make inferences. The ability to identify a block 
        of data as being a "thing" of a certain type is crucial to being able to 
        manipulate that thing. Thus, ultimately, the purpose of the semantic web 
        (as he saw it) was to provide an architecture that would not only make 
        it possible to objectify the web but to do so in a way that required 
        relatively little human intervention.
      &lt;/para>
      &lt;para>The original vision that Berners-Lee had of this Semantic web 
        depended upon a standard that is still relatively obscure today, though 
        it is growing in popularity. The Resource Description Framework 
        language, or RDF, can seem fairly abstruse -- it's primary purpose is to
        provide a framework for describing the associations between one or more 
        resources on the web. A simple relationship, &lt;term>equivalence&lt;/term> 
        for instance, could be used to indicate that an XML element in one 
        schema (such as a &lt;element>lastname&lt;/element>) was equivalent to a 
        &lt;element>familyName&lt;/element> element in a different schema. By having 
        this relationship clarified, it means that if a program could read 
        &lt;element>lastname&lt;/element> elements, they could work with 
        &lt;element>familyName&lt;/element> elements in the same way, even if the rest 
        of the schema was very different.
      &lt;/para>
      &lt;!-- additional content -->
    &lt;/body>
  &lt;/page>
&lt;/document>


</pre>