Apparently, these features fall outside the scope of OSN,
which targets the data structures of <span class="emph ">formal languages</span>.
</span>
+ <br />
</li>
- <br />
<li class="blue-mark">
<span class="alpha">
Optionally <a href="https://en.wikipedia.org/wiki/Namespace">qualified</a> symbolic expressions
domain-specific OSN applications can work as expected even if
data from different domains is added to the text they process.
</span>
+ <br />
</li>
- <br />
<li class="green-mark">
<span class="alpha">
The <a href="https://en.wikipedia.org/wiki/ASCII">US-ASCII</a> character set,
<div xmlns:ld="http://lambdadelta.info/" class="spacer">
<br />
</div>
- <div xmlns:ld="http://lambdadelta.info/" class="spacer">Last update: Fri, 22 Jul 2016 19:37:02 +0200</div>
+ <div xmlns:ld="http://lambdadelta.info/" class="spacer">Last update: Fri, 22 Jul 2016 19:42:53 +0200</div>
</body>
</html>
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></item><newline/>
+ </style><newline/></item>
<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
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></item><newline/>
+ </style><newline/></item>
<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