<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>I attach one more cool example.</p>
<p>An XML book with an UML extension:</p>
<p>This is the source:</p>
<pre><book>
<requirements>
<feature>EruditeXMLBookHTML</feature>
<feature>EruditeXMLBookSmalltalk</feature>
<feature>EruditeXMLBookUML</feature>
</requirements>
<chapter>
<title>Intro</title>
<p>Hello world</p>
<p>
<ul>
<li>Hello</li>
<li>World</li>
</ul>
</p>
<p>
<smalltalk>
Object new
</smalltalk>
</p>
<p>
<doit>
Smalltalk inspect
</doit>
</p>
<p>
<uml>
Alice -> Bob: Authentication Request
Bob --> Alice: Authentication Response
Alice -> Bob: Another authentication Request
Alice <-- Bob: another authentication Response
</uml>
</p>
</chapter>
</book>
</pre>
<p>I attach PDF with formatted document. <br>
</p>
<div class="moz-cite-prefix">El 13/3/25 a las 19:45, Mariano Montone
escribió:<br>
</div>
<blockquote type="cite"
cite="mid:4d35448b-531b-4f5f-815f-55e3b70a5b49@gmail.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<p>Hi Hannes, folks,<br>
</p>
<div class="moz-cite-prefix">El 12/3/25 a las 12:00, H. Hirzel
escribió:<br>
</div>
<blockquote type="cite"
cite="mid:4fdbd44c-9213-483a-881e-b4dda5c47b5a@gmail.com">On
11/03/2025 3:28 pm, Mariano Montone via Cuis-dev wrote: <br>
<br>
<blockquote type="cite" style="color: #007cff;">Btw, last time I
looked at DocBook, I didn't find it extensible the way I would
have liked. <br>
<br>
In my opinion, we should have an XML standard that is easily
extensible, and that completely separates semantic elements
from its rendering. <br>
<br>
That would make it possible to manipulate documents and
extract information from them in a powerful way, without
losing information. And also render the documents for
different mediums in a correct way. <br>
<br>
I don't understand why there's not something like that. I
don't think DocBook is that, but it should have been. <br>
</blockquote>
Could you please elaborate on this? For my purposes it seems to
be good enough. Or do you specifically mean the handling of the
embedded code expressions? <br>
<blockquote type="cite" style="color: #007cff;"> <br>
That's what XMLEruditeBook is about. </blockquote>
</blockquote>
<p>I've added an example of XML books.</p>
<p>To try, evaluate:</p>
<pre>Feature require: 'EruditeXMLBook'.
(EruditeXMLBook new
file: (CodePackage installedPackages at: 'EruditeXMLBook') fullFileName asFileEntry parent // 'Examples/xmlbook2.xml')
open.</pre>
<p>This is the demo book:</p>
<pre><book>
<requirements>
<feature>EruditeXMLBookHTML</feature>
<feature>EruditeXMLBookSmalltalk</feature>
</requirements>
<chapter>
<title>Intro</title>
<p>Hello world</p>
<p>
<ul>
<li>Hello</li>
<li>World</li>
</ul>
</p>
<p>
<smalltalk>
Object new
</smalltalk>
</p>
<p>
<doit>
Smalltalk inspect
</doit>
</p>
</chapter>
</book>
</pre>
<p>Notice how the book specifies the features it needs for parsing
and rendering, and they are loaded when the book is opened.<br>
</p>
<p>XML makes the syntax automatically extensible, and references
to the requirements loads the parsers and renderers needed for a
book.</p>
<p>There's no book that can't be authored with a system like this!
:)</p>
<p>This is Erudite endgame :P</p>
<p> Mariano</p>
</blockquote>
</body>
</html>