Nick Gall wrote: > > Sounds elegantly simple, as one would expect from a "webful" design. I > use "webful" because I don't want to start YARD - Yet Another Rest > Debate. <grin>
:). Actually .. the registry we're implementing is truly RESTful. It actually has no WS-* in at all ;-). Its basically a Java API and then a "Web API" which is AtomPub. We are planning to do an alpha release next week; feedback from playing with that will be greatly welcome. > This elegant use of URIs serves as yet another reminder that while the > world very quickly understood the deep power and rich flexibility > offered by a universal format standard -- XML -- it has taken that same > world much longer to understand the substantially deeper power and > richer flexibility offered by a universal identifier standard -- URI. > This despite the fact that TBL said long ago that > <http://www.furl.net/item/3421653>: > > The most fundamental specification of Web architecture, while one of the > simpler, is that of the Universal Resource Identifier, or URI. The > principle that anything, absolutely anything, "on the Web" should > identified distinctly by an otherwise opaque string of characters (A URI > and possibly a fragment identifier) is core to the universality. > > By using URIs as the uniform identifier for any (meta)data a reg/rep may > contain and by enabling such URIs to be associated with any > service/resource WSO2 is able to offer a simpler, more general, more > webful annotation solution. > > Don't /use/ the web -- become the web. +1. For the problem of a registry & repository I'm convinced that a RESTful design is the right answer. Let's not start the debate on whether that's the right answer to every problem ;-). Sanjiva. -- Sanjiva Weerawarana, Ph.D. Founder & Director; Lanka Software Foundation; http://www.opensource.lk/ Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/ Member; Apache Software Foundation; http://www.apache.org/ Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
