Changes between Version 1 and Version 2 of Public/AiTechnical

Timestamp:

Jul 20, 2026, 1:47:36 PM (33 hours ago)

Author:

Boris Horner

Comment:

—

Public/AiTechnical

@@ -136 +136 @@
 <p><b>i2store</b> allows definition of typed attribute fields. Such fields can be numeric, textual, date, and they can use hierarchical values from taxonomies. Attribute fields can be linked to domains and the nodes in that domain have these attribute fields then. Attribute fields can then be searched using the search API.</p>
 <p><b>i2store</b> provides typed relations that make a link between two nodes. They could have any kind of semantic meaning, like linking up children of a DITAmap, representing a "see also" relation or any other. Relations can have attributes available for filtering, too.</p>
-<h1 style="margin-left: 0;">API first</h1>
-<p>.</p>
    }}}
  }}}
@@ -143 +141 @@
 }}}
 
+{{{#!html
+<h1 style="margin-left: 0;">API first</h1>
+<p>The <b>i2ai / i2store</b> API is not wired on top of the web application, but <b>i2ai / i2store</b> IS the API and all that's behind it. The web application just accepts user interaction and displays results. Therefore, anything you can do in the web application can be called with a few lines of code from any application you want to integrate to:</p>
+<ul>
+<li><p>We explained a simple RAG example on this page. The user interface is just an input field and an output field for result and one for the references. Call the API endpoint with the id of the process and the same input string from the user and get the same results. You can integrate this into any web or desktop application or backend process you like, for example, to implement RAG in your Content Delivery Portal.</p></li>
+<li><p>Talking about Content Delivery Portals: <b>i2ai / i2store</b> API has all the building blocks for a CDP. It stores content, assigns user permissions, exposes four-axes search and ranking, manages renditions and relations and fetches content on demand. No logic needs to be implemented, just a web frontend matching your corporate design.</p></li></ul>
+<li><p>With one API service in your network, you can make sure that the same function, wherever you use it, is identical. For example, you might have a process verifying adherence to authoring guidelines in a DITA topic. This function would make sense both in an editor context while the author is writing and as a precondition when lifecycle state is about to be changed to approved. With <b>i2ai / i2store</b>, you can call the identical function in both places, with a few lines of code each.</p></li></ul>
+<li><p>The API does not depend on how many users are logged into your applications. You can have multiple web frontend instances, but they don't overload your AI infrastructure with numerous, simultaneous requests. <b>i2ai / i2store</b> API manages a job queue with detailed configuration options whether and how jobs of the same type can run concurrently.</p></li></ul>
+}}}
+
 
 [wiki:Public/Imprint Imprint]