Re: TBTF: Proposed resolution issue 179

I agree with Chris, it's "enable".  In general, the same MEP will be 
"enabled" by many different bindings, thus I am reluctant to signal that 
binding specs should "define" MEPs.  So, "enable" but not "define", I 
think.  Thanks.

------------------------------------------------------------------
Noah Mendelsohn                              Voice: 1-617-693-4036
IBM Corporation                                Fax: 1-617-693-8676
One Rogers Street
Cambridge, MA 02142
------------------------------------------------------------------







Christopher Ferris <chris.ferris@sun.com>
Sent by: xml-dist-app-request@w3.org
02/12/2002 05:57 PM

 
        To:     Henrik Frystyk Nielsen <henrikn@microsoft.com>
        cc:     Noah Mendelsohn/Cambridge/IBM@Lotus, marc.hadley@sun.com, XML Protocol 
Discussion <xml-dist-app@w3.org>
        Subject:        Re: TBTF: Proposed resolution issue 179


I would think "enable".

and +1 btw:)

Henrik Frystyk Nielsen wrote:

> Looks good - only comment is that "support" may be understood in many
> different--does it mean "define" or "enable", or both? We saw this many
> times in the requirements document [1]. In this case, I think we mean
> both so what about saying "define or enable" instead or something to
> that effect?
>
>
>>""A binding specification MUST support one or more Message Exchange
>>Patterns.  A binding specification MAY state that it supports
>>additional
>>features,
>>in which case the binding specification MUST provide for
>>maintaining state, performing processing, and transmitting
>>information in a manner consistent with the specification for
>>those features."
>>
>
> Henrik
>
> [1] http://www.w3.org/TR/2001/WD-xmlp-reqs-20010319/
>
>
>

Received on Wednesday, 13 February 2002 12:11:06 UTC