Bindings, Platforms, and Innovation
This presentation focuses on the Internet and separating myth from fact, history from the future, and the mundane from the imaginative. Bob Frankston presents a vision of what could and should be.
Tracking change and innovation in the enterprise software development community
Posted by Mark Little on Jul 02, 2008 03:16 AM
OASIS just announced the closure of two technical committees: UDDI and OASIS Framework for Web Services Implementation (FWSI). In terms of UDDI:The UDDI Specification TC standardized two versions (v2.0 and v3.0)This isn't the end of UDDI development, as the OASIS announcement makes clear: it's still alive and well at the main UDDI site. OASIS announces the closer of technical committees all the time, but this may be different. In recent years the need for registries has grown but the adoption of UDDI has not. Although in the open source arena some ESBs use UDDI, others don't and have voiced doubts over its usefulness. Maybe moving out of OASIS (for now, or permanently is not clear) is not a problem for UDDI, since it has been dogged by these kinds of concerns since its birth. But the number of new users of UDDI does not seem to be keeping pace with the number of new users of registries.
of the UDDI specification set, as well as a Schema Centric XML
Canonicalization Specification V1.0. See:
http://www.oasis-open.org/committees/uddi-spec/doc/tcspecs.htm#uddiv3
UDDI versions 2.0 and 3.0 were approved as OASIS Standards. See:
http://www.oasis-open.org/news/oasis_news_02_03_05.php
and the TC's presentation "UDDI v3: The Registry Standard for SOA", at:
http://www.oasis-open.org/presentations/uddi_v3_webcast_20050222.pdf
The UDDI specification set and associated data models and schemas
provide the basic methods for publication and discovery of Web
services, both within and between enterprises. These standards are
in wide use today, and serve as the cornerstone for standards-based
Web service registries and directories.
The FWSI TC produced two specifications, the FWSI FunctionalDid FWSI have an impact on the industry? Certainly the technical committee produced a few documents and had a few meetings, but it was never heavily cross-referenced by vendors or other standards.
Elements Specification v2.0, approved as a Committee Specification,
and the FWSI Web Service Implementation Methodology, approved as a
Public Review Draft.
The FWSI project sought to facilitate implementation of robust Web
services by defining a practical and extensible methodology
consisting of implementation processes, and common functional
elements, for high quality Web services systems.
Give-away eBook – Confessions of an IT Manager
Usage Landscape: Enterprise Open Source Data Integration
Agile Development: A Manager's Roadmap for Success
Comprehensive Threat Protection for REST, SOA, and Web 2.0 Applications
Would you enroll in an India Forex Group i.e http://www.indiaforex.com Groups?
That's not built around SOAP/web services. See here for more info...
One of the reason I see with UDDI registry approach is its complexity. Now the trend is different people are building registry/repository on HTTP and APP , IMO which will be the future. Having said that there are two very good open source registry/repository products out there. Both of them did their releases in last few weeks.
http://blogs.deepal.org
I agree with Dan we need a new API based on AtomPub. If you want to read about how to use a new kind of OSS Registry to do SOA Governance, I've written about that in my blog: http://pzf.fremantle.org/2008/06/soa-governance-and-open-source.html
And with a proper link: http://pzf.fremantle.org/2008/06/soa-governance-and-open-source.html
This presentation focuses on the Internet and separating myth from fact, history from the future, and the mundane from the imaginative. Bob Frankston presents a vision of what could and should be.
This article explores the use of JBoss and jBPM to implement design solutions that effectively address the issue of orchestrating long running activities.
This presentation covers the use of graph databases as an optimal solution for data that is difficult to fit in static tables, rapidly evolving data or data that has a lot of optional attributes.
This session introduces Real Options and shows how it can help in running your project. Real Options is a decision-making process that can be used to manage risk.
This article discusses the use of bindings on services and references (including the instance of non-configured bindings) as the means to implement SCA communications in a Web and SOA environment.
After a short introduction to DSLs, Scott Davis plays with the keyboard showing how to approach the creation of a DSL by typing working snippets of Groovy code that get executed.
IBM Rational and InfoQ present, Scaling Agile with C/ALM, an eBook showing organizations how to become “finely tuned software delivery machines” by enabling team integration and scaling.
Amanda Laucher presents a real life enterprise application written in F#. She shows actual code snippets, explaining design decisions and suggesting how to use some of the F# constructs.
4 comments
Watch Thread Reply