<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//TaxonX//DTD Taxonomic Treatment Publishing DTD v0 20100105//EN" "../../nlm/tax-treatment-NS0.dtd">
<article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:tp="http://www.plazi.org/taxpub" article-type="research-article" dtd-version="3.0" xml:lang="en">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">109</journal-id>
      <journal-id journal-id-type="index">urn:lsid:arphahub.com:pub:3dc5f44e-8666-58db-bc76-a455210e8891</journal-id>
      <journal-title-group>
        <journal-title xml:lang="en">JUCS - Journal of Universal Computer Science</journal-title>
        <abbrev-journal-title xml:lang="en">jucs</abbrev-journal-title>
      </journal-title-group>
      <issn pub-type="ppub">0948-695X</issn>
      <issn pub-type="epub">0948-6968</issn>
      <publisher>
        <publisher-name>Journal of Universal Computer Science</publisher-name>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="doi">10.3217/jucs-021-04-0604</article-id>
      <article-id pub-id-type="publisher-id">23116</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Research Article</subject>
        </subj-group>
        <subj-group subj-group-type="scientific_subject">
          <subject>H.0 - GENERAL</subject>
          <subject>I.2.7 - Natural Language Processing</subject>
          <subject>I.7 - DOCUMENT AND TEXT PROCESSING</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>From Terminology Extraction to Terminology Validation:An Approach Adapted to Log Files</article-title>
      </title-group>
      <contrib-group content-type="authors">
        <contrib contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Saneifar</surname>
            <given-names>Hassan</given-names>
          </name>
          <email xlink:type="simple">hassan.saneifar@gmail.com</email>
          <xref ref-type="aff" rid="A1">1</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Bonniol</surname>
            <given-names>Stéphane</given-names>
          </name>
          <xref ref-type="aff" rid="A2">2</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Poncelet</surname>
            <given-names>Pascal</given-names>
          </name>
          <xref ref-type="aff" rid="A1">1</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Roche</surname>
            <given-names>Mathieu</given-names>
          </name>
          <xref ref-type="aff" rid="A3">3</xref>
        </contrib>
      </contrib-group>
      <aff id="A1">
        <label>1</label>
        <addr-line content-type="verbatim">LIRMM - University Montpellier 2 - CNRS, Montpellier, France</addr-line>
        <institution>LIRMM - University Montpellier 2 - CNRS</institution>
        <addr-line content-type="city">Montpellier</addr-line>
        <country>France</country>
      </aff>
      <aff id="A2">
        <label>2</label>
        <addr-line content-type="verbatim">Satin Technologies, Montpellier, France</addr-line>
        <institution>Satin Technologies</institution>
        <addr-line content-type="city">Montpellier</addr-line>
        <country>France</country>
      </aff>
      <aff id="A3">
        <label>3</label>
        <addr-line content-type="verbatim">TETIS - Cirad - Irstea - AgroParisTech, Montpellier, France</addr-line>
        <institution>TETIS - Cirad - Irstea - AgroParisTech</institution>
        <addr-line content-type="city">Montpellier</addr-line>
        <country>France</country>
      </aff>
      <author-notes>
        <fn fn-type="corresp">
          <p>Corresponding author: Hassan Saneifar (<email xlink:type="simple">hassan.saneifar@gmail.com</email>).</p>
        </fn>
        <fn fn-type="edited-by">
          <p>Academic editor: </p>
        </fn>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2015</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>01</day>
        <month>04</month>
        <year>2015</year>
      </pub-date>
      <volume>21</volume>
      <issue>4</issue>
      <fpage>604</fpage>
      <lpage>635</lpage>
      <uri content-type="arpha" xlink:href="http://openbiodiv.net/9AEA682A-CEC8-5650-A50C-6644BE5862A3">9AEA682A-CEC8-5650-A50C-6644BE5862A3</uri>
      <uri content-type="zenodo_dep_id" xlink:href="https://zenodo.org/record/5505025">5505025</uri>
      <history>
        <date date-type="received">
          <day>22</day>
          <month>11</month>
          <year>2012</year>
        </date>
        <date date-type="accepted">
          <day>26</day>
          <month>03</month>
          <year>2015</year>
        </date>
      </history>
      <permissions>
        <copyright-statement>Hassan Saneifar, Stéphane Bonniol, Pascal Poncelet, Mathieu Roche</copyright-statement>
        <license license-type="creative-commons-attribution" xlink:href="" xlink:type="simple">
          <license-p>This article is freely available under the J.UCS Open Content License.</license-p>
        </license>
      </permissions>
      <abstract>
        <label>Abstract</label>
        <p>Log files generated by computational systems contain relevant and essential information. In some application areas like the design of integrated circuits, log files generated by design tools contain information which can be used in management information systems to evaluate the final products. However, the complexity of such textual data raises some challenges concerning the extraction of information from log files. Log files are usually multi-source, multi-format, and have a heterogeneous and evolving structure. Moreover, they usually do not respect natural language grammar and structures even though they are written in English. Classical methods of information extraction such as terminology extraction methods are particularly irrelevant to this context. In this paper, we introduce our approach EXTERLOG to extract terminology from log files. We detail how it deals with the specific features of such textual data. The performance is emphasized by favoring the most relevant terms of the domain based on a scoring function which uses a Web and context based measure. The experiments show that EXTERLOG is a well-adapted approach for terminology extraction from log files.</p>
      </abstract>
    </article-meta>
  </front>
</article>
