X-Git-Url: http://matita.cs.unibo.it/gitweb/?a=blobdiff_plain;f=helm%2Fwww%2Flambdadelta%2Fweb%2Fhome%2Fosn.ldw.xml;h=45920eb7d30d2973164e70fedc6d8173ab2f47ea;hb=9a6cf8c3b53fe33515acd1aef8e7c7a10d71ae71;hp=5fa8a698199cd7d4de6f0ccd94d8fcd5531a40f2;hpb=282936907bd9b37d9de37f14e0e497db16f5d8b0;p=helm.git

diff --git a/helm/www/lambdadelta/web/home/osn.ldw.xml b/helm/www/lambdadelta/web/home/osn.ldw.xml
index 5fa8a6981..45920eb7d 100644
--- a/helm/www/lambdadelta/web/home/osn.ldw.xml
+++ b/helm/www/lambdadelta/web/home/osn.ldw.xml
@@ -28,16 +28,16 @@
       as well as the support for canonicalization.
       Apparently, these features fall outside the scope of OSN,
       which targets the data structures of <notice text="formal languages"/>. 
-   </style><newline/></item>
-   <item class="blue-mark"><style class="alpha">
+   </style></item></list>
+   <list><item class="blue-mark"><style class="alpha">
       Optionally <link to="https://en.wikipedia.org/wiki/Namespace">qualified</link> symbolic expressions 
       allow OSN texts to mix data from different domains preserving their own semantics
       because name conflicts can be avoided.
       As a consequence OSN documents are <notice text="easy to extend"/> in that
       domain-specific OSN applications can work as expected even if
       data from different domains is added to the text they process.
-   </style><newline/></item>
-   <item class="green-mark"><style class="alpha">
+   </style></item></list>
+   <list><item class="green-mark"><style class="alpha">
       The <link to="https://en.wikipedia.org/wiki/ASCII">US-ASCII</link> character set,
       extended to <link to="http://www.utf-8.com/">UTF-8</link> in
       free-form text strings for the convenience of human readers,
@@ -68,7 +68,8 @@
             <str2 of="a"/> <etc/> <str2 of="z"/>
          <stop/>
       </ebnf>
-   </item><newline/><item>
+   </item></list>
+   <list><item>
       This token contains free-form text with commonly accepted escape sequences:
       <newline/><ebnf>
          <prod of="string"/> <def/>
@@ -116,7 +117,8 @@
             <str2 of="a"/> <etc/> <str2 of="f"/>
          <stop/>
       </ebnf>
-   </item><newline/><item>
+   </item></list>
+   <list><item>
       This token is a widely used alternative of the former token:
       <newline/><ebnf>
          <prod of="string-alt"/> <def/>
@@ -129,26 +131,30 @@
             <str1 of="'"/>
          <stop/>
       </ebnf>
-   </item><newline/><item>
+   </item></list>
+   <list><item>
       This token separates the qualifiers of a symbolic expression:
       <newline/><ebnf>
          <prod of="sep"/> <def/> <str2 of=":"/> <stop/>
       </ebnf>
-   </item><newline/><item>
+   </item></list>
+   <list><item>
       This token starts a compound symbolic expression:
       <newline/><ebnf>
          <prod of="open"/> <def/>
             <str2 of="("/> <or/> <str2 of="&lt;"/> <or/> <str2 of="["/> <or/> <str2 of="{"/>
          <stop/>
       </ebnf>
-   </item><newline/><item>
+   </item></list>
+   <list><item>
       This token ends a compound symbolic expression:
       <newline/><ebnf>
          <prod of="close"/> <def/>
             <str2 of=")"/> <or/> <str2 of="&gt;"/> <or/> <str2 of="]"/> <or/> <str2 of="}"/>
          <stop/>
       </ebnf>
-   </item><newline/><item>
+   </item></list>
+   <list><item>
       This token is ignored and separates the other tokens:
       <newline/><ebnf>
          <prod of="gap"/> <def/>
@@ -169,7 +175,8 @@
             <star/> <prod of="q-expr"/>
          <stop/>
       </ebnf>
-   </item><newline/><item>
+   </item></list>
+   <list><item>
       A qualified symbolic expression:
       <newline/><ebnf>
          <prod of="q-expr"/> <def/>
@@ -179,7 +186,8 @@
             <prod of="expr"/>
          <stop/>
       </ebnf>
-   </item><newline/><item>
+   </item></list>
+   <list><item>
       An unqualified symbolic expression:
       <newline/><ebnf>
          <prod of="expr"/> <def/>