<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Wiki Authoring and Semantics of Mathematical Document Structure</article-title>
      </title-group>
      <contrib-group>
        <aff id="aff0">
          <label>0</label>
          <institution>Hiraku Kuroda and Takao Namiki Department of Mathematics, Hokkaido University</institution>
          ,
          <addr-line>060-0810 Sapporo</addr-line>
          ,
          <country country="JP">Japan</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>We are developing a CMS including document authoring feature based on wiki to publish structural mathematical documents on the Web. Using this system, users can write documents including mathematical expressions written in LATEX notation and explicitly stated characteristic structures of mathematical articles such as definitions, theorems, and proofs. Documents input to the system is published on the Web as not only XHTML files to be browsed but also XML files complying with NLM-DTD, which is used to exchange articles electronically. Not only single wiki page document, users can build a document which consist of more than one pages and is described its structure semantically by the system. In order to do this, we also propose an application of OAI-ORE and RDF vocabularies to describe structures of documents consisting of several resources.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1 Introduction</title>
      <p>Today, many documents are published on the Web. The term “documents” here includes articles of news
or blog, wiki pages, journal articles, and any other web pages. These documents are published as HTML
or XHTML to be browsed, or as PDF or PS file to be printed out. Sometimes one document is published
as several formats.</p>
      <p>Some documents consist of several resources. One of examples is a document including a graphic
image. Here, we assume that body text of the document is written in a HTML file and the image is a
JPG file. On the Web, each of them is independent resource and given unique URI. When URI of the
image is put on src attribute of an img element in the HTML file, we should treat the document as not
just referencing but including or embedding the image. In this case, this document is an aggregation of
two resources that are HTML file of body text and JPG file of graphical image.</p>
      <p>
        Sometimes documents include not only graphic images but also whole of other (more small)
documents. In general, this is called transclusion. HTML does not have this transclusion feature in itself,
but MediaWiki, for example, has templates feature to extract content of other wiki pages to the page [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ].
In this case, the document is an aggregation of resources that are body text written in wiki markup and
other documents which are indicated in the document to be included.
      </p>
      <p>
        Furthermore, we sometimes build a document by integrating several documents. In this case, not
only a large document is just split into several documents, but each of documents is independent and
has their own URI, and they can be referenced directly. In general, parts, chapters, or sections of a
document are able to be independent documents. MathML specification by W3C [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ] is an example of
such documents. This document consists of one overview, eight sections, and eleven appendices. These
divisions are independent web pages and have their own URIs. Finer divisions of a document may be
independent documents according to structure or characteristics of a document. For example, definitions,
theorems, proofs, and expressions in mathematical documents may be independent documents.
      </p>
      <p>
        Open Archives Initiative Object Reuse and Exchange is standards to describe and exchange
aggregations of web resources [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ]. In the User Guide of OAI-ORE [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ], journal articles are described as
      </p>
      <sec id="sec-1-1">
        <title>Listing 1: A document including a theorem written in Wiki</title>
        <p>At f i r s t , we g i v e Taylor ’ s theorem and p r o o f o f i t .
[ [ theorem i d =” t a y l o r t h e o r e m ” t i t l e =” Taylor ’ s theorem ” j
Let $f$ be a f u n c t i o n which i s d e f i n e d on t h e i n t e r v a l $ ( a , b ) $ and s u p p o s e t h e $ n $ t h
d e r i v a t i v e $ f ˆ f ( n ) g$ e x i s t s on $ ( a , b ) $ . Then f o r a l l $x$ and $x 0$ i n $ ( a , b ) $ ,
$$ R n ( x ) = n f r a c f f ˆ f ( n ) g( y ) gfn ! g ( x x 0 ) ˆ n $$
w i t h $y$ s t r i c t l y between $x$ and $x 0$ ( $y$ depends on t h e c h o i c e o f $x$ ) . $R n ( x ) $ i s t h e
$ n $ t h r e m a i n d e r o f t h e T a y l o r s e r i e s f o r $ f ( x ) $ .
] ]
( O r i g i n a l t e x t o f t h e theorem i s h t t p : / / p l a n e t m a t h . org / e n c y c l o p e d i a / TaylorsTheorem . html ,
r e t r i e v e d a t 2 0 1 1 . 0 5 . 0 8 )
aggregations of representation files such as PDF or PS. In this article, on the other hand, we propose
describing documents as aggregations of constituting resources and relating the documents with their
representations apart from describing aggregations.</p>
        <p>With a background like that, we are developing a content management system Matherial, which
