Revision: 16005
http://gate.svn.sourceforge.net/gate/?rev=16005&view=rev
Author: valyt
Date: 2012-08-10 10:04:27 +0000 (Fri, 10 Aug 2012)
Log Message:
-----------
Added note about JAPE Plus being able to match zero-length annotations.
Modified Paths:
--------------
userguide/trunk/jape.tex
Modified: userguide/trunk/jape.tex
===================================================================
--- userguide/trunk/jape.tex 2012-08-10 01:19:20 UTC (rev 16004)
+++ userguide/trunk/jape.tex 2012-08-10 10:04:27 UTC (rev 16005)
@@ -2080,18 +2080,28 @@
Additionally, the Java JIT optimisations can also apply in this set-up.
\end{description}
-One small difference between JAPE and JAPE Plus is that the latter behaves in a
-more deterministic fashion. There are cases where multiple paths inside the
-annotation graph can be matched with the same precedence, e.g. when the same
-JAPE rule matches different sets of annotations using different branches of a
-disjunction in the rule. In such situations, the standard JAPE engine will pick
-one of the possible paths at random and apply the rule using it. Separate
-executions of the same grammar over the same document can thus lead to
different
-results. By contrast, JAPE Plus will always choose the same matching set of
-annotations. It is however not possible to know a priori which one will be
-chosen, unless the rules are re-written to remove the ambiguity (solution which
-is also possible with the standard JAPE engine).
+There are a few small differences in the behaviour of JAPE and JAPE Plus:
+\begin{itemize}
+ \item JAPE Plus behaves in a more deterministic fashion. There are cases
where
+ multiple paths inside the annotation graph can be matched with the same
+ precedence, e.g. when the same JAPE rule matches different sets of
annotations
+ using different branches of a disjunction in the rule. In such situations,
the
+ standard JAPE engine will pick one of the possible paths at random and apply
+ the rule using it. Separate executions of the same grammar over the same
+ document can thus lead to different results. By contrast, JAPE Plus will
+ always choose the same matching set of annotations. It is however not
possible
+ to know a priori which one will be chosen, unless the rules are re-written to
+ remove the ambiguity (solution which is also possible with the standard JAPE
+ engine).
+ \item JAPE Plus is capable of matching zero-length annotations, i.e.
+ annotations for which the start and end offsets are the same, so they cover
+ no document text. The standard JAPE engine simply ignores such annotations,
+ while JAPE Plus allows their use in rules. This can be useful in matching
+ annotations converted from the original markup, for example HTML \verb!<br>!
+ tags will never have any text content.
+\end{itemize}
+
\begin{figure}[htb]
\begin{center}
\includegraphics[scale=0.5]{jape-v-japeplus.png}
This was sent by the SourceForge.net collaborative development platform, the
world's largest Open Source development site.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
GATE-cvs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/gate-cvs
