<!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>DC2AP Metadata Editor: A Metadata Editor for an Analysis Pattern Reuse Infrastructure</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Douglas Alves Peixoto</string-name>
          <email>douglasalves.ufv@gmail.com</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Lucas Francisco da Matta Vegi</string-name>
          <email>lucasvegi@gmail.com</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Jugurta Lisboa-Filho</string-name>
          <email>jugurta@ufv.br</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Departamento de Informática, Universidade Federal de Viçosa Viçosa-MG, Brazil</institution>
          ,
          <addr-line>36570-000</addr-line>
        </aff>
      </contrib-group>
      <abstract>
        <p>The software development process often encounters obstacles to reuse analysis patterns. Many designers do not have access to these computational artifacts by the difficulty in finding them, since the ways in which analysis patterns are documented are often precarious. The lack of both a computational tool which supports the analysis patterns documentation process and a digital repository to store these patterns affect their reuse. This paper presents the tool DC2AP Metadata Editor. This tool is a metadata editor for analysis patterns based on the Dublin Core Application Profile for Analysis Patterns (DC2AP). To support the patterns retrieval, the DC2AP Metadata Editor provides analysis patterns documented in RDF files, thus allowing the knowledge stored in these artifacts to be shared and automatically interpreted by software.</p>
      </abstract>
      <kwd-group>
        <kwd>analysis pattern</kwd>
        <kwd>reuse</kwd>
        <kwd>Dublin Core</kwd>
        <kwd>semantic web</kwd>
        <kwd>linked data</kwd>
        <kwd>cloud computing</kwd>
        <kwd>software as a service</kwd>
        <kwd>web service</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>Analysis patterns are reusable computational artifacts aimed at the analysis stage of
the software development process. These artifacts support software designers during
the system domain analysis, reducing in this way the time spent on the software
design and especially allowing interoperability between systems. Although the analysis
patterns provide gains in the software development process through knowledge reuse,
designers can still find difficulties in reuse them due to inefficiency in the way which
these patterns are documented. This complicates to search for these artifacts by
computational tools or even by search engines on the Internet.</p>
      <p>The analysis patterns documentation is an important task in order to enable
software designers to effectively share these artifacts. To date there is no template to
document patterns of analysis that is widely accepted, so each set of patterns is specified
according to its author’s preferences. Although this is a common practice, a consensus
on the use of a single documentation standard by the authors can facilitate the
processes of search, manipulation and dissemination of these patterns.</p>
      <p>
        Aiming to solve the problem of the lack of both standardization and detail in the
analysis patterns documentation, a specific metadata profile to document analysis
patterns, called DC2AP, was proposed [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ].
      </p>
      <p>The following paper presents the tool DC2AP Metadata Editor. This tool allows
the creation and editing of metadata about analysis patterns by using the DC2AP
profile. The metadata documented with this tool can be exported to RDF format and
consequently became Linked Data that reduces barriers to reuse analysis patterns.</p>
      <p>
        The DC2AP Metadata Editor is a free software that is available on the Software as
a Service (SaaS) model. Thus, it can be accessed from any location via the Internet
regardless of technological details in your terminal access, requiring only a Web
browser and Internet access [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ]. Some of the functionalities of this metadata editor
are also available via Web services, allowing other systems to make use of them.
      </p>
      <p>The remainder of this paper is organized as follows: Section 2 describes the related
works with documentation of analysis patterns; semantic Web and Linked Data; cloud
computing and Web services. The tool DC2AP Metadata Editor proposed in this
paper is presented in Section 3, while Section 4 presents conclusions and future works.
2
2.1</p>
    </sec>
    <sec id="sec-2">
      <title>Related Work</title>
      <sec id="sec-2-1">
        <title>Analysis Pattern Documentation</title>
        <p>
          Analysis patterns can be documented from the use of predefined models and
sketches. The absence of use of models in the analysis pattern documentation reduces
the usability of these patterns [
          <xref ref-type="bibr" rid="ref4">4</xref>
          ]. It happens due to a bigger difficulty in retrieving
knowledge in unstructured documentation. Some analysis patterns documented by
means of models can be found in [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ]. A model for documenting analysis patterns is
presented in [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ], which is composed of the topics: name, problem, context,
motivation, solution, participants and related patterns. This model was applied by [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ] to
document an analysis pattern focused on defining an urban streets mesh.
        </p>
        <p>
          This analysis pattern, originally documented in [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ], will be presented later