manages and publishes mathematical documents and other resources. One of the purposes is developing
a system which assists to write documents consisting of several resources, and publishes as web pages
with appropriate metadata to describe its structure and publishes as XML files complying with
NLMDTD for further reusing.</p>
        <p>Matherial provides authoring assistant feature based on wiki engine. Users of the system can write
a wiki page including chapters, sections, mathematical statements, and expressions, or they can write
some of them as independent wiki pages and integrate them into one document and publish it.
Relationships between documents and included resources, and between documents and wiki pages representing
them, are modeled as aggregations of OAI-ORE, and they are described in XHTML representation of
documents by RDFa. Matherial can output documents into not only one or more XHTML pages, but
also XML files complying with NLM-DTD. Therefore, other systems supporting NLM-DTD are able to
re-use documents by Matherial.</p>
        <p>The paper is organized as follows: In section 2, we present an example of mathematical structural
documents on Matherial. In section 3, we propose an application of OAI-ORE and RDF vocabulary to
describe structural documents on Matherial and more generally on the Web. Finally, section 4 concludes
the paper.
2
2.1</p>
      </sec>
    </sec>
    <sec id="sec-2">
      <title>Mathematical Contents Management System</title>
      <sec id="sec-2-1">
        <title>Wiki-based Authoring</title>
        <p>
          One of major features of Matherial, developed in this study, is assistant authoring mathematical
documents. This is based on so-called “Wiki Engine”, so users can write documents by simple markup
notation and publish them on the Web. They can put mathematical expressions written in LATEX notation
into texts, and our own MathML library [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ] converts them to MathML [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ].
        </p>
        <p>The most simple type of documents created on Matherial is one consisting of a wiki page. When users
need to write mathematical text structures, such as definitions, theorems, and proofs, using functional
markup for them, they can expressly provide that segments have such property.</p>
        <p>For example, Listing 1 is a document written in wiki markup including a theorem. When users
write theorems in their document directly like this, URIs of theorems are hash URIs, appending</p>
        <sec id="sec-2-1-1">
          <title>Listing 2: A document imporint other resources</title>
          <p>We b e g i n w i t h Taylor ’ s theorem and i t s p r o o f .
