RE: PROPOSAL: CAP Error codes definition and handling

[andrec@xxxxxx]

By reading the details of the tokens,
you will see that in the following,

    rstatus    = "REQUEST-STATUS" rstatparam ":"
                 statcode ";" statdesc [";" extdata]

statdesc MUST be the description given in the RFC and
not some arbitrary text.

Furthuremore, statdesc is of a type that can be localized,
with a language tag, bla, bla bla.

It is much more restrictive than the one proposed.

Andre Courtemanche
CS&T

-----Original Message-----
From: Bruce_Kahn@iris.com [mailto:Bruce_Kahn@iris.com]
Sent: Monday, May 17, 1999 2:46 PM
To: andrec@cst.ca
Cc: ietf-calendar@imc.org
Subject: Re: PROPOSAL: CAP Error codes definition and handling





Andre wrote:
>That to each transaction from the CUA to the server, the
>satus be reported as follows:
>
><statuscode>;<text>
[Snip]
>I also propose that whatever this group chooses to do,
>that we make that error code format identical between
>iCal's and CAP.

Why not just follow the same format that is defined in RFC 2445 for Request
Status (section 4.8.8.2)?  That defines the format of:

   The value consists of a short return status component, a longer
  return status description component, and optionally a status-specific
  data component. The components of the value are separated by the
  SEMICOLON character (US-ASCII decimal 59).
[Snip]
   Format Definition: The property is defined by the following notation:

    rstatus    = "REQUEST-STATUS" rstatparam ":"
                 statcode ";" statdesc [";" extdata]

    rstatparam = *(

               ; the following is optional,
               ; but MUST NOT occur more than once

                (";" languageparm) /

               ; the following is optional,
               ; and MAY occur more than once

               (";" xparam)

               )

    statcode   = 1*DIGIT *("." 1*DIGIT)
    ;Hierarchical, numeric return status code

    statdesc   = text
    ;Textual status description

    extdata    = text
    ;Textual exception data. For example, the offending property
    ;name and value or complete property line.

(For those out there who are not sure; Im not advocating the ENTIRE reuse
of this property and it params, etc, just the format of the 'value' part;
statcode ';"...)

Good reasons to do this include:

1: I can reuse my existing parser code and
2: Its already defined by iCal so why not reuse it in CAP?

Bruce
===========================================================================
Bruce Kahn                                INet: Bruce_Kahn@iris.com
Iris Associates                          Phone: 978.392.5335
Westford, MA, USA 01886                    FAX: and nothing but the FAX...
Standard disclaimers apply, even where prohibited by law...