W3C home > Mailing lists > Public > public-xml-processing-model-comments@w3.org > February 2008

RE: xproc static and dynamic error output as xml

From: Vasil Rangelov <boen.robot@gmail.com>
Date: Tue, 12 Feb 2008 14:59:59 +0200
To: <public-xml-processing-model-comments@w3.org>
Message-ID: <47b19852.0b38560a.1b27.0788@mx.google.com>

Isn't that already the case?

Look at 4.6.1.2: c:error - http://www.w3.org/XML/XProc/docs/langspec.html#cv.error

I suppose it should be said that implementations MAY output such error documents, as well as ones for static errors, as long as it's outputted in a different, implementation defined way i.e. implementations mustn't output errors as if everything was OK. E.g. a command line XProc processor may return error documents on stderr, but not on stdout.

-----Original Message-----
From: public-xml-processing-model-comments-request@w3.org [mailto:public-xml-processing-model-comments-request@w3.org] On Behalf Of James Fuller
Sent: Tuesday, February 12, 2008 11:58 AM
To: public-xml-processing-model-comments@w3.org
Subject: xproc static and dynamic error output as xml


I think we can all see value in specifying static and dynamic error
output as well formed xml

for example;

<err:result>
    <err:XS0049>It is a static error if the psvi-required attribute is
"true" and the processor does not support passing PSVI annotations
between steps.</err:XS0049>
</err:result>

is this something to leave as an implementation detail or should we
amend 6 Errors section a little bit ?

cheers, Jim Fuller
Received on Tuesday, 12 February 2008 13:00:09 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 12 February 2008 13:00:10 GMT