Dan, I can see your perspective, but consider the consequences if we produce
a specification that prevents us from integrating with legacy applications.
Although we are in the domain of web services, the world will not become
fully WSIA aware for several years, and many of the implementations will be
producers exposing existing applications.
Without the ability to integrate the adoption rate will be low, which will
lead us down the path to obscurity.
I support Eilon's reworded statement, though I'm not sure that
'infrastructure' adds anything to the requirement.
Regards
Greg
-----Original Message-----
From: Dan Gisolfi [mailto:]
Sent: Monday, May 06, 2002 4:32 AM
To:
Subject: Re: [wsia][wsia-requirements][E922]
As we are dealing with the domain of Web Services, an assumption should be
made that the spec should pertain to any Web Service. Therefore, I see no
need for the spec to specifically call out legacy applications and
infrastructure. The spec will pertain to any software component that can be
described using a Web Services facade.
Therefore I do not see a need for this requirement. I motion for deletion.
Dan Gisolfi
To:
cc:
Subject: [wsia][wsia-requirements][E922]
E922
Producers SHOULD provide the capability to support legacy applications and
infrastructure. Debate: GG, ER, DG, SB, TJ.
This seems to be a requirement from a tool and not necessarily from the
specification.
Try:
The specification should not preclude Producers from providing the
capability to support legacy applications and infrastructure.
----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>
