W3C home > Mailing lists > Public > www-validator@w3.org > October 2007

Re: proposal to have sequential / grouped messages in soap output

From: Karim A. <directeur@gmail.com>
Date: Wed, 17 Oct 2007 16:19:02 +0100
Message-ID: <9ddf33ea0710170819l65dbec78x7cc5cd8648af84e@mail.gmail.com>
To: Chris. <chris.forummail@swankinnovations.com>, "olivier Thereaux" <ot@w3.org>
Cc: www-validator@w3.org

On 10/17/07, Chris. <chris.forummail@swankinnovations.com> wrote:

> I don't think that this is correct as the 'grouped' mode for the web api
> groups all errors or warnings of the same 'type' (message id, really) but a
> group of errors can be followed by a group of warnings or vice versa.

Thank you Chris ! I was lost and pulling my hair ; how come
I don't see that it's "grouped"...

In fact, I too don't think it's a grouped mode of output, or at least
not the same as the html one.

A grouped soap response would be something like:

<m:error>
    <m:message>
        no document type declaration; implying &quot;&lt;!DOCTYPE HTML
        SYSTEM&gt;&quot;
   </m:message>
   <m:messageid>344</m:messageid>
   <m:explanation> ...</m:explanation>
   <m:occurences>
        <m:position>
          <m:line>...</m:line>
          <m:col>...</m:col>
       </m:position>

        <m:position>
          <m:line>...</m:line>
          <m:col>...</m:col>
       </m:position>
        ...
        <m:position>
          <m:line>...</m:line>
          <m:col>...</m:col>
       </m:position>
   </m:occurences>
</m:error>

Where <m:error> is a direct child of <m:errorlist> of
the surrent implementation.

(Do the same thing for warnings)

This way, we can group similar errors/warnings and be able
to retrieve ALL positions where they occured.

> In the default output for the soap api, all errors (ordered sequentially by
> occurrence) and all warnings (ordered sequentially by occurrence) are
> segregated into separate containers.  This seems like a third (more useless)
> mode that is its own creation -- closest to sequential mode of the web api
> if anything.

Why useless? :)

I do use it myself, and have no problem with it... or maybe just the
redundancy in messages and explanations in the output.
But my app is living well with it ;-)

If you change that, all my work (a hard work) will be vain :(
So, please, keep it that way, and add a second template
and a second way of generating output using this template...

Thank you! :)

Karim
--
http://akoncept.com
Innovate Humanum Est
Received on Wednesday, 17 October 2007 15:19:13 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 25 April 2012 12:14:26 GMT