This is an automated email from the ASF dual-hosted git repository.

aradzinski pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-nlpcraft-website.git


The following commit(s) were added to refs/heads/master by this push:
     new bcdca18  WIP.
bcdca18 is described below

commit bcdca18884f4d9a71027f843e307928a4d4a8c07
Author: Aaron Radzinski <[email protected]>
AuthorDate: Sat Mar 27 11:02:46 2021 -0700

    WIP.
---
 basic-concepts.html                  |  3 ++-
 blogs/composable_named_entities.html |  2 +-
 blogs/short_term_memory.html         | 10 +++++-----
 data-model.html                      |  4 ++--
 docs.html                            | 16 ++++++++--------
 examples/alarm_clock.html            |  2 +-
 index.html                           |  2 +-
 intent-matching.html                 |  2 +-
 8 files changed, 21 insertions(+), 20 deletions(-)

diff --git a/basic-concepts.html b/basic-concepts.html
index 4cc71ec..1d8d426 100644
--- a/basic-concepts.html
+++ b/basic-concepts.html
@@ -118,7 +118,8 @@ id: basic_concepts
             The process of detecting named entities is called Named Entity 
Recognition (NER). There are many
             different ways of how a certain named entity can be detected: 
through list of synonyms, by name, rule-based or by using
             statistical techniques like neural networks with large corpus of 
predefined data. NLPCraft allows you define
-            named entities through powerful DSL and also supports named 
entities that can be composed from other named entities
+            named entities through powerful <a 
href="/intent-matching.html">Intent Definition Language</a> (IDL)) and also 
supports named
+            entities that can be composed from other named entities
             including named entities from external projects such OpenNLP, 
spaCy or Stanford CoreNLP.
         </p>
         <p>
diff --git a/blogs/composable_named_entities.html 
b/blogs/composable_named_entities.html
index 199d292..cdb815d 100644
--- a/blogs/composable_named_entities.html
+++ b/blogs/composable_named_entities.html
@@ -264,7 +264,7 @@ publish_date: January 20, 2021
     <p>
         In this example, we defined a new named entity 
<code>custom:airport:usa</code>. In its definition we not only
         filter cities for the USA but also added a prefix that would indicate 
that this is an airport (learn more about
-        token DSL syntax <a 
href="https://nlpcraft.apache.org/data-model.html#dsl";>here</a>).
+        NLPCraft IDL syntax <a 
href="https://nlpcraft.apache.org/intent-matching.html";>here</a>). 
     </p>
     <p>
         Composable named entities can be nested but not recursive. All the 
normalized metadata of the constituent
diff --git a/blogs/short_term_memory.html b/blogs/short_term_memory.html
index b0eff75..cc40374 100644
--- a/blogs/short_term_memory.html
+++ b/blogs/short_term_memory.html
@@ -295,13 +295,13 @@ publish_date: July 26, 2019
         have the following 4 intents:
     </p>
     <ul>
-        <li><code>id=sale term={id=='sale'}</code></li>
-        <li><code>id=best_sale_person term={id=='sale'} 
term={id==best_employee}</code></li>
-        <li><code>id=buy term={id=='buy'}</code></li>
-        <li><code>id=buy_best_person term={id=='buy'} 
term={id==best_employee}</code></li>
+        <li><code>id=sale term={tok_id() == 'sale'}</code></li>
+        <li><code>id=best_sale_person term={tok_id() == 'sale'} term={tok_id() 
== best_employee}</code></li>
+        <li><code>id=buy term={tok_id() == 'buy'}</code></li>
+        <li><code>id=buy_best_person term={tok_id() == 'buy'} term={tok_id() 
== best_employee}</code></li>
     </ul>
     <p>
