Title: RE: [asap] Three primary points of discussion
I think we can flesh out the goals a bit to make action items:
* Extract goals, update and get agreement with working group members. This needs to be settled before we can move forward on the specification.
* We need a open source JSP based reference implementation for testing with. The service should be a trivial one that simply delays a set number of seconds (e.g. 10 seconds) and then sends notification that it completed. It does not need to be programmable. In order to accomplish this, someone needs to write up a requirements specification that describes this scenario.
* Need to get the XSD Validated
* Need a plan for a public demonstrations of implementations. Get 4-5 commitments to implement a particular scenario with real process technology. Let the analysts know ahead of time. Let public and potential implementers know that analysts will be watching, and this might be a good opportunity to jion in the show. Demonstrate interoperability across the Internet. I realize it is early, but it will take 6 to 9 months to set up such a demo, so we need to get started.
-Keith Swenson
-----Original Message-----
From: Jeffrey Ricker [mailto:]
Sent: Sunday, November 02, 2003 4:51 PM
To: ASAP
Subject: [asap] Three primary points of discussion
There are three primary points of discussion.
1. Getting on with business.
This committee has stalled over the past month, and the blame rest
entirely with me. As such, I intend to fix it. This forum needs to
churn. We have a lot details to resolve over the next eight weeks. This
mailing list is where it will happen.
2. Letting the world know what we are doing.
The cat is out of the bag now. The InfoWorld article is out and the
official OASIS press release will follow sometime this week. We need to
provide the world some content. I have created a draft FAQ. Let me know
if you have any objections to it or anything to add. It should go out
right away. Let me know what else we can or should provide.
3. Resolve fundamentals
We have resolved to publish a set of requirements that are minimum set
necessary to make asynch work. The driving concept here is the needs for
(a) small, embedded wireless devices and (b) large telecom switching
infrastructure. This is a big switch from the origins of ASAP, which was
workflow. I think it is healthy to get such divergent perspective of
requirements.
I ask the members to propose their thoughts on minimum requirements to
the list.
To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/asap/members/leave_workgroup.php.
