Re: Fallback mechanism for the datatype

[James Clark <jjc@jclark.com>]

The "shall at user option report warning message" bit doesn't work for me. 
The processor may not be running interactively.  A RELAX NG processor might 
be built into the firmware of a fridge.  An implementation may have not any 
way to report an error or to support user options.

I think the critical point that the spec needs to make is that a RELAX NG 
processor does not become non-conformant merely because it does not support 
some datatype library.  Also if an implementation claims conformance, it 
should as part of that claim state what datatype libraries it supports.

--On Tuesday, July 31, 2001 8:40 AM +0900 Murata Makoto 
<mura034@attglobal.net> wrote:

> Kohsuke KAWAGUCHI wrote:
>
>> > I think this is a good thing for a RELAX NG processor to do, but I'm
>> > not sure the spec needs to say anything.  I don't think I want to
>> > mandate any particular recovery behavior.
>>
>> I guess you are right.
>
> But we still have to define what is a conformant implementation.  We
> cannot  require that a conformant implementation must know all datatype
> libraries.
>
> How about this?
>
> 	When it encounters an unknown datatype library,  a conformant RELAX NG
> 	processor shall, at user option, report warning message.  It may continue
> 	or abort normal processing.
>
> Cheers,
>
> Makoto
>
> ------------------------------------------------------------------
> To unsubscribe from this elist send a message with the single word
> "unsubscribe" in the body to: relax-ng-request@lists.oasis-open.org
>
>