index.html 52.7 KB

Raw Blame History Permalink

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
<head>
  <title>Ontology of Rhetorical Blocks (ORB)</title>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<meta content="text/html; charset=utf-8" http-equiv="Content-Type"/>

  <link href="default.css" rel="stylesheet" type="text/css"/>
  <link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-IG-NOTE"/>
</head>

<body>
<div class="head"> <!--begin-logo-->
   <p id="x"><a href="http://www.w3.org/"><img alt="W3C" height="48"
    src="http://www.w3.org/Icons/w3c_home" width="72"/></a></p> <!--end-logo-->

   <h1>Ontology of Rhetorical Blocks (ORB)</h1>

   <h2 class="no-num no-toc" id="longstatus-date">W3C Interest Group Note 20 October 2011</h2>

   <dl>
    <dt>This version:</dt>
    <dd><a href="http://www.w3.org/TR/2011/NOTE-hcls-orb-20111020/">http://www.w3.org/TR/2011/NOTE-hcls-orb-20111020/</a></dd>
    <dt>Latest version:</dt>
    <dd><a href="http://www.w3.org/TR/hcls-orb/">http://www.w3.org/TR/hcls-orb/</a></dd>
    <dt>Editors:</dt>
    <dd><a href="http://www.paolociccarese.info/">Paolo Ciccarese</a>, Massachusetts General Hospital / Harvard Medical School &lt;<a href="mailto:paolo.ciccarese@gmail.com">paolo.ciccarese@gmail.com</a>&gt;</dd>

    <dd><a href="http://www.tudorgroza.org/">Tudor Groza</a>, School of ITEE, The University of Queensland / Digital Enterprise Research Institute (DERI), Galway &lt;<a href="mailto:tudor.groza@uq.edu.au">tudor.groza@uq.edu.au</a>&gt;</dd>
    <dt>Contributors:</dt>
    <dd>Tim Clark, Massachusetts General Hospital / Harvard Medical School</dd>
    <dd>Anita De Waard, Elsevier Laboratories</dd>
   </dl>

   <!--begin-copyright-->
   <p class="copyright" id="copyright-copy-year-2000-w3creg-mit-erci"><a
    href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright"
    rel="license">Copyright</a> &copy; 2011 <a
    href="http://www.w3.org/"><acronym title="World Wide Web
    Consortium">W3C</acronym></a><sup>&reg;</sup> (<a
    href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute
    of Technology">MIT</acronym></a>, <a href="http://www.ercim.eu/"><acronym
    title="European Research Consortium for Informatics and
    Mathematics">ERCIM</acronym></a>, <a
    href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a
    href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
    <a
    href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a>

    and <a
    href="http://www.w3.org/Consortium/Legal/copyright-documents">document
    use</a> rules apply.</p>
   <!--end-copyright-->
   <hr title="Separator for header"/>
</div>

  <h2 class="no-num no-toc" id="abstract">Abstract</h2>

  <p id="this-css-image-values-and-replaced-conte">The Ontology of Rhetorical Blocks is a formalization capturing the coarse-grained rhetorical structure of scientific publications. This note is designed to provide a general overview of the motivation and use-cases supporting ORB, in addition to the actual conceptual elements, as well as, practical examples of how to use it in conjunction with different representation languages.</p>

  <h2 class="no-num no-toc" id="status">Status of this document</h2>
  <!--begin-status-->

<p><em>This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the <a href="http://www.w3.org/TR/">W3C technical reports index</a> at http://www.w3.org/TR/.</em></p>

<p id="this-document-was-produced-by">The document was produced by the the <a href="http://esw.w3.org/HCLSIG/SWANSIOC">Scientific Discourse Task Force</a>,
    part of the <a href="http://www.w3.org/2001/sw/hcls/">
   	Semantic Web in Health Care and Life Sciences Interest Group (HCLS)</a>,
    part of the <a href="http://www.w3.org/2001/sw/">W3C Semantic Web Activity</a>
    (<a href="http://www.w3.org/2008/05/HCLSIGCharter">see charter</a>).
    Comments may be sent to the <a href="http://lists.w3.org/Archives/Public/public-semweb-lifesci/">publicly archived</a>
    <a href="mailto:public-semweb-lifesci@w3.org">public-semweb-lifesci@w3.org</a> mailing list.</p>

<p>Publication as an Interest Group Note does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.</p>

<p>The <a href="http://www.w3.org/2004/01/pp-impl/38539/status">IPR status</a> of information provided in this document is in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20030520.html#sec-Disclosure">Section 6</a> of the W3C Patent Policy. The disclosure obligations of the Participants of this group are described in the <a href="http://www.w3.org/2011/09/HCLSIGCharter#patentpolicy">charter</a>.</p>
<!--end-status-->
<h2 class="no-num no-toc" id="contents">Table of Contents</h2>

  <!--begin-toc-->
  <ul class='toc'>
   <li><a href="#intro"><span class="secno">1.
    </span>Introduction</a>
    <ul class='toc-sub'>

     <li><a href="#target-audience"><span class='secno'>1.1. </span>Document Scope and Target Audience</a></li>
     <li><a href="#document-conventions"><span class='secno'>1.2. </span>Document Conventions</a></li>
      </ul></li>
 <li><a href="#use-cases"><span class="secno">2.
    </span>Use Cases</a>
<ul class='toc-sub'>

     <li><a href="#use-case-1"><span class='secno'>2.1. </span>Use Case #1: Finding appropriate information within publications</a></li>
     <li><a href="#use-case-2"><span class='secno'>2.2. </span>Use Case #2: Publication authoring</a></li>
      </ul></li>
<li><a href="#ontology"><span class="secno">3.
    </span>The Ontology</a>
    <ul class='toc-sub'>

     <li><a href="#onto-header"><span class='secno'>3.1. </span>Header</a></li>
     <li><a href="#onto-body"><span class='secno'>3.2. </span>Body</a></li>
     <li><a href="#onto-tail"><span class='secno'>3.3. </span>Tail</a></li>
      </ul></li>
     <li><a href="#extensions"><span class="secno">4.
    </span>ORB Extensions</a></li>
    <li><a href="#using"><span class="secno">5.
    </span>Using ORB</a>
    <ul class='toc-sub'>
    	 <li><a href="#using-xml"><span class='secno'>5.1. </span>With XML</a></li>
         <li><a href="#using-rdf"><span class='secno'>5.2. </span>With RDF</a></li>
         <li><a href="#using-rdf-html"><span class='secno'>5.3. With </span>HTML and RDF</a></li>
         <li><a href="#using-rdfa"><span class='secno'>5.4. With </span>HTML and RDFa</a></li>
    </ul></li>
   <li class="no-num" id='acknowledgments-'><a
    href="#acknowledgments">Acknowledgments</a></li>

   <li class='no-num' id='references-normative-references-informat'><a
    href="#references">References</a></li>
  </ul>
  <!--end-toc-->

 <div>
   <h2 id="intro"><span class="secno">1. </span>Introduction</h2>

   <p id='_1'>In the last the decade, the consistently growing number of scientific publishing spheres (journals, conferences, workshops, etc) led to a significant increase in the amount of publications, with the biomedical and pharmaceutical domains being some of the most heavily affected. For example, MedLine now hosts over 18 million articles, and has a growth rate of 0.5 million / year (around 1300 articles/day) <a href="#tsuji2009">[Tsuji2009]</a>. This makes the process of finding and associating relevant work in a particular field a cumbersome task. </p>
   <p>One of the key issues behind this information overload problem is the inefficiency proved by the current indexing mechanisms based solely on syntactic resources. Scientific publications represent collections of artefacts contributed by authors, at different granularity levels. For example, they state claims, positions and arguments in relation to their own achievements, or the results achieved by other researchers (corresponding to a fine-grained level), or synthesise background information or experimental results (corresponding to a coarse-grained level). These epistemic items represent the key to decoding the rhetoric captured within the publications' content, and thus identifying and acquiring them could lead to novel ways of dealing with the information overload. Additionally, they may also contain important domain knowledge that can then be directly coupled with the rhetoric and argumentation semantics of the content.</p>