documented with DC2AP using the DC2AP Metadata Editor.
        </p>
      </sec>
      <sec id="sec-2-2">
        <title>APRI – Analysis Patterns Reuse Infrastructure.</title>
        <p>
          The access to analysis patterns is still very deficient due to the format used for
documentation and availability of them [
          <xref ref-type="bibr" rid="ref4">4</xref>
          ]. These patterns are usually presented in
means of access not machine-processable, such as books and scientific papers, thus
hindering the retrieval of information from these reusable computational artifacts.
        </p>
        <p>
          In order to minimize these problems concerning the documentation and availability
of analysis patterns, thus increasing the possibilities for reuse of these artifacts, in [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ]
was proposed the architecture of an Analysis Pattern Reuse Infrastructure (APRI). In
the following infrastructure, which is shown in Fig. 1, the analysis patterns are
documented using metadata and can be retrieved by Web services.
        </p>
        <p>The DC2AP Metadata Editor presented here was designed and developed as a tool
of the Pattern Portal.</p>
        <p>Pattern Portal: Contains a set of tools and services focused on discovery,
obtaining, cataloging and reuse of analysis patterns.</p>
        <p>Metadata Repository: Are repositories that contain metadata in XML for the
documentation of analysis patterns and services contained in an APRI.
Analysis Pattern Repository: Are repositories that contain the solutions
proposed by analysis patterns represented by means of diagrams in the XMI
format. These diagrams can be used by portrayal and collaboration services.
Portrayal Service: Are services that support the visualization of diagrams
contained in analysis patterns of an APRI.</p>
        <p>Catalog Service: Are services that enable the cataloging, discovery and use
of analysis patterns and services of an APRI, based on their metadata.
Access Service: Are services that allow to obtain analysis patterns.</p>
        <p>Collaboration Service: Are services that allow analysts and designers to
share their use experiences to improve analysis patterns in an APRI.</p>
      </sec>
      <sec id="sec-2-3">
        <title>DC2AP - Dublin Core Application Profile for Analysis Pattern.</title>
        <p>
          To assist authors and users of analysis patterns in documentation task, [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ] [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ]
presented the Dublin Core Application Profile for Analysis Patterns (DC2AP). The
DC2AP was developed based on the model for the specification of analysis patterns
proposed by [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ] and the Dublin Core metadata standard [
          <xref ref-type="bibr" rid="ref16">16</xref>
          ]. The main goals of the
DC2AP are to standardize the analysis patterns documentation in APRI metadata
repositories and then improve the reuse of analysis patterns through documentation
that allow a better knowledge retrieval made by computers and therefore provide
specific information that could not be previously retrieved by search engines.
        </p>
        <p>In contrast to the Dublin Core metadata standard, which is generic and therefore
intended to document resources from multiple domains, the model proposed in DC2AP
was specially developed to document analysis patterns, thus rich in details of this
specific domain. The DC2AP is composed by twenty-one major elements and
fortyone elements refiners, all of them are specific for analysis patterns documentation.
Each of the main and refiners elements of DC2AP are controlled by rules regarding to
obligation, occurrence and value type of each field. These rules seek to standardize
the use of this application profile and analysis pattern documentation.</p>
        <p>Due to its level of detail, this model was chosen to be used in the DC2AP Metadata
Editor to document analysis patterns.
2.2</p>
      </sec>
      <sec id="sec-2-4">
        <title>Semantic Web and Linked Data</title>
        <p>
          The Semantic Web is seen as a layer of the Web where is possible to publish,
retrieve and use data that can be processed by machines [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ]. Linked Data provides the
means to make this possible, because these are structured and machine-processable
data published on the Web. These data are well defined and connected to other data
from different sources through semantic relationships [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ].
        </p>
        <p>
          Linked Data uses three technologies to support the Semantic Web. Uniform
Resource Identifiers (URIs) are used to identify the data, the HTTP (Hypertext Transfer
Protocol) on the other hand is used as a mechanism for data retrieval and finally the
RDF (Resource Description Framework) is used to describe machine-processable data
on the Web and creating semantic relationships among them [
          <xref ref-type="bibr" rid="ref6">6</xref>
          ].
        </p>
        <p>In order to provide Linked Data from analysis patterns is important that a tool for
cataloging intends to export the metadata of these artifacts to RDF files and assign an
URI to each of these documents. The objectives of the tool DC2AP Metadata Editor,
presented in Section 3, comply with such tasks.
2.3</p>
      </sec>
      <sec id="sec-2-5">
        <title>Cloud Computing and Web Services</title>
        <p>
          Cloud computing is provided through different types of services, and the main one
