It is a useful approach, in my opinion, and has been used for some time for handling content in applications. It isn't particularly new. You will find a very similar specification (although with a narrower focus) in the Clinical Observation Access Service from the OMG circa 2000. The interesting thing about that specification, is that the knowledge of "clinical data" is only in the actual data moved, not in the methods used to manipulate the data. It also supports a superset if XML.
It is nice to see these concepts used in an even more general way. Dave Forslund Teo Hui Ming wrote: > > On 7/10/06, Gregg Wonderly <[EMAIL PROTECTED] <mailto:gergg%40cox.net>> wrote: > > > [1] "JSR 170 Overview: Standardizing the Content Repository Interface" > > There are a lot of interesting words, phrases and paragraphs in this > JSR. > > However, there isn't a lot of useful, new ideas about how to solve > problems. > > Interesting, wish you can elaborate more. From the paper, > content-centric interface looks promising in integration problems. By > comparing itself to control-centric, it gives a new appearance to HTTP > and Web (document-based distributed system) presented as another > design (plus implementation) choice for service-based software. So, > what's the missing point in this idea? > > -- > Teo Hui Ming > teohuiming.work at gmail dot com > > ------------------------ Yahoo! Groups Sponsor --------------------~--> Great things are happening at Yahoo! Groups. See the new email design. http://us.click.yahoo.com/TISQkA/hOaOAA/yQLSAA/NhFolB/TM --------------------------------------------------------------------~-> Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/service-orientated-architecture/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