<p>Our goal is to research and develop a formal structure able to represent all these discourse knowledge items. However, in the context of this note, we focus only on modeling larger spans of text that carry a rhetorical role, and thus forming the coarse-grained rhetorical structure of the publication, via the Ontology of Rhetorical Blocks. At a later stage, we will present a formalization also for the fine-grained rhetorical structure built by means of parts of sentences, sentences or phrases.</p>

    <h3 id='target-audience'><span class='secno'>1.1. </span>Document Scope and Target Audience</h3>
   <p id='_1_1'>This document describes the Ontology of Rhetorical Blocks (ORB). ORB can be used to add semantics to the structure of newly-written scientific articles as well as annotating already existing ones.</p>
    <h3 id='document-conventions'><span class='secno'>1.2. </span>Document Conventions</h3>
   <p id='_1_2'>The following namespace prefix bindings are assumed unless otherwise stated:</p>
   <table style="border-collapse: collapse; border-color: #000000" border="1" cellpadding="5">
	<tr><th>Prefix</th>				<th>URI</th>	  <th>Description</th></tr>
	<tr><td><code>rdf:</code></td>
	<td><code>http://www.w3.org/1999/02/22-rdf-syntax-ns#</code></td>	<td>The RDF Vocabulary</td></tr>

	<tr><td><code>rdfs:</code></td>			<td><code>http://www.w3.org/2000/01/rdf-schema#</code></td>	<td>The RDF Schema vocabulary</td></tr>
	<tr><td><code>xsd:</code></td>			<td><code>http://www.w3.org/2001/XMLSchema#</code></td>	<td>XML Schema</td></tr>
	<tr><td><code>dc:</code></td>			<td><code>http://purl.org/dc/elements/1.1/</code></td>
	  <td>Dublin Core Metadata Element Set, Version 1.1</td>
     </tr>

    <tr><td><code>dcterms:</code></td>			<td><code>http://purl.org/dc/terms/</code></td>
	<td>Dublin Core Metadata Terms</td>
	</tr>
    <tr>
    	<td><code>orb:</code></td>
        <td><code>http://purl.org/orb/</code></td>
        <td>Latest version of the ORB ontology</td>
    </tr>
  </table>

</div>

 <h2 id="use-cases"><span class="secno">2. </span>Use Cases</h2>
<p id='_2'>The range of activities that researchers usually perform is quite broad, and usually context dependent. To simplify the description, one can classify these contexts into: actual research, project administration / management, dissemination and supervision. While this classification is quite naive and far from being unique, it is good enough to serve our purposes. From the four above-mentioned contexts, three rely on "using" scientific literature to achieve specific goals. For example, consulting the state of the art for comparative purposes (actual research), writing about own research achievements (dissemination) or teaching students how to perform research and disseminate its results (supervision). Consequently, in one way or another, publications represent the center-piece of our daily research activities, and their rhetorical and argumentation structures represent key elements in decoding the message that the authors tried to convey. In the following we present a series of use cases showing how the externalization of these structures can improve the current research workflow.</p>

 <h3 id="use-case-1"><span class="secno">2.1. </span>Use Case #1: Finding appropriate information within publications</h3>
