OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

wsrp-wsia message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: [wsrp-wsia] RE: [wsrp][wsia] Draft spec v0.7


I have been trying to proof the current specification. However, when I get
to Sections 1.2.1 to, I get confused. Am I interpreting the
following correctly:

"This specification supports Consumers and Producers of various levels of
sophistication interacting with one another. While not exhaustive, the
following cases and how they can interact with each other are explored as
examples of the broad range of possibilities."

The specification then presents four examples. 

Does this mean that there is a very large set of permutations and
combinations that are all compliant with this specification? Must all
consumers and producers "plug and play" together? In other words, are
SophisticatedProducers required to work correctly with SimpleConsumers and
SimpleProducers with SophisticatedConsumers?

Should we define only one discrete compliant subset? If we did there would
only be Simple (the subset) and Sophisticated, but nothing in between. The
defined subset idea has been popular in programming language specifications.


Thank you.

Joe Rudnicki

-----Original Message-----
From: Rich Thompson [mailto:richt2@us.ibm.com]
Sent: Monday, September 30, 2002 7:07 AM
To: wsrp@lists.oasis-open.org; wsia@lists.oasis-open.org
Subject: [wsrp][wsia] Draft spec v0.7

Just realized this morning that I posted this to the joint mailing lists
rather than the TC mailing lists. Sorry for the duplication this causes.



                      Thompson/Watson/I        To:
                      BM@IBMUS                 cc:

                                               Subject:  [wsrp-wsia] Draft
spec v0.7                             
                      09/27/2002 09:59




As the editors talked today about whether or not there would be value in
holding up sending out this version for another couple of days, we decided
to send it out as the pending work fell into 2 basic camps:
 - Small stuff that has no technical impact: Examples include adding
introductory blurbs in front of the data structure subsections in Chapter
 - Big stuff: Major example is definition of a set of fault messages. 1 or
2 days will not make a difference here.

Compared against this is the need to see how the decisions of the past 3
weeks work together to mold the spec toward completion.

As a result, here is v0.7. We think it reflects the discussion/decisions
from the F2F and Issue calls since. It also includes a simplified caching
proposal (from what has been discussed on the email list) so that it could
be viewed in context of the whole. This is an example where we will need to
discuss whether it is useful at this simpler level and the complexity/value
tradeoff of moving it to the next level. This version also incorporates the
simplified property proposal discussed at the F2F for entity state updates.
Also included is a change to use the <any/> payload extension mechanism we
decided to explore. Preliminary tests of the attached WSDL says that both
Axis and .Net tooling will process it to produce reasonable stubs.
Interoperability and treatment by other web service tooling also need to be

(See attached file: WSIA - WSRP Interface Specification v0.7.doc)(See
attached file: WRSP-wsdl_files v0.7.ZIP)
(See attached file: WSIA - WSRP Interface Specification v0.7.doc)(See
attached file: WRSP-wsdl_files v0.7.ZIP)

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Powered by eList eXpress LLC