RE: [wsia][wsia-requirements][R414]

["Timothy N. Jones" <tim@crossweave.com>]

I agree with Alan: I think the Consumer should be able to add constraints,
but it should't be able to remove/modify constraints.  I suggest:

  The Consumer MUST adhere to whatever property validation constraints the
Producer has specified. The Consumer MAY specify additional property
validation constraints.

Tim

> I'm a little uncomfortable with suggesting to the Consumer that it is
> possible for them to ignore Producer validation constraints.
Operationally,
> this cannot be expected to lead to good QOS.
> I completely agree that the Consumer MAY specify additional validation
> constraints.
> -----Original Message-----
> From: Rich Thompson [mailto:richt2@us.ibm.com]
> Sent: Monday, May 06, 2002 5:01 AM
> To: wsia@lists.oasis-open.org
> Subject: RE: [wsia][wsia-requirements][R414]
> I think the original intent was that a Consumer may add property
validation
> constraints to those specified by the Producer (likely a 'republish'
> requirement). Suggest:
>       R414 [Functionality]
>               The Consumer SHOULD adhere to whatever property validation
>       constraints the Producer has specified. The Consumer MAY specify
>       additional property validation constraints.
>  
>                       Eilon Reshef
>                       <eilon.reshef@webc        To:       "'Alan Kropp'"
> <akropp@epicentric.com>,                 
>                       ollage.com>                wsia@lists.oasis-open.org
>                                                 cc:
>                       05/04/2002 06:24          Subject:  RE:
> [wsia][wsia-requirements][R414]                     
>                       PM
>  
>  
> I agree (except that I would change must to should...).
>       -----Original Message-----
>       From: Alan Kropp [mailto:akropp@epicentric.com]
>       Sent: Friday, May 03, 2002 9:10 PM
>       To: 'wsia@lists.oasis-open.org'
>       Subject: [wsia][wsia-requirements][R414]
>       R414 [Functionality?]
>                       The Consumer should have a means to override
property
>       validation constraints and logic at each of its levels.
>       Well, the Consumer could certainly do this, but the Producer is
>       likely to
>       reject such overriden values as invalid!  I think the Consumer must
>       be bound
>       by whatever property validation schema the Producer enforces:
>       R414 [Functionality]
>                       The Consumer must adhere to whatever property
>       validation
>       constraints the Producer may specify for any of its properties.
>       ----------------------------------------------------------------
>       To subscribe or unsubscribe from this elist use the subscription
>       manager: <http://lists.oasis-open.org/ob/adm.pl>
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>