Re: 12. Are C1 controls Unicode non-characters disallowed?

What should happen then if the MicroXML is either

1) created from data in a database
2) actually stored in a database as XML and then
extracted after possible changes have been made to the XML

- if the data coming from the database now has an invalid
character which was valid as per the XML spec

???

I don't like the implications that seem to lead to a
proprietary database not easily being used with MicroXML
if the DB supports XML - unless the database manufacturers
add support (not sure how) for MicroXML too. I get the
impression either the app developer using MicroXML
and/or the MicroXML parser developer have to find some
way to handle possible newly illegal characters whenever
data or XML is extracted from a database.
----
Stephen D Green



On 11 September 2012 02:44, Uche Ogbuji <uche@ogbuji.net> wrote:

> On Mon, Sep 10, 2012 at 7:39 PM, Michael Sokolov <sokolov@falutin.net>wrote:
>
>>  Yes - some kind of recovery process would be a boon; +1 for allowing
>> parsers to replace these disallowed codepoints with the special Unicode
>> character reserved to mean "unknown or unrepresentable character": FFFD.
>>
>
> Yes. MicroXML's policy on error handling states that the parser must
> report that the document is not a MicroXML document, but having done so, it
> is free to recover as it pleases.
>
> David's point and yours here is a good one, and it's the lesson I think
> most have learned the hard way from XML's experiment with draconian error
> handling.  I think most would agree that experiment failed (just as
> Postel's Law predicted it would ;) )
>
>
>
> --
> Uche Ogbuji                       http://uche.ogbuji.net
> Founding Partner, Zepheira        http://zepheira.com
> http://wearekin.org
> http://www.thenervousbreakdown.com/author/uogbuji/
> http://copia.ogbuji.net
> http://www.linkedin.com/in/ucheogbuji
> http://twitter.com/uogbuji
>
>