Tracking change and innovation in the enterprise software development community
Free Book Offer
SOA Demystified
$40 Value
Scaling Scrum
in the enterprise?
ScrumWorks Pro
can help.
Start a trial today
QCon London 2010!
March 10-12, 100
Speakers, 80 sessions,
"THE" team leads and,
architects conference.
Posted by Mark Little on Jul 02, 2008
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.
Understand and Align BPM, SOA, and Lean Six Sigma: 43 page IBM Redguide
Restful BPM, Pragmatic SOA, Mashups, Avoiding Failure: SOA track @ QCon London in March
Visit SOA Appliance Comparison Site
*Video Usage Model Tutorials
*Comparison to IBM DataPower X150
*Performance Benchmarks/Webinars
*Replace DataPower Program
FREE 1:1 Swap & Migration Services
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.
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:
pzf.fremantle.org/2008/06/soa-governance-and-op...
And with a proper link: pzf.fremantle.org/2008/06/soa-governance-and-op...
Brian Marick takes us through a quick tour of the most important values and challenges to adopting Agile successfully (they aren't the typical challenges and values we hear in the community).
The line between development and architecture is tricky. Does it exist at all? Is an ivory tower actually needed? There's a balance in the middle, but how do you move from developer to architect?
The word 'authority' sometimes produces an allergic response in hard-line agilists. Freedom and authority – both are bad if misused and both are good if used in right spirit for a noble cause.
"Getting Started with Grails" brings you up to speed on this modern web framework. Companies as varied as LinkedIn, Wired, and Taco Bell are all using Grails. Are you ready to get started as well?
Those familiar with only ITIL V2 often scoff at the thought that ITIL could serve as a governance framework for SOA. With ITIL V3, the focus of the framework shifted towards service-orientation.
SpringSource CTO Adrian Colyer discusses AspectJ, SpringSource's dm Server and tc Server products, OSGi and Scrum.
Heroku's Adam Wiggins talks about Rails, Background Jobs, Add-Ons, Ruby, and how Heroku manages to work around Ruby's inefficiencies using Erlang and other languages.
For Grady Booch the foundation of a good architecture is patterns, SOA being just one of many patterns. In this Second Life presentation, Booch attempts to bring more clarity on what architecture is.
4 comments
Watch Thread Reply