is the Software as a Service (SaaS) [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ]. This service type provides various software
resources over the internet and they can be used via web browsers by end users [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ].
The DC2AP Metadata Editor presented here is an example of SaaS.
        </p>
        <p>
          The main reasons for developing the DC2AP Metadata Editor as a SaaS are the
democratization of the access to this tool and its facilitated coupling to an APRI.
Other tools as CatMDEdit [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ] and xMET Metadata Editor [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ] were evaluated during this
work. Although these tools are metadata editors based on Dublin Core, they are not
specific for analysis patterns documentation and were not developed using Web
technology, which prevents them for being used as SaaS in an APRI.
        </p>
        <p>Besides of the DC2AP Metadata Editor was developed as a SaaS, this tool provides
some of its resources by means of Web services, so other applications can understand
and reuse these resources without the need to use its GUI, regardless of the
programming language used to create them.</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>DC2AP Metadata Editor</title>
      <p>DC2AP Metadata Editor is a SaaS that enables analysis patterns users to create,
edit and store metadata of these patterns according to rules described in the DC2AP.
This tool provides Linked Data when exports these metadata to RDF files.</p>
      <p>
        DC2AP Metadata Editor was developed using the framework Google Web Toolkit
(GWT) [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ]. GWT uses Java as standard programming language, and converts the
source code produced in this language to JavaScript code compatible with different
browsers. This technology allows to create dynamic Web systems and has a high level
of portability, allowing the DC2AP Metadata Editor run on all major Web browsers.
      </p>
      <p>Fig. 2 shows the initial window of the DC2AP Metadata Editor. This tool is hosted
on a server that provides access to its facilities and Web Services. It can be accessed
by the URI: www.purl.org/dc2ap/editor.</p>
      <p>Fig. 2. DC2AP Metadata Editor</p>
      <p>By accessing the tool, the user has access to all the elements described in DC2AP.
For each element, there are two icons showing details of them. The icon shown in
Fig. 2(a) shows the rules for filling an element regarding to obligatoriness, occurrence
and value type. On the other hand, the icon displayed in Fig. 2(b) provides access to
detailed information of the element.</p>
      <p>The DC2AP Metadata Editor also provides fields for the multivalued elements of
the DC2AP. This tool allows the manipulation and sorting the list of values of these
fields using the icons on the right side of multivalued fields. The element
2.1 Alternative Title shown in Fig. 2 is an example of a multivalued element.
3.1</p>
      <sec id="sec-3-1">
        <title>Functionalities</title>
        <p>To date, the DC2AP Metadata Editor has two major functionalities: 1) metadata
validation and 2) generation of documentation in the RDF format, accessible by the
buttons Validate and RDF respectively as presented in Fig. 2.</p>
        <p>The Validate functionality verifies if the metadata is in accordance with the
obligatoriness rules of the DC2AP profile. If there are required elements that were not
reported, the tool will then report this information to user by means of a window that
contains a list of the errors found. After the validation of the metadata, it can be
exported to RDF files by means of the function Generate RDF. The use of DC2AP to
document analysis patterns in RDF files makes the metadata repository proposed by
APRI (Fig. 1) a specific domain linked data source.
3.2</p>
      </sec>
      <sec id="sec-3-2">
        <title>Example</title>
        <p>
          Part of the RDF code equivalent to the analysis pattern originally documented in
[
          <xref ref-type="bibr" rid="ref7">7</xref>
          ] is shown in Fig. 3. This code was generated by the DC2AP Metadata Editor after
validation of the metadata registered for the pattern. After generating this code, the
same could be exported to a RDF file and stored in a metadata repository of an APRI.
        </p>
        <p>The full version of the RDF file shown in Fig. 3 can be accessed by URI
http://purl.org/apri/metadata/UrbanStreetMesh-v1.</p>
        <p>
          To create the URI present in the RDF files generated by the DC2AP Metadata
Editor, this tool has been integrated into the PURL toolkit [
          <xref ref-type="bibr" rid="ref17">17</xref>
          ], which is an environment
for creating permanent identifiers for documents on the Web.
        </p>
        <p>The DC2AP Metadata Editor provides some of its functionalities by means of a
web service (DC2APWebService), in which the exchange of messages with the
external environment is via SOAP protocol. The goal of the DC2APWebService is to
allow developers of applications related to the domain of analysis patterns reuse the
DC2AP Metadata Editor functionalities without the need to access the system GUI or
redeploy them into their applications. This approach allows developers be free to
create their own application using resources provided by the DC2AP Metadata Editor
using languages and technologies of their choice, since the protocol SOAP is based on
XML and HTTP, universal technologies for messaging.</p>
        <p>The access to the DC2APWebService can be done via the URL:
