Alvis-NLPPlatform

 view release on metacpan or  search on metacpan

Changes  view on Meta::CPAN

       - for some OS, Config::General returns while setting variables
         as yatea.rc is on read-inly mode


0.5    - Addition of missing packages in the installation file
         (Build.PL) 
       - Switching the Makefile.PL on Build.PL
       - Correction in the Yatea wrapper in the handling of the output file.

0.4    - Correction in the function sigint handler : nlp_host and
         nlp_port are now declared as global.
       - Correction in the TermTagging : language switch was well
         taken into account
       - Correction in the management of the ".proc_id" file
       - correction in the computing of the xml rendering time
         (the variable is set to zero ;-)
       - stderr when NLP tools are called, is redirected in a log file
       - addition of a variable DEBUG defining a debug mode (temporary
         files are not removed)
       - alvis-nlp-standalone can read a file given in argument or on
         the STDIN stream

examples/InputDocument.xml  view on Meta::CPAN

              <section>token_id_follows_list_refid_token()</section> token_id_follows_list_refid_token($list_refid_token, $token_to_search); 
              <section>The method returns 1 if the token $token_to_search is the foollwing of the last token of the list $list_refid_token , 0 else.</section></section>
            <section title="token_id_just_before_last_of_list_refid_token()">
              <section>token_id_just_before_last_of_list_refid_token()</section> token_id_just_before_last_of_list_refid_token($list_refid_token, $token_to_search); 
              <section>The method returns 1 if the token $token_to_search is just before the first token of the list $list_refid_token , 0 else.</section></section>
            <section title="unparseable_id()">
              <section>unparseable_id()</section> unparseable_id($id) 
              <section>The method checks if the id have been parsed or not. If not, it prints a warning.</section></section></section>
          <section title="PLATFORM CONFIGURATION">
            <section>PLATFORM CONFIGURATION</section> 
            <section>The configuration file of the NLP Platform is composed of global variables and divided into several sections:</section>  
            <section>Global variables. 
              <section>The two mandatory variables are ALVISTMP and PRESERVEWHITESPACE (in the XML_INPUT section).</section>  
              <section>
                <section>ALVISTMP : it defines the temporary directory used during the annotation process. The files are recorded in (XML files and input/output of the NLP tools) during the annotation step. It must be writable to the user the process...
              <section>
                <section>DEBUG : this variable indicates if the NLP platform is run in a debug mode or not. The value are 1 (debug mode) or 0 (no debug mode). Default value is 0. The main consequence of the debug mode is to keep the temporary file.</...
              <section>Additional variables and environement variables can be used if they are interpolated in the configuration file. For instance, in the default configuration file, we add</section>  
              <section>
                <section>PLATFORM_ROOT : directory where are installed NLP tools and resources.</section></section> 
              <section>

lib/Alvis/NLPPlatform.pm  view on Meta::CPAN

=head2 platform_reset()

   platform_reset()

The method empties or resets the structures and variables attached to
a processed document.

=head1 PLATFORM CONFIGURATION

The configuration file of the NLP Platform is composed of global
variables and divided into several sections:

=over 

=item * Global variables.

The two mandatory variables are C<ALVISTMP> and C<PRESERVEWHITESPACE>
 (in the XML_INPUT section). 

lib/Alvis/NLPPlatform/data/example-fr.txt  view on Meta::CPAN

Comment mesurer la couverture d'une ressource terminologique pour un corpus ?

Cet article propose une définition formelle de la notion de couverture lexicale. Celleci repose sur un ensemble de quatre métriques qui donnent une vue globale de l'adéquation d'une ressource lexicale à un corpus et permettent ainsi de guider le ...

lib/Alvis/NLPPlatform/data/example-fr.xml  view on Meta::CPAN

cyB2YWxldXJzIG9idGVudWVzIHBlcm1ldCBlZmZlY3RpdmVtZW50IGRlIGRpc2Nlcm5lciBkaWZm
w6lyZW50cyB0eXBlcyBkZSByZWxhdGlvbnMgZW50cmUgcmVzc291cmNlcyBldCBjb3JwdXMuIENl
cyBwcmVtaWVycyByw6lzdWx0YXRzIG1vbnRyZW50IGwnaW50w6lyw6p0IGRlIGNldHRlIGFwcHJv
Y2hlIHRvdXQgZW4gb3V2cmFudCBkZXMgdm9pZXMgZCdhbcOpbGlvcmF0aW9uLgo=
</originalDocument>
      <canonicalDocument>        
        <section>
          <section title="Comment mesurer la couverture d'une ressource terminologique pour un corpus ?">
	    <section>Comment mesurer la couverture d'une ressource terminologique pour un corpus ?
	    </section>
	    <section>Cet article propose une définition formelle de la notion de couverture lexicale. Celleci repose sur un ensemble de quatre métriques qui donnent une vue globale de l'adéquation d'une ressource lexicale à un corpus et permettent ainsi...
            </section>
          </section>
        </section>
      </canonicalDocument>
    </acquisition>
  </documentRecord>
</documentCollection>