[ [ i m p o r t w i k i / TaylorTheorem ] ]
[ [ i m p o r t w i k i / ProofOfTaylorTheorem ] ]
For a f u n c t i o n $ f ( x ) $ , $f$ i s T a y l o r e x p a n d a b l e when $n l i m fnn t o n i n f t y gR n ( x ) =0$ where $R$ i s
r e m i n d e r term o f [ [ [ w i k i / TaylorTheorem j t h e theorem ] ] , and we have b e l l o w .
[ [ i m p o r t w i k i / T a y l o r E x p a n s i o n ] ]
Even i f complex f u n c t i o n $ f ( z ) $ i s n o t h o l o m o r p h i c a t a p o i n t $c$ , i f $f$ i s h o l o m o r p h i c i n an
a n n u l u s around $c$ , we g e t L a u r e n t s e r i e s bellow ,
$$f ( z ) = nsum fn=n i n f t y gˆfn i n f t y g a n ( z c ) ˆ n$$
where
$$a n =n f r a c 1 f2n p i i gn o i n t ngamman f r a c f f ( z ) dz gf( z c ) ˆf n+1gg $$
and $ngamma$ i s a c l o s e d c u r v e i n t h e a n n u l u s ( f i g . [ [ r e f a n n u l u s ] ] ) .
[ [ f i g u r e f i l e / A n n u l u s O f L a u r e n t i d = a n n u l u s ] ]
T h i s i s e x t e n s i o n o f [ [ [ T a y l o r E x p a n s i o n ] ] ] f o r f u n c t i o n s which a r e n o t h o l o m o r p h i c .
their IDs as fragment to URI of the document. In this case, assuming a URI of a document is
http://mw2011.matherial.org/wiki/Taylor, a URI of a theorem itself in the document is http:
//mw2011.matherial.org/wiki/Taylor#taylor_theorem.</p>
          <p>For important definitions, theorems, and proofs, considering we discuss about them or reuse them
from other documents, they should be independent documents and referenced by their own URI. On
wiki of Matherial, users can set type of page, for example set that page is a theorem, the system treats the
document by the wiki page as if it is described a theorem. In this case, URI of the theorem is URI of the
document by wiki page. Detail about URIs and relationships of documents and wiki pages in Matherial
are illustrated in section 3.</p>
          <p>With Matherial, users can write documents importing and extracting mathematical statements which
have been created as independent document. Moreover users can put images which are managed in
Matherial into documents in the same way, and they can use descriptions of images which were input
when images were upload to the system instead of writing new descriptions in the page. Listing 2 is
a document importing statements which are already published and going on to describe a statement
following them. In that example, an image referenced in the text will be imported with its description.</p>
          <p>Moreover, aggregating these documents as sections, chapters, or parts, users can build a new
document. In Matherial, users input enumeration of sub documents with metadata of the document such as
title, author’s information, and so on into form to build the document. Detail of semantic structure of
documents which consist of several resources is described at section 3.
2.2</p>
        </sec>
      </sec>
      <sec id="sec-2-2">
        <title>Output Documents</title>
        <p>
          Matherial output documents as XML files. XML schemas of output XML files are XHTML [
          <xref ref-type="bibr" rid="ref18">18</xref>
          ] to read
directly by web browsers, and NLM-DTD [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ] to exchange articles electrically.
        </p>
        <p>
          For XHTML files, metadata are described as RDF graph [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ] and embedded by RDFa [
          <xref ref-type="bibr" rid="ref15">15</xref>
          ]. Metadata
written into XHTML are metadata of the document itself such as title, authors’ information, and time and
date when the document was created and update, and structure information about relationships between
the document and other resources. For example, relationships between resources for a document about
the Laurent series shown previously is illustrated at Fig.1. The web page of this document browsed is
        </p>
        <p>Listing 3: A part of an NLM-DTD XML version of a document
Discussion forum for The Document</p>
        <p>Taylor Theorem
mt:discussedAt
mt:discussionAbout
mt:hasRepresentation</p>
        <p>Laurent Series
XHTML</p>
        <p>Wiki Markup Text
shown at Fig.2.</p>
        <p>
          For XML files complying with Archiving and Interchange Tag Set [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ] of NLM-DTD, URIs of
included resources are written at xlink:href attribute of uri element in elements which included
resources are extracted to. Mathematical statements are extracted into statement element, and type of
statements are explicitly shown at content-type attributes. Listing 3 is a part of an XML file
complying with NLM-DTD of the document shown previously. Mathematical statements are written into
statement elements and their URLs are into statement/attrib/uri elements. Relationship
between a theorem and its proof is shown at statement/attrib/uri element of the proof. Imported
image and its description are extracted at fig element and it is referenced using xref element. You can
get the whole of the XML file from http://mw2011.matherial.org/LaurentSeries/en/nlm.
3
        </p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>Document structure and its metadata</title>
      <p>
        The documents authoring feature of Matherial is based on wiki engine. Users write texts by wiki markup
of Matherial. The most simple document is one consist of only body text but not any other resources.
Matherial converts an input wiki markup text to XML files complying with XHTML and NLM-DTD, and
publish them on the Web. Wiki source files, XHTML files, and XML files should be given different URI,
and a URI of each files is different from the URI of the document itself (we call a URI for a document
itself platonic form URI) [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ].
      </p>
      <p>In Matherial, users can write documents which include other resources, too. This does not means
that documents just reference other resources. As \includegraphics command or \input command
of LATEX, users can embed images or extract contents of other documents into the document. Matherial
generates XHTML files which include contents of other documents and is embedded images by img
elements, and generates XML files of NLM-DTD which include other documents and is embedded</p>
      <p>mt http://www.matherial.org/terms/
rdf http://www.w3.org/1999/02/22-rdf-syntax-ns#
ore http://www.openarchives.org/ore/terms/
images by graphic elements, from wiki sources written like that.</p>
      <p>
        This document structure on Matherial is described as an RDF graph whose nodes are platonic form
URI of the document, URIs of resources included in the document, URIs of representations of the
document, and so on (Fig.1). Matherial describes this structure by Resource map of Open Archives Initiative
Object Reuse and Exchange (OAI-ORE) [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ].
      </p>
      <p>The structure of a document which consists of several resources and which is represented by several
representations could be applied to not only documents in Matherial but general documents on the Web.
In following subsection 3.1, we will introduce OAI-ORE to describe Aggregations of resources, then in
subsection 3.2, we will show a model of the document structure and metadata schema to describe the
structure. RDF namespaces and its prefixes used in this article are shown at table 1.
:
s
a
x
h</p>
      <p>N ore:proxyIn
e
x
t
t
N
s
x
e
x
:
h
a</p>
      <sec id="sec-3-1">
        <title>Revisiting OAI-ORE</title>
        <p>Open Archives Initiative Object Reuse and Exchange (OAI-ORE) provides a model to describe
aggregations of resources. In OAI-ORE, a resource which consists of one or more resources is called an
Aggregation. A resource which is a member of an Aggregation is called an Aggregated Resource. An
aggregation is defined as a conceptual construct, so it does not have a representation. Therefore,
information about an Aggregation should be described by other resources different from the Aggregation. Such a
resource which describes an Aggregation is called a Resource Map. For example, relationships between
an Aggregation and Aggregated Resources are described in a Resource Map for the Aggregation.</p>
        <p>OAI-ORE provides a mechanism named Proxy to relate Aggregated Resources with properties which
are given only in the Aggregation. In an Aggregation A-1, for example, we assume that two Aggregated
Resources AR-1 and AR-2 have order AR-1 ! AR-2. Moreover, we assume that they have different order
AR-2 ! AR-1 in another Aggregation A-2. In this case, if we describe directly the order relationship
between AR-1 and AR-2 in AR-1, it conflict to relationship in AR-2. This is because we describe
relationship which is available only in AR-1 independently of AR-1. To resolve this problem, we use Proxy
resources which act as Resources in the Aggregation to describe relationships available only in the
Aggregation between Aggregated Resources and other resources. For example, relationships between AR-1
and AR-2 in A-1 is described using their Proxies like fig.3.</p>
        <p>
          For more detail of OAI-ORE, see [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ].
3.2
        </p>
      </sec>
      <sec id="sec-3-2">
        <title>Structure of Document including Resources</title>
        <p>3.2.1</p>
        <p>Document and its Members
In this study, a Document is an Aggregation consisting of one or more resources. A resource which is a
constituent of a Document is called a Member of Document, or simply a Member. An image embedded
into a Document is familiar example of Member. A Member of a Document could be another Document
different from the aggregating Document. In other words, aggregating several Documents, we can build
a new Document. Relationships between a Document and its Members are described by RDF triples
whose predicates are ore:aggregates.
Document Content. A Document could have a resource as one of Members which is described the
content of the Document itself. We call such a Member a Document Content. A content of a Document
is body text of the Document. When a Document includes other resources, indications to include them
are written into the content. One example of Document Content is a HTML file, which is a source file of
a web page. We can write not only marked-up body text, but also indications to embed images into the
page using img elements. In this case, the Document consists of a HTML file as Document Content and
images indicated. When we browse this document, web browser get a HTML file from a server, recognize
it, get other resources to embed into the page, and display the completed web page. For another example,
text files written in wiki markup for any wiki engines. They are described body text and embedding
indications different notation from HTML. The system may convert it to a HTML, or create a PDF file
which contains image files. Relationship between a Document and a Document Content is described by
a RDF triple whose predicate is mt:hasContent, which is sub property of ore:aggregates.
Order of Members. When Document has the Document Content, positioning of other Members is
described in the Document Content. On the other hand, when Document is simple Aggregation of
resources and does not have a Document Content, we may want to describe positioning or order of
Members. Furthermore, we may want to give Members complicated and non-linear order relationships
such as tree structure. In this article, we propose mt:hasNext predicate to describe order relationships
of Members in the Document. This property takes URIs of Proxies of Members for subjects and objects
of triples to describe linear or complicated order relationships of Members of the Document (fig.4)
Type of Members. We may want to give Members any role in a Document. In an “article” document,
for example, the first Member is abstract of the article, following some Members are Sections of the
article, and the last Member is References of the article.</p>
        <p>mt:partType predicate is to describe these roles of Members in a Document. This property takes
URIs of Proxies of Members for subjects, and URIs of sub-classes of mt:PartType which
represent roles of Members in Documents. Sub-classes of mt:PartType are mt:Preface, mt:Abstract,
mt:TableOfContents, mt:Part, mt:Chapter, mt:Section, mt:Acknowledgment, mt:Appendix,
mt:References, and mt:Index.
3.2.2</p>
        <p>Mathematical Element
Mathematical documents may contain distinctive elements, such as mathematical expressions (especially
display math style), definitions, theorems, proofs. When we write a mathematical document, preparing
these elements as independent resources and including them in the Document as Members, we can
reference these import elements individually and reuse them.</p>
        <p>When we create a Document containing mathematical elements, we can show type of the Document
explicitly using sub-classes of mt:MathematicalObject. Sub classes of mt:MathematicalObject
aremt:Expression, mt:Definition, mt:Theorem, and mt:Proof. mt:Theorem has more detailed
sub classes, that are mt:Lemma, mt:Corollary, and mt:Proposition.</p>
        <p>A resource of type mt:Proof describing mathematical proof should show explicitly which theorem
is proved. mt:proofOf is predicate for RDF triples to relate theorems and its proofs. This property takes
URIs of resources of type mt:Proof for subjects and URIs of resources of type mt:Theorem or its sub
classes for objects (fig.4).
:
s
t
m
h
a</p>
        <p>N
e
x
t
mt:partType
mt:Section
In this article, Documents are Aggregations of ORE, so Documents are abstract resources and do not
have entities. Therefore, to browse Documents, Documents should be related with other resources which
Documents are serialized in any formats which we can browse. A resource which is serialized from a
Document and has URI different from URI of the Document is called a Representation of the
Document. When a Document is related to a Representation of the Document, We say a Document has a
Representation. a Document Content may be one of Representations of the Document. Some
Representations include all Members of Document any way like PDF files, other Representations include only
indications and references to other Members like HTML files. Relationships between Documents and its
Representations are described by RDF triples using mt:hasRepresentaion predicate (fig. 1).
4</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>Conclusion and Discussion</title>
      <p>In this article, we introduced a CMS developed for authoring and publishing mathematical documents,
and we proposed background semantics to describe structures of documents consisting of several
resources. Using the system, we can publish not only small documents but also large documents consisting
of several resources by writing in easy mark-up. Structures of documents consisting of several resources
are described as RDF graphs based on Resource map of OAI-ORE, and they will be reused by Semantic
Web Technologies.</p>
      <p>
        Some applications of OAI-ORE are describe an article as an aggregation of OAI-ORE. The
FORESITE [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] project developed a toolkit to describe metadata of articles from JSTOR by using OAI-ORE.
In the project, each issue of journals is an Aggregation of articles, and each article is an Aggregation
of individual page images and a PDF-formatted version of the entire article [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. The ICE-TheOREM
project [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ] provides thesis authoring and publishing systems. In this project, each thesis is an
Aggregation of sections and PDF, DOC, and ODT version of the article, and each section is an Aggregation
of PDF, DOC, and ODT version of the section. These applications treats each article as an Aggregation
of parts of it and its Representations. On the other hand, in this article, we describe a Document as an
Aggregation of parts of it, and we use another property for relationships between a Document and its
Representations.
      </p>
      <p>
        The OMDoc format is a content markup scheme for mathematical documents [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. This format is
designed for the Mathematical Knowledge Base. SWiM is a semantic wiki for Mathematical
Knowledge Management using OMDoc and OpenMath [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ][
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. While these are aimed at building the
Mathematical Knowledge Base, the Matherial is aimed at publishing mathematical documents by using
simple notation for authoring and only presentation markups for outputting. OMDoc also provides a
document ontology [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ]. RDF classes i.e. Definition, Theorem (and so on), Proof, and Formula
and RDF properties i.e. proves and provedBy are defined, but a class for general mathematical
expression is not defined. These classes of OMDoc ontology are subclass of MathKnowledgeItem.
However, documents of Matherial are not expressed in OMDoc. So we use classes in mt namespace
instead of OMDoc ontology.
      </p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>H.</given-names>
            <surname>V. de Sompel</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Lagoze</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. L.</given-names>
            <surname>Nelson</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Warner</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Sanderson</surname>
          </string-name>
          , and
          <string-name>
            <given-names>P.</given-names>
            <surname>Johnston</surname>
          </string-name>
          .
          <article-title>Adding eScience Assets to the Data Web</article-title>
          .
          <source>In Proceedings of the WWW2009 Workshop on Linked Data on the Web</source>
          ,
          <year>June 2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>[2] FORESITE. http://foresite.cheshire3.org/.</mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <surname>Help</surname>
          </string-name>
          :
          <article-title>Templates MediaWiki</article-title>
          . http://www.mediawiki.org/wiki/Help:Templates.
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>M.</given-names>
            <surname>Kohlhase. OMDoc - An Open</surname>
          </string-name>
          Markup
          <source>Format for Mathematical Documents [version 1</source>
          .2], volume
          <volume>4180</volume>
          of Lecture Notes in Computer Science. Springer Berlin Heidelberg, Berlin, Heidelberg,
          <year>2006</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>C.</given-names>
            <surname>Lange</surname>
          </string-name>
          .
          <article-title>Mathematical Semantic Markup in a Wiki: the Roles of Symbols and Notations</article-title>
          .
          <source>In Proceedings of the 3rd Semantic Wiki Workshop (SemWiki</source>
          <year>2008</year>
          )
          <article-title>at the 5th European Semantic Web Conference (ESWC</article-title>
          <year>2008</year>
          ),
          <year>June 2008</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>C.</given-names>
            <surname>Lange. SWiM - A Semantic</surname>
          </string-name>
          <article-title>Wiki for Mathematical Knowledge Management</article-title>
          .
          <source>In The Semantic Web: Research and Applications 5th European Semantic Web Conference, ESWC</source>
          <year>2008</year>
          , Tenerife, Canary Islands, Spain, June 1-5,
          <fpage>2008</fpage>
          <string-name>
            <surname>Proceedings</surname>
          </string-name>
          ,
          <year>June 2008</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>MathML</given-names>
            <surname>Library</surname>
          </string-name>
          . http://rubygems.org/gems/math_ml.
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>Mathematical</given-names>
            <surname>Markup Language (MathML) Version</surname>
          </string-name>
          <article-title>2.0 (Second Edition)</article-title>
          . http://www.w3.org/TR/MathML2/.
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>Journal</given-names>
            <surname>Archiving</surname>
          </string-name>
          and Interchange Tag Suite. http://dtd.nlm.nih.gov/.
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <article-title>Archiving and Interchange Tag Set</article-title>
          . http://dtd.nlm.nih.gov/archiving/.
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <article-title>ORE Specifications and User Guides - Table of Contents</article-title>
          . http://www.openarchives.
          <source>org/ore/1</source>
          .0/toc.
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>OMDoc</given-names>
            <surname>Document</surname>
          </string-name>
          <article-title>Ontology</article-title>
          . http://kwarc.info/projects/docOnto/omdoc.html.
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <given-names>ORE</given-names>
            <surname>User Guide - Primer</surname>
          </string-name>
          . http://www.openarchives.
          <source>org/ore/1</source>
          .0/primer.
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <surname>RDF - Semantic Web</surname>
          </string-name>
          Standards. http://www.w3.org/RDF/.
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <article-title>RDFa in XHTML: Syntax and Processing</article-title>
          . http://www.w3.org/TR/rdfa-syntax/.
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <string-name>
            <given-names>L.</given-names>
            <surname>Richardson</surname>
          </string-name>
          and
          <string-name>
            <given-names>S.</given-names>
            <surname>Ruby. Restful Web Services. O'Reilly Media</surname>
          </string-name>
          ,
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [17]
          <string-name>
            <given-names>P.</given-names>
            <surname>Sefton</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Downing</surname>
          </string-name>
          , and
          <string-name>
            <given-names>N.</given-names>
            <surname>Day</surname>
          </string-name>
          .
          <article-title>ICE-Theorem - End to end semantically aware eResearch infrastructure for theses</article-title>
          .
          <source>Journal of Digital Information</source>
          ,
          <volume>11</volume>
          (
          <issue>1</issue>
          ), Jan.
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          <source>[18] XHTML 1</source>
          .1 -
          <string-name>
            <surname>Module-based</surname>
            <given-names>XHTML</given-names>
          </string-name>
          - Second
          <string-name>
            <surname>Edition</surname>
          </string-name>
          . http://www.w3.org/TR/xhtml11/.
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>