http://www.ide.ufv.br/dc2ap/webservices/, where is possible to have
access to the following methods:


generateRdfScript() - Creating RDF script for the input metadata.</p>
        <p>validateResource() - Validate metadata according to the DC2AP rules.</p>
        <p>The method generateRdfScript() takes as parameters all the elements of the
DC2AP. This method then converts this input to a script RDF, similar to the script
shown in Fig. 3. The method validateResource() takes as parameters only the
Mandatory and Conditional DC2AP elements. It checks if the input conforms to the
validation rules of DC2AP and then returns a list of messages containing validation errors,
or an empty list if no error has been found.
4</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>Conclusions and Future Work</title>
      <p>The DC2AP Metadata Editor aims to improve the analysis patterns documentation
process by applying the DC2AP profile. Due to its functionality to export the
metadata to the RDF format, the DC2AP Metadata Editor allows the creation of digital
collections of machine-processable analysis patterns. Thus, this tool enables to document
analysis patterns in a better structured way. So, these patterns can be retrieved more
quickly and efficiently in APRI's repositories distributed on the Web.</p>
      <p>
        Creating documentation in the RDF format also aims to provide Linked Data.
When analysis patterns are described as Linked Data they have the reuse potential
expanded and can be better integrated with other data of heterogeneous sources [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ].
      </p>
      <p>This tool provides some of its functionality through Web services, allowing
application developers in the field of analysis patterns to use the resources of the DC2AP
Metadata Editor, regardless of the technology used for development and thus enabling
the reuse of computational resources in another scale.</p>
      <p>As future work is intend to provide new functionalities in the DC2AP Metadata
