Saturday, May 04, 2002
Eric Knorr's 30 April article in ZDNet Tech Update titled Web Services Meet Process Management made me think about the many different directions we are going. Yes, we need to integrate process design and management into the architecture of systems we're designing and building. However, is yet another process notation or methodology needed? Given the activity surrounding Web Services Flow Language (WSFL) my question is moot. Personally, the best approach I've seen so far is that proposed by Nick V. Flor in Web Business Engineering. Bemoaning the fact that this well thought out approach is being ignored accomplishes nothing. I can console myself that at least the importance of process as a foundation is recognized and standards are being developed. I've collected a number of articles and documents about Web Services Flow Language and encourage anyone who is involved in the design and development of web-based systems to become familiar with them:
- A good starting point is Web Services Flow Language (WSFL) by Robin Cover
- IBM's five part series on web services: Part 1, Part 2, Part 3, Part 4 and Part 5 cover WSFL and related aspects and is essential reading. In fact I consider IBM to be leading the way in web services, posturing and hype from other factions aside, and invite your attention to the wealth of articles and journal articles they have published on the subject.
- ebPML.org, which is an organization dedicated to architectures and technologies of business process management systems. This site has an excellent description of WSFL, among other related resources.
- The archive of documents provided by Web Services Architect, and especially the article titled Business Process Standards for Web Services: The candidates.
Subscribe to Posts [Atom]