<p id='_2_1_1'> Composing a literature survey requires a thorough analysis of the
targeted scientific area, and hence the understanding of the
contribution brought by the existing publications in that particular
domain. At the same time, understanding such contributions requires
one to read each and every interesting paper, which could represent a
quite overwhelming task. Alternatively, one could use a search engine
to find publications that may contain some specific keywords, however
this will result in a set of publications that might have tangential
topics to the one of interest and not to their actual contribution.</p>
<p id='_2_1_2'>Having the rhetorical block structure externalized and attached to the
digital publications would enable a richer and more expressive
searching and browsing experience. One would be able to quickly spot
the METHODS blocks within the publication and possibly resume the
reading activity only to those, thus reducing the time usually spent
on reading the entire publication. On the other hand, being able to
formulate queries for content specific only to such blocks could
already improve the quality (and possibly the quantity) of the set of
relevant publications (e.g. methods: "autosomal-dominant mutations in
APP").</p>
<p id='_2_1_3'>In practice, the externalisation process requires human or machine
annotation of the original publication, in order to create the
corresponding ORB metadata. This metadata could then reside within the
publication (subject to the publishing format - see below for an
example of using RDFa and XHTML) or outside the publication in a
metadata repository. In both cases, the publication and the metadata
should be exposed on the Web following the Linked Data principles, in
particular to enable the identification of the rhetorical blocks and
their retrievability. Hence, to get to the METHODS block of this
document one should be able to simply use the following URI:
  <code>http://www.w3.org/TR/2011/NOTE-hcls-orb-20111020/#orb-methods</code>. The actual content
negotiation process is deferred to the server that publishes the
document and/or metadata, while the interpretation of the hash-based
identification is the responsibility of the environment that renders
the publication and metadata. This last aspect is especially relevant
when one tries to address a non-existing rhetorical block, in which
case, the addressing could be interpreted as a declaration.</p>

 <h3 id="use-case-2"><span class="secno">2.2. </span>Use Case #2: Publication authoring</h3>
<p id='_2_2_1'>In general, the authoring process of a publication usually starts by creating the linear (section) structure of the publication and continues with laying the argumentative thread within this structure. This process, together with its outcome (i.e., the document), suffers from two major problems. Firstly, in the last decade, we observe a shift from printed publications to electronic publications. While for the former, the presence of the typical linear (print-driven) structure is compulsory, the latter could make use of novel structuring approaches, that would enable the externalization of both the semantics of the content and its argumentative support. Secondly, considering the current information overload, the existence of an explicit semantic structure within the publication (created already at authoring time) would reduce the overhead of post-processing the publications in order to externalize it.</p>

<p id='_2_2_2'>The process of making the semantics explicit can be easily improved by using a fixed rhetorical structure. One could start authoring the publication from a given template of a rhetorical structure, following a core model, which could, at a later stage, be customized according to the domain of the publication. For example, if the publication is in the Experimental Biology domain, the core model only would be sufficient, while if the publication is in Mathematics, several specific modules capturing particular rhetorical blocks could be added. This scenario has two advantages: firstly, the author would have from the start a clear structure which to fill in, and secondly, each block of the structure would have a clear rhetorical role (unlike today's publication sections), making it easy to mine, retrieve and browse.</p>

    <h2 id="ontology"><span class="secno">3. </span>The Ontology</h2>
<p id='_3_1'>Subject to the scientific field, the coarse-grained rhetorical structure of scientific publications can take several shapes. While in the Computer Science domain we would commonly find blocks carrying rhetorical roles such as Scenario, Related Work or Evaluation, in the biomedical field we would encounter others, like Background, Experimental Results or Discussion. In principle, most of these blocks can be found in the vast majority of the domains, however, with slightly different names. As such, independently of the domain, the coarse rhetoric emerging from the publications' content will have a commonly shared semantics, but will be materialized in different domains using different terminologies.</p>
<p id='_3_2'>The Ontology of Rhetorical Blocks (ORB) aims at providing a minimalistic set of common rhetorical blocks that can be leveraged from scientific publications. At the same time, it acts as an entry point to the fine-grained semantics not only of the actual publication content, but also of the publication as a document, thus capturing its provenance and external references information. Consequently, the ontology models a publication by means of three artefacts: the Header, the Body and the Tail. As described in the following sections, out of these artefacts only the Header will be materialised into an ontological entity, the rest being defined by their actual rhetoric components.</p>

 <h3 id="onto-header"><span class="secno">3.1. </span>Header</h3>
 <table class="propdef">
  	<tbody>
   		<tr>
    			<th style="width: 10em;">Class</th>
    			<th style="width: 50em;">Definition</th>
			</tr>
          <tr>
    			<td>orb:Header</td>
    			<td>The part of the publication that models, or captures, meta-information about the publication, including fields such as title, authors, affiliations, publishing venue or abstract.</td>
			</tr>
       </tbody>
  </table>

<p id='_3_1_1'>Every scientific publication, independently of its subject area, is accompanied by a Header. The Header of the publication contains meta-information about it, describing the provenance and the rhetorical summary. Hence, it will capture the publication's title, authors, affiliations, publishing venue, but also the abstract, as a rhetorical summary.</p>

 <!--
 <pre>Amyloid Precursor Protein Mediates a Tyrosine-kinase Dependent Activation Response in Endothelial Cells
S.A. Austin, M.A. Sens, and C.K. Combs
J Neurosci. 2009 November 18; 29(46): 14451-62. </pre>

<div class="example">
  <p>The article bibliographic object using Dublin Core <a href="#dcmi">[DCMI]</a>, Publishing Requirements for Industry Standard Metadata  (PRISM)
       <a href="#prism">[PRISM]</a> and Bibliographic Ontology (BIBO) <a href="#bibo">[BIBO]</a>:<pre>
 &lt;info:doi/10.1523/JNEUROSCI.3107-09.2009&gt; a bibo:Article ;
    dc:title "Amyloid Precursor Protein Mediates a Tyrosine-kinase Dependent Activation Response in Endothelial Cells."@en ;
    dc:date "2009-11-18" ;
    dc:identifier "doi:10.1030/03054" ;
    dc:isPartOf &lt;urn:issn:02706474&gt;  ;
    prism:doi "doi:10.1030/03054" ;
    prism:volume "29" ;
    prism:issueIdentifier "46" ;
    prism:startingPage "14451" ;
    prism:endingPage "14462" ;
    dc:creator &lt;http://examples.net/contributors/3&gt; ;
    dc:creator &lt;http://examples.net/contributors/2&gt; ;
    dc:creator &lt;http://examples.net/contributors/1&gt; ;
    bibo:authorList ( &lt;http://examples.net/contributors/3&gt; &lt;http://examples.net/contributors/2&gt; &lt;http://examples.net/contributors/1&gt ) .

&lt;urn:issn:02706474&gt; a bibo:Journal ;
    dc:title "The Journal of neuroscience : the official journal of the Society for Neuroscience"@en ;
    bibo:shortTitle "J Neurosci"@en .

&lt;http://examples.net/contributors/3> a foaf:Person;
    foaf:name "C.K. Combs" ; .
      </pre>
    <p>In the above example we used Doublin Core Metadata Element Set <a href="#dcmi">[DCMI]</a> as the PRISM Subset of the Dublin Core Namespaces suggests <a href="#prism-dc">[PRISM-DC]</a>. It is always possible to drop the Dublin Core vocabulary in favor of the newest Doublin Core Terms vocabulary <a href="#dcmi-terms">[DCMI-TERMS]</a>.</p>
</div>


<div class="example">
        <p>Dublin Core and Bibliographic Ontology (BIBO)
        <pre>
 &lt;info:doi/10.1523/JNEUROSCI.3107-09.2009&gt; a bibo:Article ;
    dc:title "Amyloid Precursor Protein Mediates a Tyrosine-kinase Dependent Activation Response in Endothelial Cells."@en ;
    dc:date "2009-11-18" ;
    dc:isPartOf &lt;urn:issn:15292401&gt; ;
    bibo:volume "29" ;
    bibo:issue "46" ;
    bibo:pageStart "14451" ;
    bibo:pageEnd "14462" ;
    dc:creator &lt;http://examples.net/contributors/3&gt; ;
    dc:creator &lt;http://examples.net/contributors/2&gt; ;
    dc:creator &lt;http://examples.net/contributors/1&gt; ;
    bibo:authorList ( &lt;http://examples.net/contributors/3&gt; &lt;http://examples.net/contributors/2&gt; &lt;http://examples.net/contributors/1&gt;) .
      </pre>
      -->
<!-- /div -->

 <h3 id="onto-body"><span class="secno">3.2. </span>Body</h3>

<p id='_3_2_1'>As mentioned above, subject to the scientific domain, the rhetorical blocks may have different names. In order to be abstract enough, yet inclined towards HealthCare and Life Sciences, ORB adopts the IMRAD (Introduction, Methods, Results And Discussion) <a href="#imrad">[IMRAD]</a> structure and terminology to define the rhetorical blocks of the Body. This structure is preferred by several scientific journals and explicitly recommended in the "Uniform Requirements for Manuscripts Submitted to Biomedical Journals: Writing and Editing for Biomedical Publication" issued by the International Committee of Medical Journal Editors (ICMJE).</p>
<p id='_3_2_2'>IMRAD <a href="#imrad-xml">[IMRAD-XML]</a>, and consequently ORB, describes the standard main structure of a scientific publication, which typically includes the following four sections in the following order:</p>

   <table class="propdef">
    	<tbody>
     		<tr>
      			<th style="width: 10em;">Class</th>
      			<th style="width: 50em;">Definition</th>
			</tr>
            <tr>

      			<td>orb:Introduction</td>
      			<td>The section describing why was the study in the publication undertaken, what was the tested hypothesis or what was the purpose of the research. It lays down the rationale behind the existence of the publication.</td>

			</tr>
             <tr>

      			<td>orb:Methods</td>
      			<td>The section describing when, where, and how was the study done. It includes the materials used as part of the study and who was included in the study groups (patients, etc.).</td>

			</tr>
             <tr>
      			<td>orb:Results</td>
      			<td>The part synthesizing the results of the study presented in the paper.</td>
			</tr>
            <tr>
      			<td>orb:Discussion</td>
      			<td>The section analyzing whether the tested hypothesis was confirmed. It also interprets the results to understand their consequences and importance. And finally, it shows how the approach and results fit to what other researchers in the field have discovered, including possible perspectives of future research.</td>
			</tr>
         </tbody>
    </table>

 <h3 id="onto-tail"><span class="secno">3.3. </span>Tail</h3>
   <p id='_3_3_1'>Similar to the Header, the Tail provides additional meta-information about the paper, however, this time in the context of external references included in the paper. Here we distinguish between two categories that define the Tail artefact:</p>
   <table class="propdef">
    	<tbody>
     		<tr>
      			<th style="width: 10em;">Class</th>
      			<th style="width: 50em;">Definition</th>
			</tr>
            <tr>
      			<td>orb:Acknowledgments</td>
      			<td>List pointing to funding bodies or individuals that contributed in a way or the other to enabling or supporting the work presented in the publication.</td>
			</tr>
            <tr>
      			<td>orb:References</td>
      			<td>External references to other works (e.g., scientific publications, websites, software) that are relevant for the content of the current publication.</td>
			</tr>
         </tbody>
    </table>

   <p id='_3_3_2'>It should be pointed out that in the context of ORB, the <i>References</i> are not limited to the usual list of citations provided by the publication. Instead, <i>References</i> denote any external resources that complement, in a way or another, the work described in the paper under scrutiny, including elements such as, data, websites, software, scientific publications, etc. There is, however, a distinction being made between references to resources and to people (or organizations), via the <i>Acknowledgments</i> concept.</p>

     <h2 id="extensions"><span class="secno">4. </span>ORB Extensions</h2>

<p id='_4_1'>As already described, the Ontology of Rhetorical Blocks provides a high-level coarse-grained rhetorical structure for scientific publications. Subject to the actual rhetorical block, this can be further specified or decomposed into finer-grained elements carrying a rhetorical role. For example, the <i>Methods</i> block could comprise elements such as <i>Purpose</i>, <i>Objects of study</i> and <i>Tools and procedures</i>. As a note, this decomposition process, or the creation of a fine-grained rhetorical structure, is currently in progress in the Scientific Discourse Task of the HCLS Working Group.
	</p>
	<p id='_4_2'>One block that particular requires more attention is the Header, as it contains clear and well-established components. In accordance with the spirit of the Semantic Web, in the context of the ORB Header, we did not re-define (or introduce recycled) terms or entities to model such information. Instead, the ORB Header should be interpreted as a container of the textual representation of the publication metadata. Hence, in the following, we propose a series of guidelines (see table below) with respect to the information that should be considered when analyzing the Header, and defer the definition of the actual elements to widely used semantic models. Also, it should be noted that the resulting metadata fields should be attached to the overall publication, and not only to the Header, in order to provide a clean semantics and to be compliant with most of the current ontologies that deal with this subject. Two examples of such ontologies are the Bibliographic Ontology (BIBO) [<a href="#bibo">BIBO</a>] and the FRBR aligned Bibliographic Ontology (FaBiO) [<a href="#fabio">FABIO</a>]. Another valuable resource in represented by the Publishing Requirements for Industry Standard Metadata (PRISM) [<a href="#prism">PRISM</a>] that makes already use of a subset of the Dublin Core namespaces [<a href="#prism-dc">PRISM-DC</a>]. More precisely, PRISM version 2.1 - published on 15 May 2009 - is in fact making use of the Dublin Core Metadata Element Set, Version 1.1 [<a href="#dcmi">DCMI</a>] and not of the latest DCMI Metadata Terms [<a href="#dcmi-terms">DCMI-Terms</a>]. </p>

	<table class="propdef">
	 	<tbody>
	  		<tr>
	   			<th style="width: 10em;">Field</th>
	   			<th style="width: 50em;">Description</th>
	  			<th style="width: 10em;">Formal definition</th>
		  </tr>
	         <tr>
	   			<td>Title</td>
	   			<td>The title of the publication.</td>
	   			<td>dc:title</td>
		  </tr>
	         <tr>
	   			<td>Author / Contributor</td>
	   			<td>Each individual that contributed to the publication. Individuals can be modeled as a foaf:Person in conjunction with the properties specified in the formal definition.</td>
	   			<td>dc:creator + prism:role + foaf:Person</td>
		  </tr>
	         <tr>
	   			<td>Affiliation</td>
	   			<td>The affiliation of each author. Can be modeled as foaf:Organization in conjunction with the properties specified in the formal definition.</td>
	   			<td>swrc:affiliation</td>
		  </tr>
	         <tr>
	   			<td>Publishing venue</td>
	   			<td>The publishing venue of the publication. Modeled in PRISM as publicationName: Title of the magazine, or other publication, in which a resource was/will be published</td>
	   			<td>prism:publicationName</td>
		  </tr>
	         <tr>
	   			<td>Date</td>
	   			<td>The publishing date of the publication.</td>
	   			<td>dc:date</td>
		  </tr>
	         <tr>
	   			<td>Abstract</td>
	   			<td>The abstract of the publication</td>
	   			<td>dcterms:abstract</td>
		  </tr>
      </tbody>
</table>

	<p id='_5_2'>Similar to the Header, the Tail's components can also be further decomposed into several finer-grained elements. For example, the <i>References</i> block will always contain an element about bibliographic citations. It may also contain elements pointing to the data used in the experiments, or even pointers to additional sets of experiments performed. However, it is important to note that, as in the case of the Header, such decompositions are not within the scope of ORB. Their definition is deferred either to a middle/fine-grained representation, or to specific models that target particular instances of scientific publications (or publishing venues).</p>

<h2 id="using"><span class="secno">5. </span>Using ORB</h2>
<p>Some examples of ORB usage are listed in the following sections. Every section is dealing with a different data format.</p>

  <h3 id="using-xml"><span class="secno">5.1. With </span>XML </h3>
  <!--
<div class="code">

        <p>Representing the <em>title</em> and <em>publication date</em> and the <em>authors</em> of this note</p>
  <pre>
&lt;dc:title&gt;Ontology of Rhetorical Blocks (ORB)&lt;/dc:title&gt;
&lt;dc:date&gt;2011-01-03&lt;/dc:date&gt;
&lt;dc:creator&gt;Paolo Ciccarese&lt;/dc:creator&gt;
&lt;dc:creator&gt;Tudor Groza&lt;/dc:creator&gt;
        </pre>
<p>Adding the role through the PRISM Contributor Role Controlled Vocabulary [<a href="#prism-rcv">PRISM-RCV</a>]: </p>
        <pre>
&lt;dc:creator prism:role=”editor”&gt;Paolo Ciccarese&lt;/dc:creator&gt;
&lt;dc:creator prism:role=”editor”&gt;Tudor Groza&lt;/dc:creator&gt;
</pre> -->
<!--
<p>In pure RDF format:</p>
<pre>
&lt;dc:creator&gt;
   &lt;foaf:Person&gt;
      &lt;foaf:name&gt;Paolo Ciccarese&lt;/foaf:name&gt;
      &lt;prism:role&gt;editor&lt;/prism:role&gt;
      ...
   &lt;/foaf:Person&gt;
&lt;/dc:creator&gt;
      </pre>
      -->
<!-- /div -->
   <p>ORB can be easily integrated in any XML format. However, as PRISM has been defined primarily for being implemented in XML, the following XML format is based on the PRISM Aggregator Message (PAM) [<a href="#prism-pam">PRISM-PAM</a>] currently used by several publishers.   </p>
   <p>The PAM format allows XHTML elements to carry the <em>prism:class=</em> attribute. Best practice is to use such attributes on the &lt;div&gt; tag when special structures are complex such as several paragraphs or a paragraph and a table [<a href="#prism-pam-guide">PRISM-PAM-GUIDE</a>]. However, as the semantic of such attribute has a structural connotation, the attribute new <em>orb:class</em> has been introduced. We believe this design choice  simplifies the rhetorical blocks declaration and introduces little risk of confusion. The ORB classes are the allowed values for the attribute <em>orb:class</em> and no further namespaces declarations are needed. We introduced also <em>orbext:class</em> to enable ORB extensions. </p>
<div class="code">
 <pre>
&lt;pam:article&gt;
    &lt;head&gt;
    	&lt;dc:identifier&gt;doi:10.1523/JNEUROSCI.3107-09.2009&lt;/dc:identifier&gt;
        &lt;dc:title&gt;Amyloid Precursor Protein Mediates a Tyrosine-kinase Dependent Activation Response in Endothelial Cells.&lt;/dc:title&gt;
        &lt;dc:creator prism:role=”writer”&gt;S.A. Austin&lt;/dc:creator&gt;
        &lt;dc:creator prism:role=”writer”&gt;M.A. Sens&lt;/dc:creator&gt;
        &lt;dc:creator prism:role=”writer”&gt;C.K. Combslt;/dc:creator&gt;
        &lt;dc:publisher&gt;The Society For Neuroscience&lt;/dc:publisher&gt;
        &lt;prism:publicationDate&gt;2009-11-18&lt;/prism:publicationDate&gt;
        &lt;prism:publicationName&gt;The Journal of Neuroscience&lt;/prism:publicationName&gt;
        &lt;prism:issn&gt;0270-6474&lt;/prism:issn&gt;
        &lt;prism:eIssn&gt;1529-2401&lt;/prism:eIssn&gt;
        &lt;prism:doi&gt;10.1523/JNEUROSCI.3107-09.2009&lt;/prism:doi&gt;
        &lt;prism:volume&gt;29&lt;/prism:volume&gt;
        &lt;prism:number&gt;46&lt;/prism:number&gt;
        &lt;prism:startingPage&gt;14451&lt;/prism:startingPage&gt;
        &lt;prism:url&gt;http://dx.doi.org/10.1523/JNEUROSCI.3107-09.2009&lt;/prism:url&gt;
        &lt;prism:copyright&gt;© 2010 The Society For Neuroscience&lt;/prism:copyright&gt;
    &lt;/head&gt;
    &lt;body&gt;
       &lt;div <strong>orb:class="Header"</strong>&gt;
          ...
          &lt;span class="citation-abbreviation"&gt;J Neurosci. &lt;/span&gt;
          &lt;span class="citation-publication-date" <strong>orbext:class="dc:date"</strong>&gt;2009 November 18; &lt;/span&gt;
          &lt;span class="citation-volume"&gt;29&lt;/span&gt;
          &lt;span class="citation-issue" &gt;(&lt;span&gt;46&lt;/span&gt;)&lt;/span&gt;
          &lt;span class="citation-flpages"&gt;: 14451.&lt;/span&gt;
          &lt;span class="fm-vol-iss-date"&gt;doi: &lt;span&gt;10.1523/JNEUROSCI.3107-09.2009&lt;/span&gt;&lt;/span&gt;
          ...

          &lt;div class="fm-title" <strong>orbext:class="dc:title"</strong>&gt;
              Amyloid Precursor Protein Mediates a Tyrosine-kinase Dependent Activation Response in Endothelial Cells.
          &lt;/div&gt;
          &lt;div class="contrib-group fm-author"&gt;
              &lt;span <strong>orbext:class="dc:creator"</strong>&gt;S.A. Austin&lt;/span&gt;,
              &lt;span <strong>orbext:class="dc:creator"</strong>&gt; M.A. Sens&lt;/span&gt;, and
              &lt;span <strong>orbext:class="dc:creator"</strong>&gt;C.K. Combs&lt;/span&gt;
          &lt;/div&gt;

          &lt;div <strong>orbext:class="dcterms:abstract"</strong>&gt;
             Amyloid precursor protein (APP) ...
          &lt;/div&gt;
       &lt;/div&gt;
       ...
       &lt;div class="sec" id="S1" <strong>orb:class="Introduction"</strong>&gt;
          &lt;div style="text-transform: none;" id="S1titletitle" class="head1 section-title"&gt;
             &lt;div&gt;Introduction&lt;/div&gt;
          &lt;/div&gt;
          &lt;div id="S1content" class="section-content"&gt;
             &lt;div id="P2" class="p p-first"&gt;
                Endothelial cells ...
             &lt;/div&gt;
             ...
          &lt;/div&gt;
       &lt;/div&gt;
       ...
    &lt;/body&gt;
 &lt;/pam:article&gt;
   </pre>
   </div>

<h3 id="using-rdf"><span class="secno">5.2. </span>With RDF</h3>
<p>As you might expect, ORB can be used to define content in  RDF format [<a href="#rdf">RDF</a>]. The following snippet is showing how to use ORB in conjunction with the Bibliographic Ontology (BIBO). A similar snippet could be defined using ORB in conjunction with the FRBR aligned Bibliographic Ontology (FaBiO). In both cases, the ORB blocks are defined as parts of the specific document, which in the following example is a journal article and therefore a <em>bibo:Article</em>.</p>
<div class="code">
<p>This is the Turtle RDF for the open access article <a href="http://www.ncbi.nlm.nih.gov/pmc/articles/PMC2820274/">Amyloid Precursor Protein Mediates a Tyrosine-kinase Dependent Activation Response in Endothelial Cells</a>. It combines ORB, Dublin Core and BIBO:
  </p>
<pre>
@prefix bibo: &lt;http://purl.org/ontology/bibo/&gt; .
@prefix dc: &lt;http://purl.org/dc/elements/1.1/&gt; .
@prefix dcterms: &lt;http://purl.org/dc/terms/&gt; .
@prefix orb: &lt;http://purl.org/orb/&gt; .

[ a bibo:Article ;
     dc:creator &quot;S.A. Austin&quot; ;
     dc:creator &quot;M.A. Sens&quot; ;
     dc:creator &quot;C.K. Combs&quot; ;
     dc:title &quot;Amyloid Precursor Protein Mediates a Tyrosine-kinase Dependent Activation Response in Endothelial Cells.&quot; ;
     dcterms:abstract &quot;Amyloid precursor protein (APP) ...&quot;
     dcterms:hasPart
         [ a <strong>orb:Header</strong> ;
             dc:description "Header content"
         ],
         [ a <strong>orb:Introduction</strong> ;
             dc:description "Introduction content"
         ]
         ...
].
 </pre>
</div>
<h3 id="using-rdf-html"><span class="secno">5.3. </span>With HTML and RDF</h3>
<p>If the document is published in HTML format, it is possible to leverage HTML IDs and add RDF triples about them:</p>
<div class="code">
<p>Given the HTML of the article <a href="http://www.ncbi.nlm.nih.gov/pmc/articles/PMC2820274/">Amyloid Precursor Protein Mediates a Tyrosine-kinase Dependent Activation Response in Endothelial Cells</a>:</p>
<pre>
   ...
   &lt;div class="sec" <strong>id="S1"</strong>&gt;
      &lt;div style="text-transform: none;" id="S1titletitle" class="head1 section-title"&gt;
         &lt;div&gt;Introduction&lt;/div&gt;
      &lt;/div&gt;
      &lt;div id="S1content" class="section-content"&gt;
         &lt;div id="P2" class="p p-first"&gt;
            Endothelial cells ...
         &lt;/div&gt;
         ...
      &lt;/div&gt;
   &lt;/div&gt;
   ...
</pre>
<p>We can create XML/RDF as follow:</p>
<pre>&lt;rdf:Description rdf:about=&quot;<strong>http://www.ncbi.nlm.nih.gov/pmc/articles/PMC2820274/#S1</strong>&quot;&gt;
    &lt;rdf:type rdf:resource=&quot;<strong>http://purl.org/orb/Introduction</strong>&quot;/&gt;
&lt;/rdf:Description&gt;
</pre>
</div>
<p>In the process of authoring a new document, it is preferrable to use IDs identifying ORB sections (<a href="#use-case-1">See Use Case #1</a>). These IDs are obtained by adding the prefix 'orb-' to all the ORB terms. For example, the 'methods' section will be identified by the ID 'orb-methods'. In doing this, it will be possible to resolve the section by appending  '#orb-methods' to the document URI</p>
<div class="code">
<p>While authoring a document it is preferrable to use IDs identifying ORB sections:</p>
<pre>
   ...
   &lt;div class="sec" <strong>id="orb-introduction"</strong>&gt;
      &lt;div style="text-transform: none;" id="S1titletitle" class="head1 section-title"&gt;
         &lt;div&gt;Introduction&lt;/div&gt;
      &lt;/div&gt;
      &lt;div id="S1content" class="section-content"&gt;
         &lt;div id="P2" class="p p-first"&gt;
            Endothelial cells ...
         &lt;/div&gt;
         ...
      &lt;/div&gt;
   &lt;/div&gt;
   ...
</pre>
<pre>&lt;rdf:Description rdf:about=&quot;<strong>http://www.ncbi.nlm.nih.gov/pmc/articles/PMC2820274/#orb-introduction</strong>&quot;&gt;
    &lt;rdf:type rdf:resource=&quot;<strong>http://purl.org/orb/Introduction</strong>&quot;/&gt;
&lt;/rdf:Description&gt;
</pre>
</div>
<h3 id="using-rdfa"><span class="secno">5.4. </span>With HTML and RDFa </h3>
<p>Another possible way of using ORB is through RDFa [<a href="#rdfa-primer">RDFa Primer</a>]. Using a few simple XHTML attributes, authors could mark up human-readable data with machine-readable indicators for browsers and other programs to interpret. In fact, RDFa benefits from the extensive power of RDF.</p>
<div class="code">
        <p>This is the RDFa 1.0 injected into the open access article <a href="http://www.ncbi.nlm.nih.gov/pmc/articles/PMC2820274/">Amyloid Precursor Protein Mediates a Tyrosine-kinase Dependent Activation Response in Endothelial Cells</a>. The example includes some extensions such as title and abstract. It combines ORB, Dublin Core and FaBiO:</p>
        <pre>
&lt;div <strong>typeof="fabio:Article" about="_:a"  xmlns:fabio="http://purl.org/spar/fabio/"</strong> <em><b>xmlns:orb="http://purl.org/orb/"
  xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:dcterms="http://purl.org/dc/terms/" rel="dcterms:hasPart"</b></em>&gt;
   &lt;div <em><b>typeof="orb:Header"</b></em>&gt;
      ...
      &lt;span class="citation-abbreviation"&gt;J Neurosci. &lt;/span&gt;
      &lt;span <strong>about="_:a"</strong>  class="citation-publication-date" <em><strong>property="dc:date"</strong></em>&gt;2009 November 18; &lt;/span&gt;
      &lt;span class="citation-volume" <em>property="prism:volume"</em>&gt;29&lt;/span&gt;
      &lt;span class="citation-issue" &gt;(&lt;span <em>property="prism:issueIdentifier"</em>&gt;46&lt;/span&gt;)&lt;/span&gt;
      &lt;span class="citation-flpages"&gt;: 14451.&lt;/span&gt;
      &lt;span class="fm-vol-iss-date"&gt;doi: &lt;span <em>property="prism:doi"</em>&gt;10.1523/JNEUROSCI.3107-09.2009&lt;/span&gt;&lt;/span&gt;
      ...

      &lt;div <strong>about="_:a"</strong> class="fm-title" <em><b>property="dc:title"</b></em>&gt;
          Amyloid Precursor Protein Mediates a Tyrosine-kinase Dependent Activation Response in Endothelial Cells.
      &lt;/div&gt;
      &lt;div <strong>about="_:a"</strong>  class="contrib-group fm-author"&gt;
          &lt;span <em><b>property="dc:creator"</b></em>&gt;S.A. Austin&lt;/span&gt;,
          &lt;span <em><b>property="dc:creator"</b></em>&gt; M.A. Sens&lt;/span&gt;, and
          &lt;span <em><b>property="dc:creator"</b></em>&gt;C.K. Combs&lt;/span&gt;
      &lt;/div&gt;

      &lt;div <strong>about="_:a"</strong> <em><b>property="dcterms:abstract" </b></em>&gt;
         Amyloid precursor protein (APP) ...
      &lt;/div&gt;
   &lt;/div&gt;
   ...
   &lt;div class="sec" id="orb-introduction" <em><b>typeof="orb:Introduction" property="dc:description"</b></em>&gt;
      &lt;div style="text-transform: none;" id="S1titletitle" class="head1 section-title"&gt;
         &lt;div&gt;Introduction&lt;/div&gt;
      &lt;/div&gt;
      &lt;div id="S1content" class="section-content"&gt;
         &lt;div id="P2" class="p p-first"&gt;
            Endothelial cells ...
         &lt;/div&gt;
         ...
      &lt;/div&gt;
   &lt;/div&gt;
   ...

&lt;/div&gt;
</pre>

<p>You might notice the use of the blank node _:a through the Turtle idiom _:XXX. Alternatively it is possible to use an explicit URI identifying the article.</p>

</div>
<p> Triples can be extracted from the above snippets. For example, by copying and pasting the above snippet into the W3C RDFa 1.0 Distiller and Parser [<a href="#rdfa-distiller">RDFa-Distiller</a>], the correspondent RDF structure will be obtained:</p>
<div class="code">
  <pre>
&lt;rdf:RDF
  xmlns:fabio="http://purl.org/spar/fabio/"
  xmlns:dc="http://purl.org/dc/elements/1.1/"
  xmlns:dcterms="http://purl.org/dc/terms/"
  xmlns:orb="http://purl.org/orb/"
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
&gt;
  &lt;fabio:Article rdf:about="_:a"&gt;
    &lt;dc:date&gt;2009 November 18; &lt;/dc:date&gt;
    &lt;dc:creator&gt;C.K. Combs&lt;/dc:creator&gt;
    &lt;dc:creator&gt; M.A. Sens&lt;/dc:creator&gt;
    &lt;dc:creator&gt;S.A. Austin&lt;/dc:creator&gt;
    &lt;dc:title&gt;
          Amyloid Precursor Protein Mediates a Tyrosine-kinase Dependent Activation Response in Endothelial Cells.
    &lt;/dc:title&gt;
    &lt;dcterms:abstract&gt;
         Amyloid precursor protein (APP) ...
    &lt;/dcterms:abstract&gt;
    &lt;dcterms:hasPart&gt;
      &lt;orb:Header/&gt;
    &lt;/dcterms:hasPart&gt;
    &lt;dcterms:hasPart&gt;
      &lt;orb:Introduction&gt;
        &lt;dc:description rdf:parseType="Literal"&gt;
        ...
        &lt;/dc:description&gt;
      &lt;/orb:Introduction&gt;
    &lt;/dcterms:hasPart&gt;
    ...
  &lt;/fabio:Article&gt;
&lt;/rdf:RDF&gt;
 </pre>
</div>
<p>As you might have noticed, the <em>Header</em> element is empty. This behavior is related to some limitations of RDFa 1.0. With the next version or RDFa 1.1 - expected before the end of 2011 - the code can include the property <em>dc:description</em> for the Header element without disrupting the nested declarations. Similarly it will be possible to include RDFa declarations in the other ORB sections, for example <em>Introduction</em>.</p>
<div class="code">
  <p>This is the RDFa 1.1 injected into the open access article <a href="http://www.ncbi.nlm.nih.gov/pmc/articles/PMC2820274/">Amyloid Precursor Protein Mediates a Tyrosine-kinase Dependent Activation Response in Endothelial Cells</a>. It combines ORB, Dublin Core and FaBiO:</p>
  <pre>
&lt;div <strong>typeof="fabio:Article" about="_:a"  xmlns:fabio="http://purl.org/spar/fabio/"</strong> <em><b>xmlns:orb="http://purl.org/orb/"
  xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:dcterms="http://purl.org/dc/terms/" rel="dcterms:hasPart"</b></em>&gt;
   &lt;div <em><b>typeof="orb:Header"</b></em> <em><b>property=&quot;dc:description&quot;</b></em>&gt;
      ...
      &lt;span class="citation-abbreviation"&gt;J Neurosci. &lt;/span&gt;
      &lt;span <strong>about="_:a"</strong>  class="citation-publication-date" <em><strong>property="dc:date"</strong></em>&gt;2009 November 18; &lt;/span&gt;
      &lt;span class="citation-volume"&gt;29&lt;/span&gt;
      &lt;span class="citation-issue" &gt;(&lt;span<em></em>&gt;46&lt;/span&gt;)&lt;/span&gt;
      &lt;span class="citation-flpages"&gt;: 14451.&lt;/span&gt;
      &lt;span class="fm-vol-iss-date"&gt;doi: &lt;span<em></em>&gt;10.1523/JNEUROSCI.3107-09.2009&lt;/span&gt;&lt;/span&gt;
      ...

      &lt;div <strong>about="_:a"</strong> class="fm-title" <em><b>property="dc:title"</b></em>&gt;
          Amyloid Precursor Protein Mediates a Tyrosine-kinase Dependent Activation Response in Endothelial Cells.
      &lt;/div&gt;
      &lt;div <strong>about="_:a"</strong>  class="contrib-group fm-author"&gt;
          &lt;span <em><b>property="dc:creator"</b></em>&gt;S.A. Austin&lt;/span&gt;,
          &lt;span <em><b>property="dc:creator"</b></em>&gt; M.A. Sens&lt;/span&gt;, and
          &lt;span <em><b>property="dc:creator"</b></em>&gt;C.K. Combs&lt;/span&gt;
      &lt;/div&gt;

      &lt;div <strong>about="_:a"</strong> <em><b>property="dcterms:abstract" </b></em>&gt;
         Amyloid precursor protein (APP) ...
      &lt;/div&gt;
   &lt;/div&gt;
   ...
   &lt;div class="sec" id="orb-introduction" <em><b>typeof="orb:Introduction" property="dc:description"</b></em>&gt;
      &lt;div style="text-transform: none;" id="S1titletitle" class="head1 section-title"&gt;
         &lt;div&gt;Introduction&lt;/div&gt;
      &lt;/div&gt;
      &lt;div id="S1content" class="section-content"&gt;
         &lt;div id="P2" class="p p-first"&gt;
            Endothelial cells ...
         &lt;/div&gt;
         ...
      &lt;/div&gt;
   &lt;/div&gt;
   ...

&lt;/div&gt;
</pre>

<p>You might still notice the use of the blank node _:a through the Turtle idiom _:XXX. Alternatively it is possible to use an explicit URI identifying the article.</p>
</div>

<p> Triples can be extracted from the above snippets. For example, by copying and pasting the above snippet into the W3C RDFa 1.1 Distiller and Parser [<a href="#rdfa-distiller-1_1">RDFa-1.1-Distiller</a>], the correspondent RDF structure will be obtained:</p>
<div class="code">
<pre>
&lt;rdf:RDF
  xmlns:dc="http://purl.org/dc/elements/1.1/"
  xmlns:dcterms="http://purl.org/dc/terms/"
  xmlns:fabio="http://purl.org/spar/fabio/"
  xmlns:orb="http://purl.org/orb/"
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
&gt;
  &lt;fabio:Article&gt;
    &lt;dc:creator&gt; M.A. Sens&lt;/dc:creator&gt;
    &lt;dc:creator&gt;S.A. Austin&lt;/dc:creator&gt;
    &lt;dc:creator&gt;C.K. Combs&lt;/dc:creator&gt;
    &lt;dc:title&gt;
          Amyloid Precursor Protein Mediates a Tyrosine-kinase Dependent Activation Response in Endothelial Cells.
    &lt;/dc:title&gt;
    &lt;dc:date&gt;2009 November 18; &lt;/dc:date&gt;
    &lt;dcterms:abstract&gt;
         Amyloid precursor protein (APP) ...
    &lt;/dcterms:abstract&gt;

    &lt;dcterms:hasPart&gt;
      &lt;<strong><em>orb:Header</em></strong>&gt;
        &lt;dc:description&gt;
	      J Neurosci.
	      2009 November 18;
	      29
	      (46)
	      : 14451.
	      doi: 10.1523/JNEUROSCI.3107-09.2009
	      Amyloid Precursor Protein Mediates a Tyrosine-kinase Dependent Activation Response in Endothelial Cells.
	      S.A. Austin, M.A. Sens, and  C.K. Combs
	      Amyloid precursor protein (APP)
        ...
        &lt;/dc:description&gt;
      &lt;/<strong><em>orb:Header</em></strong>&gt;
    &lt;/dcterms:hasPart&gt;

    &lt;dcterms:hasPart&gt;
      &lt;<strong><em>orb:Introduction</em></strong>&gt;
        &lt;dc:description&gt;
          Introduction
          Endothelial cells ...
          ...
   	  &lt;/dc:description&gt;
      &lt;/<strong><em>orb:Introduction</em></strong>&gt;
    &lt;/dcterms:hasPart&gt;

    ...
  &lt;/fabio:Article&gt;
&lt;/rdf:RDF&gt;

</pre>
</div>
<p> This last snippet is looking more similar to the pure RDF snippet in section 4.2.</p>


<h2 class="no-num" id="acknowledgments">Acknowledgments</h2>
<p>We would like to thank Ivan Herman (W3C Semantic Web Activity Lead) for his help and support for RDF and RDFa technologies, Ron Daniel, Jr. (Elsevier Laboratories) for the help with PRISM-related issues, and Eric Prud'hommeaux (W3C) for the technical assistance with the creation of this document.</p>
<p>Also, we would like to thank Jodi Schneider (Digital Enterprise Research Institute), David R Newman (University of Southampton) and Scott Marshall (Leiden University Medical Center) for their valuable comments and feedback during the writing and editing of this note.</p>
<h2 class="no-num" id="references">References</h2>
  <dl>
   <dt><a id="tsuji2009" name="tsuji2009"></a>
   	[Tsuji2009]</dt>
	<dd>Tsujii, J. (2009). Refine and PathText, which combines Text Mining with
	Pathways. Keynote at Semantic Enrichment of the Scientific Literature Workshop 2009 (SESL
	2009), Cambridge, UK</dd>
    <dt><a id="dcmi" name="dcmi"></a>[DCMI]</dt>
    <dd>Dublin Core Metadata Element Set, Version 1.1 <br/><a href="http://dublincore.org/documents/dces/">http://dublincore.org/documents/dces/</a></dd>
    <dt><a id="bibo" name="bibo"></a>[BIBO]</dt>
    <dd>Bibliographic Ontology<br/><a href="http://bibliontology.com/">http://bibliontology.com/</a></dd>
    <dt><a id="fabio" name="fabio"></a>[FaBiO]</dt>
    <dd>FRBR aligned Bibliographic Ontology <br/><a href="http://purl.org/spar/fabio">http://purl.org/spar/fabio</a></dd>
    <dt><a id="prism" name="prism"></a>[PRISM]</dt>
    <dd>PRISM Namespaces, Version 2.1 <br/><a href="http://www.prismstandard.org/specifications/2.1/PRISM_prism_namespace_2.1.pdf">http://www.prismstandard.org/specifications/2.1/PRISM_prism_namespace_2.1.pdf</a></dd>
     <dt><a id="prism-dc" name="prism-dc"></a>[PRISM-DC]</dt>
    <dd>PRISM Subset of the Dublin Core Namespaces, Version 2.1<br/> <a href="http://www.prismstandard.org/specifications/2.1/PRISM_dublin_core_namespaces_2.1.pdf">http://www.prismstandard.org/specifications/2.1/PRISM_dublin_core_namespaces_2.1.pdf</a></dd>
    <dt><a id="prism-rcv" name="prism-rcv"></a>[PRISM-RCV]</dt>
    <dd>PRISM Controlled VocabulariesNamespaces, Version 2.1<br/> <a href="http://www.prismstandard.org/specifications/2.1/PRISM_controlled_vocabulary_namespace_2.1.pdf">http://www.prismstandard.org/specifications/2.1/PRISM_controlled_vocabulary_namespace_2.1.pdf</a></dd>
<dt><a id="prism-pam" name="prism-pam"></a>[PRISM-PAM]</dt>
    <dd>PRISM Aggregator Message Namespace, Version 2.1<br/> <a href="http://www.prismstandard.org/specifications/2.1/PRISM_aggregator_message_namespace_2.1.pdf">http://www.prismstandard.org/specifications/2.1/PRISM_aggregator_message_namespace_2.1.pdf</a></dd>
    <dt><a id="prism-pam-guide" name="prism-pam"></a>[PRISM-PAM-GUIDE]</dt>
    <dd>PRISM Aggregator Message Namespace Guide, Version 2.1<br/> <a href="http://www.prismstandard.org/pam_2.1/PAM_guide_2.1.pdf">http://www.prismstandard.org/pam_2.1/PAM_guide_2.1.pdf</a></dd>
   <dt><a id="dcmi-terms" name="dcmi-terms"></a>[DCMI-Terms]</dt>
    <dd>DCMI Metadata Terms <br/><a href="http://dublincore.org/documents/dcmi-terms/">http://dublincore.org/documents/dcmi-terms/</a></dd>
   <dt><a id="imrad" name="imrad"></a>
   	[IMRAD]</dt>
	<dd><a href="http://en.wikipedia.org/wiki/IMRAD">http://en.wikipedia.org/wiki/IMRAD</a></dd>
   <dt><a id="imrad-xml" name="imrad-xml"></a>
   	[IMRAD-XML]</dt>
	<dd><a href="http://www.uio.no/studier/emner/hf/imk/MEVIT4725/h04/resources/imrad.xml">http://www.uio.no/studier/emner/hf/imk/MEVIT4725/h04/resources/imrad.xml</a></dd>
    <dt><a id="rdf" name="rdf"></a>
   	[RDF]</dt>
	<dd>RDF Primer  - W3C Recommendation 10 February 2004<br/><a href="http://www.w3.org/TR/2004/REC-rdf-primer-20040210/">http://www.w3.org/TR/2004/REC-rdf-primer-20040210/</a></dd>
    <dt><a id="rdfa-primer" name="rdfa-primer"></a>
   	[RDFa-Primer]</dt>
	<dd>RDFa Primer 1.0 - Bridging the Human and Data Webs <br/><a href="http://www.w3.org/TR/xhtml-rdfa-primer/">http://www.w3.org/TR/xhtml-rdfa-primer/</a></dd>
     <dt><a id="rdfa-distiller" name="rdfa-distiller"></a>
   	[RDFa-Distiller]</dt>
    <dd>W3C RDFa Distiller and Parser <br/><a href="http://www.w3.org/2007/08/pyRdfa/">http://www.w3.org/2007/08/pyRdfa/</a></dd>
     <dt><a id="rdfa-distiller-1_1" name="rdfa-distiller-1_1"></a>
   	[RDFa-1.1-Distiller]</dt>
    <dd>W3C RDFa 1.1 Distiller and Parser <br/><a href="http://www.w3.org/2007/08/pyRdfa/Shadow.html">http://www.w3.org/2007/08/pyRdfa/Shadow.html</a></dd>
   </dl>

</body>
</html>