Editor and make them available as new Web services, as for example, version control
functionality for RDF files that are generated by the tool, thus allowing the user to
have a history of changes and improvements made in the documentation and also
manage its different versions. Furthermore, the aim is to adapt this tool to also behave
as a generic Dublin Core metadata editor, thereby allowing this new extension to be
used not only for analysis patterns documentation but for document any resource
which the Dublin Core may be applied.</p>
      <p>Acknowledgment. Project partially funded by the CNPq/MCT and FAPEMIG.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Armbrust</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fox</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Griffith</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Joseph</surname>
            ,
            <given-names>A. D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Katz</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Konwinski</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lee</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Patterson</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rabkin</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Stoica</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zaharia</surname>
            ,
            <given-names>M.:</given-names>
          </string-name>
          <article-title>A View Of Cloud Computing</article-title>
          .
          <source>Communications of the ACM</source>
          .
          <volume>53</volume>
          (
          <issue>4</issue>
          ),
          <fpage>50</fpage>
          -
          <lpage>58</lpage>
          (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Berners-Lee</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>Weaving the Web: The Past, Present and Future of the World Wide Web by its Inventor</article-title>
          . Texere Publishing, London (
          <year>2000</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Bizer</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Heath</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Berners-Lee</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>Linked Data - The story so far</article-title>
          . In: Heath,
          <string-name>
            <given-names>T.</given-names>
            ,
            <surname>Hepp</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            ,
            <surname>Bizer</surname>
          </string-name>
          , C. (eds.)
          <source>IJSWIS</source>
          <year>2009</year>
          ,
          <volume>5</volume>
          (
          <issue>3</issue>
          ), pp.
          <fpage>1</fpage>
          -
          <lpage>22</lpage>
          . Elsevier (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Blaimer</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bortfeldt</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pankratz</surname>
          </string-name>
          , G.:
          <article-title>Patterns in object-oriented analysis</article-title>
          .
          <source>Working Paper n.451, Faculty of Business Administration and Economics</source>
          , University of Hagen (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>5. CatMDEdit, http://catmdedit.sourceforge.net</mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Morshed</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Caracciolo</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Johannsen</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Keizer</surname>
          </string-name>
          , J.:
          <article-title>Thesaurus alignment for Linked Data publishing</article-title>
          .
          <source>In: International Conference on Dublin Core and Metadata Applications</source>
          <year>2011</year>
          , pp.
          <fpage>37</fpage>
          -
          <lpage>46</lpage>
          . (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Lisboa-Filho</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Iochpe</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Borges</surname>
            ,
            <given-names>K. A. V.</given-names>
          </string-name>
          :
          <article-title>Analysis Patterns for GIS data schema reuse on urban management applications</article-title>
          .
          <source>CLEI Electronic Journal</source>
          .
          <volume>5</volume>
          (
          <issue>2</issue>
          ),
          <fpage>01</fpage>
          -
          <lpage>15</lpage>
          (
          <year>2002</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Meszaros</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Doble</surname>
            ,
            <given-names>J.:</given-names>
          </string-name>
          <article-title>A pattern language for pattern writing</article-title>
          . In: Martin,
          <string-name>
            <given-names>R. C.</given-names>
            ,
            <surname>Riehle</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            ,
            <surname>Buschmann</surname>
          </string-name>
          ,
          <string-name>
            <surname>F</surname>
          </string-name>
          . (eds.),
          <source>Pattern languages of program design 3</source>
          , pp.
          <fpage>529</fpage>
          -
          <lpage>574</lpage>
          . AddisonWesley, Boston (
          <year>1997</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Pantoquilho</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Raminhos</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Araújo</surname>
            ,
            <given-names>J.:</given-names>
          </string-name>
          <article-title>Analysis Patterns specifications: Filling the gaps</article-title>
          .
          <source>In: 2nd Viking Conference Pattern Languages of Programs</source>
          , pp.
          <fpage>169</fpage>
          -
          <lpage>180</lpage>
          . (
          <year>2003</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Vegi</surname>
            ,
            <given-names>L. F. M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Peixoto</surname>
            ,
            <given-names>D. A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Soares</surname>
            ,
            <given-names>L. S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lisboa-Filho</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Oliveira</surname>
            ,
            <given-names>A. P.:</given-names>
          </string-name>
          <article-title>An infrastructure oriented for cataloging services and reuse of Analysis Patterns</article-title>
          . In: Daniel,
          <string-name>
            <given-names>F.</given-names>
            ,
            <surname>Barkaoui</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            ,
            <surname>Dustdar</surname>
          </string-name>
          , S. (eds.)
          <source>Business Process Management Workshops</source>
          <year>2011</year>
          , LNBIP vol.
          <volume>100</volume>
          , Part 4, pp.
          <fpage>338</fpage>
          -
          <lpage>343</lpage>
          . Springer, Heidelberg (
          <year>2012</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Vegi</surname>
            ,
            <given-names>L. F. M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lisboa-Filho</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Crompvoets</surname>
            ,
            <given-names>J.:</given-names>
          </string-name>
          <article-title>A Machine-Processable Dublin Core Application Profile for Analysis Patterns to provide Linked Data</article-title>
          .
          <source>In: International Conference of Dublin Core and Metadata Applications</source>
          , pp.
          <fpage>23</fpage>
          -
          <lpage>32</lpage>
          . DCMI,
          <string-name>
            <surname>Kuching</surname>
          </string-name>
          , Malaysia (
          <year>2012</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Vegi</surname>
            ,
            <given-names>L. F. M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lisboa-Filho</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Costa</surname>
            ,
            <given-names>G. L. S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Oliveira</surname>
            ,
            <given-names>A. P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Braga</surname>
            ,
            <given-names>J. L.</given-names>
          </string-name>
          :
          <article-title>DC2AP: A Dublin Core application profile to analysis patterns</article-title>
          .
          <source>In: 24th International Conference on Software Engineering and Knowledge Engineering</source>
          , pp.
          <fpage>511</fpage>
          -
          <lpage>516</lpage>
          . KSI,
          <string-name>
            <surname>Skokie</surname>
          </string-name>
          (
          <year>2012</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>13. xMET Metadata Editor, http://www.anzlic.org.au/</mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Yang</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Goodchild</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Huang</surname>
            ,
            <given-names>Q.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nebert</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Raskin</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Xu</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bambacus</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fay</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>Spatial cloud computing: how can the geospatial sciences use and help shape cloud computing?</article-title>
          .
          <source>International Journal of Digital Earth</source>
          .
          <volume>4</volume>
          (
          <issue>4</issue>
          ),
          <fpage>305</fpage>
          -
          <lpage>329</lpage>
          (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Weiss</surname>
          </string-name>
          , A.:
          <article-title>Computing in the clouds</article-title>
          .
          <source>networker</source>
          .
          <volume>11</volume>
          (
          <issue>4</issue>
          ),
          <fpage>16</fpage>
          -
          <lpage>25</lpage>
          (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16. Dublin Core Metadata Initiative.: Dublin Core metadata element set,
          <source>v.1</source>
          .0: Reference description, http://www.dublincore.org/documents/1998/09/dces/
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>17. Persistent Uniform Resource Locators, http://purl.oclc.org/docs/index.html</mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>18. Google Web Toolkit, http://developers.google.com/web-toolkit/</mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>