simon/wwui
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Actually added the documentation to the repository. D'oh!

Browse source
This commit is contained in:
Simon Brooke 2020-05-01 12:10:12 +01:00
parent 12a2eb71c8
commit 38a4610f0e
No known key found for this signature in database
GPG key ID: A7A4F18D1D4DF987
9 changed files with 757 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

34
docs/codox/parsing.html Normal file
View file

@ -0,0 +1,34 @@
<!DOCTYPE html PUBLIC ""
"">
<html><head><meta charset="UTF-8" /><title>Parsing</title><link rel="stylesheet" type="text/css" href="css/default.css" /><link rel="stylesheet" type="text/css" href="css/highlight.css" /><script type="text/javascript" src="js/highlight.min.js"></script><script type="text/javascript" src="js/jquery.min.js"></script><script type="text/javascript" src="js/page_effects.js"></script><script>hljs.initHighlightingOnLoad();</script></head><body><div id="header"><h2>Generated by <a href="https://github.com/weavejester/codox">Codox</a></h2><h1><a href="index.html"><span class="project-title"><span class="project-name">Wwui</span> <span class="project-version">0.1.0-SNAPSHOT</span></span></a></h1></div><div class="sidebar primary"><h3 class="no-link"><span class="inner">Project</span></h3><ul class="index-link"><li class="depth-1 "><a href="index.html"><div class="inner">Index</div></a></li></ul><h3 class="no-link"><span class="inner">Topics</span></h3><ul><li class="depth-1 "><a href="intro.html"><div class="inner"><span>Introduction to wwui</span></div></a></li><li class="depth-1 current"><a href="parsing.html"><div class="inner"><span>Parsing</span></div></a></li></ul><h3 class="no-link"><span class="inner">Namespaces</span></h3><ul><li class="depth-1"><div class="no-link"><div class="inner"><span class="tree"><span class="top"></span><span class="bottom"></span></span><span>wwui</span></div></div></li><li class="depth-2 branch"><a href="wwui.core.html"><div class="inner"><span class="tree"><span class="top"></span><span class="bottom"></span></span><span>core</span></div></a></li><li class="depth-2"><a href="wwui.parser.html"><div class="inner"><span class="tree"><span class="top"></span><span class="bottom"></span></span><span>parser</span></div></a></li></ul></div><div class="document" id="content"><div class="doc"><div class="markdown"><h1><a href="#parsing" name="parsing"></a>Parsing</h1>
<p>Generally, The <code>wwui</code> parser needs to be able to recognise, and to extract in a form usable by <code>wildwood</code>, two general forms of utterances:</p>
<ol>
<li>Propositions, and</li>
<li>Questions;</li>
</ol>
<p>where questions can be further subdivided:</p>
<ol>
<li>is (proposition) true at present?</li>
<li>was (proposition) true in the past?</li>
<li>will (proposition) be true in the future?</li>
<li>is (proposition) true at this (time or time range specification)?</li>
<li>what is the value of (property) of (entity)?</li>
<li>how do you know that (proposition) has (truth-value)?</li>
<li>how do you know that (property) of (entity) has (value)?</li>
</ol>
<p>So the key things we need to know about and identify in natural language input are</p>
<ol>
<li>Propositions;</li>
<li>Entities;</li>
<li>Properties;</li>
<li>Values</li>
</ol>
<p>At the current stage of development of the current iteration, is is anticipated that the key construct that <code>wildwood</code> will reason with are <a href="https://simon-brooke.github.io/wildwood/codox/Bialowieza.html#propositions">located two position propositions</a>; that is to say propositions having</p>
<ol>
<li>A <strong>verb</strong>;</li>
<li>A <strong>subject</strong>, being an entity;</li>
<li>An <strong>object</strong>, being an entity;</li>
<li>Optionally, a <strong>spatial location</strong>;</li>
<li>Optionally, a <strong>temporal location</strong>.</li>
</ol>
<p>The principle behind <code>wildwood</code> - at least in its current iteration - is that for the inference game to work, there has to be, for every entity, a ‘true name’ or unique identifier consensually agreed by each agent for each entity. The parser, obviously, can only parse noun phrases, so to be able to resolve noun phrases to true names there must be an API for the parser to pass a noun phrase, possibly with some context, to a knowledge accessor and receive a true name back.</p></div></div></div></body></html>