MHonArc v2.5.2 -->
wsia message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [Elist Home]
Subject: WSIA 5/23/2002: [wsia][wsia-requirements][R201]
How about say that the minimal conditions should be defined although we
are not defining them? Would need to decide when they should be
defined. "Simple" is not testable.
A WSIA Web Service MUST be capable of being produced from or in lieu of
a pre-existing web application, under a minimum set of pre-defined?
default? conditions.
Decide if it must be defined from a default set, defined when developed,
etc.....
A WSIA Web Service SHOULD be capable of being published and consumed
under a
minimum set of pre-defined? default? conditions.
Same comment for team's input and resolve.
Thanks.
Monica
-----Original Message-----
From: Rich Thompson
Sent: Thu 5/23/2002 11:57 AM
To: wsia@lists.oasis-open.org
Cc:
Subject: Re: WSIA 5/21/2002: [wsia][wsia-requirements][R201]
I'm not sure we want to have to enumerate the minimum conditions
explicitly
... how about:
It MUST be simple both to author, either new or from an
existing
application, and publish a simple WSIA Web Service.
"Monica Martin"
<mmartin@certivo. To: Rich Thompson/Watson/IBM@IBMUS,
net> <wsia@lists.oasis-open.org>
cc:
05/21/2002 08:51 Subject: WSIA
5/21/2002: [wsia][wsia-requirements][R201]
PM
R201 (broken into two requirements)
Suggested wording (remember testability):
A WSIA Web Service MUST be capable of being produced from or in
lieu of
a pre-existing web application, under the following minimum
conditions:??state these if applicable.
A WSIA Web Service SHOULD be capable of being published and
consumed
under the following minimum conditions:???.state these if
applicable.
Arrows welcome.
Thanks. Monica
-----Original Message-----
From: Rich Thompson
Sent: Fri 5/17/2002 1:33 PM
To: wsia@lists.oasis-open.org
Cc:
Subject: [wsia][wsia-requirements][R130]
Here are the modified requiremetns documents ...
the 'a'
version
is prior
to accepting changes and rearranging the
requirements by
functional
categories. In addition to those changes, the 'b'
version has
consistent
capitalization of words like 'MUST' and Consumer. I
also noted
and
implemented the global change of 'property' to
'context data'.
(See attached file: WSIA reqs 2002-05-17a.doc)(See
attached
file: WSIA reqs
2002-05-17b.doc)
Requirements still needing attention include:
R201
R203
R130
Overlap between R601 & E905
Overlap between R702 & E904
Monica's recent email:
WSIA Web Services SHOULD provide the
capability for
those
Presentation
Fragments, returned by the Producer, can
be requested
and relayed
through the Consumer.
WSIA Web Service SHOULD provide the
capability for
Presentation
Fragments to reference end-user requests
for external
resources.
----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: < http://lists.oasis-open.org/ob/adm.pl>
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [Elist Home]
Powered by eList eXpress LLC