RE: Two level result codes

["Jeff Bohren" <jbohren@opennetwork.com>]

I am a little concerned about adding another extensibility mechanism
when we already have one in place. The operational attributes can
already be defined in the SPML schema for which the provider is defined.

Perhaps we could define an error code called "Custom". If the error code
is set to custom then it is assumed that all error information is
included in the operational attributes, in one or more attributed
defined in the SPML schema for that service. This mechanism allows
extended error codes to be defined that are tied to a provider.

Jeff Bohren
Product Architect
OpenNetwork Technologies, Inc
 

-----Original Message-----
From: Cohen, Doron [mailto:Doron_Cohen@bmc.com] 
Sent: Tuesday, March 25, 2003 10:30 AM
To: provision@lists.oasis-open.org
Subject: RE: Two level result codes 

We can have something like ExtendedErrorCode this in SpmlResponse :

<xsd:complexType name="ExtendedErrorCode">
	<xsd:sequence>
            	<xsd:element name="provider"
type="spml:ProviderIdentifier"/>
	            <xsd:element name="errorCode" type="xsd:string" />
	</xsd:sequence>
</xsd:complexType>


Doron Cohen
BMC Software

-----Original Message-----
From: Cohen, Doron [mailto:Doron_Cohen@bmc.com] 
Sent: Tuesday, March 25, 2003 4:09 PM
To: provision@lists.oasis-open.org
Subject: Two level result codes 


Sometime ago, we agreed to have two level result code system referred to
as
ResultCode and ErrorCode. On the last call, dealing with the
internationalization problem, I raised that the extensible reason code
may
provide implementations better means of identifying error situations
that
relate to a specific target and I wanted to create a sample of the
proposal.

To deal with it, I would like to propose to have ErrorCode enhanced to
include a provider ID so that detailed error codes can be included in
the
responses for SPML requests. 

Doron Cohen
BMC Software