Thank Andrew for the support and thank Kelvin and Geoff for the text contribution.
I propose this brief description right after "SDO is a natural format ...": "SDO provides flexible data structures that allow data to be organized as graphs of objects (called data objects) that are composed of properties. Properties can be single or many valued and can have other data objects as their values. A data object can maintain a change summary of the alterations made to it, providing efficient communication of changes and a convenient way to update an original data source. SDO naturally permits disconnected data access patterns with an optimistic concurrency control model. Change summaries are great for doing roll-back too." "SDO offers a convenient way to work with XML documents. SDO implementations provide helpers to populate a data graph from both XML documents and relational databases and also to read SDO metadata from an XML Schema Definition (XSD). Data objects can be serialized to XML and the metadata can be serialized to an XSD file." And I propose this structural diagram clickable towards brief DataObject, Type, Property and ChangeSummary description: http://issues.apache.org/jira/secure/attachment/12341428/overview.gif As for DataObject brief description page, I propose "Data objects are composed of properties. Properties can be single or many valued and can have other data objects as their values. A data object can maintain a change summary of the alterations made to it." with this diagram: http://issues.apache.org/jira/secure/attachment/12341426/DataObject.gif As for Type brief description page, I propose "Type is the model of DataObject. Type is composed of Properties, also Type inherits Properties from base Types." with this diagram: http://issues.apache.org/jira/secure/attachment/12341429/type.gif As for ChangeSummary brief description page, I propose "ChangeSummary provides efficient communication of changes and a convenient way to update an original data source. SDO naturally permits disconnected data access patterns with an optimistic concurrency control model. Change summaries are great for doning roll-back too." with this diagram: http://issues.apache.org/jira/secure/attachment/12341430/ChangeSummary.gif As for Property brief description page, I propose "A Property can be single or many valued, and value has a Type. A Property can specify a default value." with this diagram: http://issues.apache.org/jira/secure/attachment/12341425/property.gif On second thought, maybe the linked description pages doesn't have to be brief. What do you think and what do you propose if we can put more description there please? Looking forward to your inputs and I'll incorporate them. Thanks. -- Yang ZHONG
