Hi Guys Not sure whether this is the place to address this... but I would really like to
* interrogate the Naked Objects spec to see if it can handle relationships gracefully and * interrogate the resultant RestFul Objects spec for the same reason. At the moment both of these specs treat relationships in a shallow way as un-typed compositions and aggregations. I would like to bring first class relationships in at the spec level rather as an Isis add-on or branch. My analysis points to a need for an entirely different approach to composition and aggregations that manages and leverages these richer relationships to sub-objects and aggregated objects. Both Naked and Restful Objects need to somehow start listing the relationships available on an object and avoid un-typed relationships. I suspect that this might lead to even stronger domains more capable of representing complex business needs. I understand that this poses a political problem in the sense that graph databases are still young and most projects feel safe with RDBMS, but I'm convinced this will change. Perhaps we could branch at the specification level? I am willing to work on both the spec and the implementation. Thnx Sizwe To read WesBank's Disclaimer for this email click on the following address or copy into your Internet browser: https://www.wesbank.co.za/wesbankcoza/about/legal/emaildisclaimer.xhtml If you are unable to access the Disclaimer, send a blank e-mail to [email protected] and we will send you a copy of the Disclaimer.
