You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@uima.apache.org by pk...@apache.org on 2013/08/19 15:39:44 UTC
svn commit: r1515410 - /uima/sandbox/ruta/trunk/ruta-docbook/src/docbook/
Author: pkluegl
Date: Mon Aug 19 13:39:44 2013
New Revision: 1515410
URL: http://svn.apache.org/r1515410
Log:
no jira - fixed some typos
Modified:
uima/sandbox/ruta/trunk/ruta-docbook/src/docbook/tools.ruta.language.actions.xml
uima/sandbox/ruta/trunk/ruta-docbook/src/docbook/tools.ruta.language.conditions.xml
uima/sandbox/ruta/trunk/ruta-docbook/src/docbook/tools.ruta.language.declarations.xml
uima/sandbox/ruta/trunk/ruta-docbook/src/docbook/tools.ruta.language.expressions.xml
uima/sandbox/ruta/trunk/ruta-docbook/src/docbook/tools.ruta.language.xml
uima/sandbox/ruta/trunk/ruta-docbook/src/docbook/tools.ruta.overview.xml
uima/sandbox/ruta/trunk/ruta-docbook/src/docbook/tools.ruta.workbench.install.xml
Modified: uima/sandbox/ruta/trunk/ruta-docbook/src/docbook/tools.ruta.language.actions.xml
URL: http://svn.apache.org/viewvc/uima/sandbox/ruta/trunk/ruta-docbook/src/docbook/tools.ruta.language.actions.xml?rev=1515410&r1=1515409&r2=1515410&view=diff
==============================================================================
--- uima/sandbox/ruta/trunk/ruta-docbook/src/docbook/tools.ruta.language.actions.xml (original)
+++ uima/sandbox/ruta/trunk/ruta-docbook/src/docbook/tools.ruta.language.actions.xml Mon Aug 19 13:39:44 2013
@@ -281,7 +281,7 @@ Document{->CONFIGURE(HtmlAnnotator, "onl
<para>
The CREATE action is similar to the MARK action. It also
annotates the matched text fragments with a type annotation, but
- additionally assigns values to a choosen subset of the type's feature
+ additionally assigns values to a chosen subset of the type's feature
elements.
</para>
<section>
@@ -352,7 +352,7 @@ Document{->CONFIGURE(HtmlAnnotator, "onl
</title>
<para>
<programlisting><![CDATA[DYNAMICANCHORING(BooleanExpression
- (,NumberExpression(,NumberExpression)?)?)]]></programlisting>
+ (,NumberExpression(,NumberExpression)?)?)]]></programlisting>
</para>
</section>
<section>
@@ -413,7 +413,7 @@ Document{->EXEC(NamedEntities, {Person,
<section id="ugr.tools.ruta.language.actions.fill">
<title>FILL</title>
<para>
- The FILL action fills a choosen subset of the given type's
+ The FILL action fills a chosen subset of the given type's
feature elements.
</para>
<section>
@@ -493,7 +493,7 @@ Document{->EXEC(NamedEntities, {Person,
<para>
This action creates a complex structure: an annotation with
features. The optionally passed indexes (NumberExpressions after the
- TypeExpression) can be used to create an annotation that spanns the
+ TypeExpression) can be used to create an annotation that spans the
matched information of several rule elements. The features are
collected using the indexes of the rule elements of the complete
rule.
@@ -546,7 +546,7 @@ A B{-> GATHER(C, 1, 2, "a" = 1, "b" = 2)
<tbody>
<row>
<entry>dominant</entry>
- <entry>finds the most occuring element</entry>
+ <entry>finds the most occurring element</entry>
</row>
</tbody>
</tgroup>
Modified: uima/sandbox/ruta/trunk/ruta-docbook/src/docbook/tools.ruta.language.conditions.xml
URL: http://svn.apache.org/viewvc/uima/sandbox/ruta/trunk/ruta-docbook/src/docbook/tools.ruta.language.conditions.xml?rev=1515410&r1=1515409&r2=1515410&view=diff
==============================================================================
--- uima/sandbox/ruta/trunk/ruta-docbook/src/docbook/tools.ruta.language.conditions.xml (original)
+++ uima/sandbox/ruta/trunk/ruta-docbook/src/docbook/tools.ruta.language.conditions.xml Mon Aug 19 13:39:44 2013
@@ -260,9 +260,9 @@
<section id="ugr.tools.ruta.language.conditions.currentcount">
<title>CURRENTCOUNT</title>
<para>
- The CURRENTCOUNT condition numbers all occurences of the matched
+ The CURRENTCOUNT condition numbers all occurrences of the matched
type within the whole document consecutively, thus assigning an index
- to each occurence. Additionally, it stores the index of the matched
+ to each occurrence. Additionally, it stores the index of the matched
annotation in a numerical variable, if one is passed. The condition
evaluates true if the index of the matched annotation is within a
specified interval. If no interval is passed, the condition always
Modified: uima/sandbox/ruta/trunk/ruta-docbook/src/docbook/tools.ruta.language.declarations.xml
URL: http://svn.apache.org/viewvc/uima/sandbox/ruta/trunk/ruta-docbook/src/docbook/tools.ruta.language.declarations.xml?rev=1515410&r1=1515409&r2=1515410&view=diff
==============================================================================
--- uima/sandbox/ruta/trunk/ruta-docbook/src/docbook/tools.ruta.language.declarations.xml (original)
+++ uima/sandbox/ruta/trunk/ruta-docbook/src/docbook/tools.ruta.language.declarations.xml Mon Aug 19 13:39:44 2013
@@ -219,7 +219,7 @@ Document{->CALL(AnotherScript)}; // <- r
Analysis Engine (ENGINE): loads the given descriptor and creates an external analysis
engine. The descriptor must be located in the descriptor paths.
The type system needed for the analysis engine has
- to be imported seperately. Please mind the filtering setting when
+ to be imported separately. Please mind the filtering setting when
calling an external analysis engine.
</para>
</listitem>
@@ -228,7 +228,7 @@ Document{->CALL(AnotherScript)}; // <- r
Analysis Engine (UIMAFIT): loads the given class and creates an external analysis
engine. Please mind that the implementation of the analysis engine needs to be available.
The type system needed for the analysis engine has
- to be imported seperately. Please mind the filtering setting when
+ to be imported separately. Please mind the filtering setting when
calling an external analysis engine.
</para>
</listitem>
Modified: uima/sandbox/ruta/trunk/ruta-docbook/src/docbook/tools.ruta.language.expressions.xml
URL: http://svn.apache.org/viewvc/uima/sandbox/ruta/trunk/ruta-docbook/src/docbook/tools.ruta.language.expressions.xml?rev=1515410&r1=1515409&r2=1515410&view=diff
==============================================================================
--- uima/sandbox/ruta/trunk/ruta-docbook/src/docbook/tools.ruta.language.expressions.xml (original)
+++ uima/sandbox/ruta/trunk/ruta-docbook/src/docbook/tools.ruta.language.expressions.xml Mon Aug 19 13:39:44 2013
@@ -304,7 +304,7 @@ BooleanListExpression -> BooleanListVa
<section id="ugr.tools.ruta.language.expressions.features">
<title>Feature Expressions</title>
<para>
- Feature expression can be used in different situations, e.g., for resticting the match of a rule element,
+ Feature expression can be used in different situations, e.g., for restricting the match of a rule element,
as an implicit condition or as an implicit action.
<programlisting><![CDATA[FeatureExpression -> TypeExpression "." DottedIdentifier
FeatureMatchExpression -> FeatureExpression "==" Expression
Modified: uima/sandbox/ruta/trunk/ruta-docbook/src/docbook/tools.ruta.language.xml
URL: http://svn.apache.org/viewvc/uima/sandbox/ruta/trunk/ruta-docbook/src/docbook/tools.ruta.language.xml?rev=1515410&r1=1515409&r2=1515410&view=diff
==============================================================================
--- uima/sandbox/ruta/trunk/ruta-docbook/src/docbook/tools.ruta.language.xml (original)
+++ uima/sandbox/ruta/trunk/ruta-docbook/src/docbook/tools.ruta.language.xml Mon Aug 19 13:39:44 2013
@@ -551,7 +551,7 @@ Document{->MARKFAST(FistName, FirstNameL
The file ending for this is <quote>.mtwl</quote>. It is generated from
several ordinary WORDLISTs given as simple text files. It contains special
nodes that provide additional information about the original file. These
- kind of WORDLIST is useful, if several fifferent WORDLISTs are used within
+ kind of WORDLIST is useful, if several different WORDLISTs are used within
a UIMA Ruta script. Using five different lists results in five rules using
the MARKFAST action. The documents to annotate are thus searched five
times resulting in a complexity of 5*O(m*log(n)) With a multi tree
Modified: uima/sandbox/ruta/trunk/ruta-docbook/src/docbook/tools.ruta.overview.xml
URL: http://svn.apache.org/viewvc/uima/sandbox/ruta/trunk/ruta-docbook/src/docbook/tools.ruta.overview.xml?rev=1515410&r1=1515409&r2=1515410&view=diff
==============================================================================
--- uima/sandbox/ruta/trunk/ruta-docbook/src/docbook/tools.ruta.overview.xml (original)
+++ uima/sandbox/ruta/trunk/ruta-docbook/src/docbook/tools.ruta.overview.xml Mon Aug 19 13:39:44 2013
@@ -181,7 +181,7 @@ W{REGEXP("dog") -> MARK(Animal)};]]></pr
In the part of the conditions, boolean expressions and feature match expression can be applied, and in the part of the actions,
type expressions and feature assignment expression can be added. The following example contains one implicit condition and one implicit action.
The additional condition is a boolean expression (boolean variable), which is set to <quote>true</quote>, and therefore is always fulfills the condition.
- The <quote>MARK</quote> action was replaced by a type expression, which refer to the type <quote>Animal</quote>. The follwong rule shows, therefore,
+ The <quote>MARK</quote> action was replaced by a type expression, which refer to the type <quote>Animal</quote>. The following rule shows, therefore,
the same behavior as the rule in the last example.
</para>
@@ -244,10 +244,10 @@ Document{-> MARKFAST(Animal, AnimalsList
<para>
There two more special symbols that can be used to link rule elements. If the symbol <quote>|</quote> is replaced by the
- symbol <quote><![CDATA[&]]></quote> in the last exmaple, then the token after the animal need to be a comma and a semicolon, which is of course not possible.
+ symbol <quote><![CDATA[&]]></quote> in the last example, then the token after the animal need to be a comma and a semicolon, which is of course not possible.
Another symbol with a special meaning is <quote>%</quote>, which cannot only be used within a composed rule element (parentheses).
- This symbol can be interpreted as a global <quote>and</quote>: It links several rules, which only fire, if all rules have sucessfully matched.
- In the following example, an annoations of the type <quote>FoundIt</quote> is created, if the document contains two periods in a row and two commas in a row:
+ This symbol can be interpreted as a global <quote>and</quote>: It links several rules, which only fire, if all rules have successfully matched.
+ In the following example, an annotation of the type <quote>FoundIt</quote> is created, if the document contains two periods in a row and two commas in a row:
</para>
<programlisting><![CDATA[PERIOD PERIOD % COMMA COMMA{-> FoundIt};]]></programlisting>
@@ -399,7 +399,7 @@ NUM{PARSE(moneyAmount)} SPECIAL{REGEXP("
</para>
<para>
- Using feature expression for conditions and action, can reduce the complexity of a rule. The first rule in the follwing example set the value of the feature
+ Using feature expression for conditions and action, can reduce the complexity of a rule. The first rule in the following example set the value of the feature
<quote>currency</quote> of the annotation of the type <quote>MoneyAmount</quote> to <quote>Euro</quote>, if it was <quote>â¬</quote> before.
The second rule creates an annotation of the type <quote>LessThan</quote> for all annotations of the type <quote>MoneyAmount</quote>,
if their amount is less than 100 and the currency is <quote>Euro</quote>.
@@ -478,7 +478,7 @@ BLOCK(ForEach) Sentence{} {
]]></programlisting>
<para>
- Here, the rule in the block statement is performed for each occurence of an annotation of the type <quote>Sentence</quote>.
+ Here, the rule in the block statement is performed for each occurrence of an annotation of the type <quote>Sentence</quote>.
The rule within the block matches on the complete document, which is the current sentence in the context of the block statement.
As a consequence, this example creates an annotation of the type <quote>SentenceWithNoLeadingNP</quote> for each sentence
that does not start with a NP annotation.
@@ -513,7 +513,7 @@ Sentence{-> SentenceWithNPNP}<-{
<para>
To be more precise, this rule matches on all documents like <quote>Apache UIMA</quote>, <quote>Apache UIMA</quote>, <quote>ApacheUIMA</quote>,
<quote><![CDATA[Apache <b>UIMA</b>]]></quote>. There are two main reasons for this: First of all, it depends on how the available annotations are defined. The default seeder
- for the inital annotations creates an annotation for all characters until an upper case character occurs. Thus, the string <quote>ApacheUIMA</quote> consists of
+ for the initial annotations creates an annotation for all characters until an upper case character occurs. Thus, the string <quote>ApacheUIMA</quote> consists of
two tokens.
However, more important, the UIMA Ruta language provides a concept of visibility of the annotations. By default, all annotations of the types
<quote>SPACE</quote>, <quote>NBSP</quote>, <quote>BREAK</quote> and <quote>MARKUP</quote> (whitespace and XML elements) are filtered and not visible. This holds of course for
@@ -564,7 +564,7 @@ Document{-> EXEC(Modifier)};
The descriptor needs to be located in the folder specified by the parameter <link linkend="ugr.tools.ruta.ae.basic.parameter.descriptorPaths">descriptorPaths</link>.
The first rule deletes all text covered by annotations of the type <quote>Date</quote>. The second rule replaces the text of all annotations of the type <quote>MoneyAmount</quote>
with the string <quote><![CDATA[<MoneyAmount/>]]></quote>. The third rule remembers to set the background color of text in Headline annotation to green. The last rule
- finally performs all of these changes in an additonal view called <quote>modified</quote>, which is specified in the configuration parameters of the analysis engine.
+ finally performs all of these changes in an additional view called <quote>modified</quote>, which is specified in the configuration parameters of the analysis engine.
<xref linkend="ugr.tools.ruta.ae.modifier"/> and <xref linkend="ugr.tools.ruta.language.modification"/> provide a more detailed description.
</para>
@@ -574,7 +574,7 @@ Document{-> EXEC(Modifier)};
implementation, to the UIMA Ruta project. If the UIMA Ruta script is applied in a UIMA Pipeline, then the configuration parameter
<link linkend="ugr.tools.ruta.ae.basic.parameter.additionalUimafitEngines">additionalUimafitEngines</link> has to list the class of the analysis engine.
The following example loads an analysis engine without an descriptor and applies it on the document. The additional list of types states that
- the annoations of those types created by the analysis engine should be available to the following Ruta rules.
+ the annotations of those types created by the analysis engine should be available to the following Ruta rules.
</para>
<programlisting><![CDATA[UIMAFIT my.package.impl.MyAnalysisEngine;
Modified: uima/sandbox/ruta/trunk/ruta-docbook/src/docbook/tools.ruta.workbench.install.xml
URL: http://svn.apache.org/viewvc/uima/sandbox/ruta/trunk/ruta-docbook/src/docbook/tools.ruta.workbench.install.xml?rev=1515410&r1=1515409&r2=1515410&view=diff
==============================================================================
--- uima/sandbox/ruta/trunk/ruta-docbook/src/docbook/tools.ruta.workbench.install.xml (original)
+++ uima/sandbox/ruta/trunk/ruta-docbook/src/docbook/tools.ruta.workbench.install.xml Mon Aug 19 13:39:44 2013
@@ -55,7 +55,7 @@ under the License.
</listitem>
<listitem>
<para>
- Select <quote>Apche UIMA Ruta</quote> and (if not yet installed) <quote>Apache UIMA Eclipse tooling and runtime support</quote>
+ Select <quote>Apache UIMA Ruta</quote> and (if not yet installed) <quote>Apache UIMA Eclipse tooling and runtime support</quote>
by clicking into the related checkbox.
</para>
</listitem>
@@ -73,7 +73,7 @@ under the License.
<para>
On the next page, click <quote>Next</quote>
again. Now, the license
- agreement site is diplayed. To install UIMA Ruta read the license and
+ agreement site is displayed. To install UIMA Ruta read the license and
choose
<quote>I accept the ...</quote>
if you agree to it. Then,