<!doctype HTML public "-//W3C//DTD HTML 4.0 Frameset//EN">

<html>

<!--(==============================================================)-->
<!--(Document created with RoboEditor. )============================-->
<!--(==============================================================)-->

<head>

<title>unsealed</title>

<!--(Meta)==========================================================-->

<meta name=generator content="RoboHELP by eHelp Corporation - www.ehelp.com">
<meta name=generator-major-version content=0.1>
<meta name=generator-minor-version content=1>
<meta name=filetype content=kadov>
<meta name=filetype-version content=1>
<meta name=page-count content=1>
<meta name=layout-height content=711>
<meta name=layout-width content=916>
<meta name=date content="05 5, 2002 0:28:17 AM">


<!--(Links)=========================================================-->

<link rel=StyleSheet href=default.css>



</head>

<!--(Body)==========================================================-->


<body>

<h1>unsealed</h1>

<h2>Purpose</h2>

<p>In a normal rule reduction, the suggested node is &quot;sealed&quot;. 
 <!--kadov_tag{{<spaces>}}-->&nbsp;<!--kadov_tag{{</spaces>}}-->This makes 
 it inaccessible to the @NODES selection mechanism, which looks for nodes 
 in the parse tree, then takes their phrase of children to use in searching 
 for rule matches. <!--kadov_tag{{<spaces>}}-->&nbsp;<!--kadov_tag{{</spaces>}}-->In 
 order to make a node accessible to be &quot;looked inside of&quot; by 
 the context selection algorithm, you can use the <span style="font-weight: bold;">unsealed</span> 
 suggested element modifier.</p>

<h2>Remarks</h2>

<p>Unsealed is not related to the singlet-base mechanism described elsewhere.</p>

<p>The @NODES selector starts at the root of the parse tree, then looks 
 only within <span style="font-style: italic;">a path of unsealed nodes</span> 
 for appropriately labeled nodes within which to perform rule matching. 
 <!--kadov_tag{{<spaces>}}-->&nbsp;<!--kadov_tag{{</spaces>}}-->So keep 
 nodes unsealed that you want to look within. <!--kadov_tag{{<spaces>}}-->&nbsp;<!--kadov_tag{{</spaces>}}-->Note 
 that the @PATH selector does not care if nodes are sealed or not.</p>

<h2>Example</h2>

<p># This rule &quot;roughs out&quot; a set of nodes ending in a period, 
 creating a _sentence node.<br>
# This rule also makes such a _sentence node accessible to further rule 
 matching.<br>
@RULES<br>
_sentence [unsealed] &lt;- <!--kadov_tag{{<spaces>}}-->&nbsp;<!--kadov_tag{{</spaces>}}-->_xWILD 
 [fail=( \. )] \. @@<br>
<br>
# Say that in a subsequent pass (shown below), we want to process _np nodes 
 within _sentence<br>
# nodes in order to count the nouns within noun phrases. <!--kadov_tag{{<spaces>}}-->&nbsp;<!--kadov_tag{{</spaces>}}-->The 
 @NODES _np<br>
# specifier will only look for _np nodes within ancestors that are <span 
 style="font-style: italic;">unsealed</span>. <!--kadov_tag{{<spaces>}}-->&nbsp;<!--kadov_tag{{</spaces>}}-->If 
 the<br>
# sentence rule above doesn't use unsealed, then noun phrases within those<br>
# sentences won't be traversed.<br>
@NODES _np<br>
<br>
@POST<br>
 <!--kadov_tag{{<spaces>}}-->&nbsp;<!--kadov_tag{{</spaces>}}-->++X(&quot;nouns&quot;);<br>
@RULES<br>
_xNIL &lt;- _noun @@</p>

<h2>See Also</h2>

<p style="margin-bottom: 0;">See <a href="NLP_PP_Stuff/Suggested_element_modifiers.htm">Suggested 
 Element Modifiers</a>.</p>

<p>&nbsp;</p>

</body>

</html>
