Dcos site updates

src/SCFirstOrderLogic.Documentation/Program.cs

@@ -1,6 +1,6 @@
 using Microsoft.AspNetCore.Components.Web;
 using Microsoft.AspNetCore.Components.WebAssembly.Hosting;
-using SCFirstOrderLogic.Documentation;
+using SCFirstOrderLogic.Documentation.Razor;
 
 var builder = WebAssemblyHostBuilder.CreateDefault(args);
 builder.RootComponents.Add<App>("#app");

src/SCFirstOrderLogic.Documentation/Pages/lab/InferenceDemo.razor → src/SCFirstOrderLogic.Documentation/Razor/Pages/lab/InferenceDemo.razor

@@ -26,8 +26,9 @@
                 </p>
                 <ul>
                     <li>
-                        The knowledge base implementations in this package are very basic for now, to the extent that it is very easy to create queries that they will struggle with.
-                        The goal of this package (for now, at least) is learning and experimentation more than anything else - so I maintain that there is value here as it stands - but improvements to the knowledge base implementations will be made (though not to any particular timeline).
+                        The knowledge base implementations offered here - which reside in the SCFirstOrderLogic.Inference.Basic package - are very basic, to the extent that it is very easy to create queries that they will struggle with.
+                        The goal of this package is learning and experimentation more than anything else.
+                        I am intending (assuming no one else beats me to it) to create some better KB implementations at some point.
                     </li>
                     <li>
                         Querying with this page is slower than it generally would be, due to limitations of the app framework used.

src/SCFirstOrderLogic.Documentation/_Imports.razor → src/SCFirstOrderLogic.Documentation/Razor/_Imports.razor

@@ -6,5 +6,5 @@
 @using Microsoft.AspNetCore.Components.Web.Virtualization
 @using Microsoft.AspNetCore.Components.WebAssembly.Http
 @using Microsoft.JSInterop
-@using SCFirstOrderLogic.Documentation
-@using SCFirstOrderLogic.Documentation.Shared
+@using SCFirstOrderLogic.Documentation.Razor
+@using SCFirstOrderLogic.Documentation.Razor.Shared

src/SCFirstOrderLogic.Documentation/SCFirstOrderLogic.Documentation.csproj

@@ -19,7 +19,7 @@
     <PackageReference Include="Microsoft.AspNetCore.Components.WebAssembly.DevServer" Version="8.0.7" PrivateAssets="all" />
     <PackageReference Include="Microsoft.Web.LibraryManager.Build" Version="2.1.175" />
     <PackageReference Include="SCFirstOrderLogic.ExampleDomains" Version="1.0.0" />
-    <PackageReference Include="SCFirstOrderLogic.Inference.Basic" Version="1.0.0" />
+    <PackageReference Include="SCFirstOrderLogic.Inference.Basic" Version="1.1.0" />
   </ItemGroup>
 
   <ItemGroup>

src/SCFirstOrderLogic.Documentation/wwwroot/md/roadmap.md

@@ -5,16 +5,14 @@ I don't intend to add any particularly powerful or specialised inference logic t
 
 Priorities at the time of writing:
 
-* *Nothing at the moment - working on other projects.*
+* A feature vector index implementation in the TermIndexing namespace of the core package.
+* A linear resolution strategy in the Inference.Basic package.
 
 Further ahead:
 
-* Next up is likely to be more indexing stuff - specifically, to facilitate finding subsuming/subsumed clauses.
-  Might go very old-school and build on discrimination/path trees for this, but will probably at least try to go slightly less old-school and have a crack at a feature vector index implementation.
-* Improvements to inference algorithms. As mentioned above and elsewhere, this package is more about the fundamentals than especially powerful inference logic - but we should probably cover at least some of the relatively fundamental problems and techniques - the inference demo is rather underwhelming at the moment.. For example, some or all of:
-  * Create a clause store or two that leverages subsumption.
+* Some improvements to the inference algorithms in Inference.Basic package.
+  As mentioned above and elsewhere, this package is more about the fundamentals than especially powerful inference logic, but we should probably cover at least some of the relatively fundamental problems and techniques - the inference demo is rather underwhelming at the moment.
+  For example, some or all of:
+  * Some clause store implementations that leverage subsumption
   * Handling of loops when chaining
-  * More flexibility when chaining. Obviously the current implementations are very constrained in their consideration of clauses.
-  * A linear resolution strategy
-
-
+  * More flexibility when chaining. The current implementations are very constrained in their consideration of clauses.