-        (this is actual <a href="/intent-matching.html#syntax">Intent DSL</a> 
used by NLPCraft -  
+        (this is actual <a href="/intent-matching.html">Intent Definition 
Language</a> (IDL) used by NLPCraft -
         <code>term</code> here is basically what's often referred to as a slot 
in other systems).
     </p>
     <p>
diff --git a/data-model.html b/data-model.html
index 5873d6e..0380010 100644
--- a/data-model.html
+++ b/data-model.html
@@ -524,7 +524,7 @@ intents:
         </p>
         <ul>
             <li>
-                New model elements can be added declaratively via token DSL, 
regex and macro expansion.
+                New model elements can be added declaratively via <a 
href="/intent-matching.html">Intent Definition Language</a> (IDL), regex and 
macro expansion.
             </li>
             <li>
                 New model elements can be also added programmatically for 
ultimate flexibility.
@@ -548,7 +548,7 @@ intents:
                 Model elements can compose named entities from many <a 
href="integrations.html#nlp">3rd party libraries</a>.
             </li>
             <li>
-                All properties of model elements (id, groups, parent & 
ancestors, values, and metadata) can be used in token and intent DSLs.
+                All properties of model elements (id, groups, parent & 
ancestors, values, and metadata) can be used in NLPCraft IDL.
             </li>
         </ul>
         <h3 class="section-title">User vs. Built-In Elements</h3>
diff --git a/docs.html b/docs.html
index 06408d6..100388f 100644
--- a/docs.html
+++ b/docs.html
@@ -26,23 +26,23 @@ id: overview
         <h2 class="section-title">Overview</h2>
         <p>
             Apache NLPCraft is a Java-based <a target=_blank 
href="https://www.apache.org/licenses/";>open source</a> library
-            for adding a natural language interaction interface to any 
applications. It can connect with
-            any private or public data source, and has no hardware or software 
lock-in. Its design based on advanced
-            <a href="/intent-matching.html">Intent Definition Language</a> 
(IDL) for defining non-trivial intents and unique fully deterministic intent 
matching
-            of the input utterances. You can build intents for NLPCraft using 
any JVM-based languages like Java, Scala, Kotlin, Groovy, etc. NLPCraft
-            exposes REST APIs for integration with end-user applications that 
can be written in any language or system.
+            for adding a natural language interface to modern applications.  
It enables people to interact with your products using voice or text. NLPCraft 
can connect with
+            any private or public data source, and has no hardware or software 
lock-ins. Its design is based on advanced
+            <a href="/intent-matching.html">Intent Definition Language</a> 
(IDL) for defining non-trivial intents and a fully deterministic intent matching
+            algorithm for the input utterances. You can build intents for 
NLPCraft using any JVM-based languages like Java, Scala, Kotlin, Groovy, etc. 
NLPCraft
+            exposes REST APIs for integration with any of your applications.
         </p>
         <p>
             One of the key features of NLPCraft is its use of IDL coupled with 
deterministic intent matching that are tailor made for
-            domain-specific natural language interface. This design doesn't 
force developers to use direct deep learning
+            <em>domain-specific</em> natural language interface. This design 
doesn't force developers to use direct deep learning
             approach with time consuming corpora development and model 
training - resulting in much a
             <em>simpler <span class="amp">&</span> faster</em> implementation.
         </p>
         <p>
             Another key aspect of NLPCraft is its initial focus on processing 
English language. Although it may sound
             counterintuitive, this narrower initial focus enables NLPCraft to 
deliver unprecedented ease of use combined with
-            unparalleled comprehension capabilities for English input 
out-of-the-box. It avoids watered down functionality and overly
-            complicated configuration and usage - following on project's 
"built for engineers by engineers" ethos.
+            unparalleled comprehension capabilities for English input 
out-of-the-box. It avoids academic, watered down functionality or overly
+            complicated configuration and usage - following on project's 
<em>"built for engineers by engineers"</em> ethos.
             English language is spoken by more
             than a billion people on this planet and is de facto standard 
global language of the business and commerce.
         </p>
diff --git a/examples/alarm_clock.html b/examples/alarm_clock.html
index 24f2882..b69f7c9 100644
--- a/examples/alarm_clock.html
+++ b/examples/alarm_clock.html
@@ -105,7 +105,7 @@ id: alarm_clock
         }
     ],
     "intents": [
-        "intent=alarm term~{id=='x:alarm'} term(nums)~{id=='nlpcraft:num' && 
~nlpcraft:num:unittype=='datetime' && 
~nlpcraft:num:isequalcondition==true}[0,7]"
+        "intent=alarm term~{tok_id() == 'x:alarm'} term(nums)~{tok_id() == 
'nlpcraft:num' && meta_token('nlpcraft:num:unittype') == 'datetime' && 
meta_token('nlpcraft:num:isequalcondition') == true}[0,7]"
     ]
 }
         </pre>
diff --git a/index.html b/index.html
index 48e77d5..c4274c5 100644
--- a/index.html
+++ b/index.html
@@ -129,7 +129,7 @@ layout: default
                 <h3 class="sub-section-title">Intent Definition Language</h3>
                 <section>
                     <p>
-                        Advanced Intent Definition Language (IDL) coupled with 
deterministic intent matching
+                        Advanced <a href="/intent-matching.html">Intent 
Definition Language</a> (IDL) coupled with deterministic intent matching
                         provide ease of use and unprecedented expressiveness 
for designing real-life, non-trivial intents.
                     </p>
                 </section>
diff --git a/intent-matching.html b/intent-matching.html
index 817f809..6d05444 100644
--- a/intent-matching.html
+++ b/intent-matching.html
@@ -182,7 +182,7 @@ id: intent_matching
                     }
                 ],
                 "intents": [
-                    "intent=alarm term~{id=='x:alarm'} 
term(nums)~{id=='nlpcraft:num' && ~nlpcraft:num:unittype=='datetime' && 
~nlpcraft:num:isequalcondition==true}[0,7]"
+                    "intent=alarm term~{tok_id()=='x:alarm'} 
term(nums)~{tok_id()=='nlpcraft:num' && ~nlpcraft:num:unittype=='datetime' && 
~nlpcraft:num:isequalcondition==true}[0,7]"
                 ]
             }
         </pre>

Reply via email to