Re: Comment on SDO overview from Tuscany site
No comment in the past 10 days; can I assume the update looks fine and I can sumbit a patch please? The timing seems nice since we're releasing M2. -- Yang ZHONG
Re: Comment on SDO overview from Tuscany site
I've just updated the demo into http://issues.apache.org/jira/browse/TUSCANY-751 Please review by unzip http://issues.apache.org/jira/secure/attachment/12341982/NewSdoOverview2.zip and use a browser to open sdo_index.html; the introduction page (thank Kelvin) is 1 click (bottom) from the overview, then the explore diagram can be clicked into respective introduction. Thank Kelvin and Luciano for the inputs, I think I've incorporated all of them such as . make overview briefer (Luciano Kelvin) . page layout (Kelvin) . move new diagrams into diferent page (Kelvin Luciano) Let me know if I missed anything and also welcome new inputs. Thanks. -- Yang ZHONG
Re: Comment on SDO overview from Tuscany site
Hi Yang, thanks for that. A few comments ... - i agree with Luciano that we are trying to get too much on the overview page - it would be nice to take more control of the layout, particularly so that the single lines of text associated with images are clearly associated with those images and maybe stand out a bit more (perhaps using a table and controlling the sizes of the images to match up could help here) - I worry about using the value(s) class in the UML diagram, and then leaving that unqualified (no link from that UML block). Technically Object would be better, but still leave the reader not much wiser and it doesn't get over the picture that this is the association by which the graph of DataObject's is built up as well as that by which simple property values are held. - It would be good to see Sequence in the UML diagram Cheers, Kelvin. On 27/09/06, Yang ZHONG [EMAIL PROTECTED] wrote: I've just attached a demo into http://issues.apache.org/jira/browse/TUSCANY-751 Please review by unzip http://issues.apache.org/jira/secure/attachment/12341763/NewSdoOverview.zip and use a browser to open sdo_index.html; the overview diagram can be clicked into respective introduction. Looking forward to your inputs and I'll incorporate them. Thanks. On 9/22/06, Yang ZHONG [EMAIL PROTECTED] wrote: 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 -- Yang ZHONG
Re: Comment on SDO overview from Tuscany site
Sorry Yang, one further thought on the UML diagram is that you have labelled the link between DataObject and ChangeSummary as changeSummary, which might lead the user to think that changeSummary is an instance member of DataObject and that they could somehow simply trigger a non-null instance to be present in an arbitrary DataObject by perhaps calling getChangeSummary(). This runs counter to the facts that a given DataObject instance can be associated with a ChangeSummary indirerctly through the containment hierarchy, and that there must be a property of ChangeSummaryType in the Type of the DataObject, which may or may not be called changeSummary, before it can directly contain a ChangeSummatry instance. An alternative would perhaps be that we could edit the compartment of the uml block for DataObject and make some key methods visible, such as getChangeSummary(), I guess its possible that this approach might address my concern about the value(s) class too, in that we could add a few get*(*) methods to the DataObject's compartment, but that might become messy. Cheers, Kelvin. On 27/09/06, kelvin goodson [EMAIL PROTECTED] wrote: Hi Yang, thanks for that. A few comments ... - i agree with Luciano that we are trying to get too much on the overview page - it would be nice to take more control of the layout, particularly so that the single lines of text associated with images are clearly associated with those images and maybe stand out a bit more (perhaps using a table and controlling the sizes of the images to match up could help here) - I worry about using the value(s) class in the UML diagram, and then leaving that unqualified (no link from that UML block). Technically Object would be better, but still leave the reader not much wiser and it doesn't get over the picture that this is the association by which the graph of DataObject's is built up as well as that by which simple property values are held. - It would be good to see Sequence in the UML diagram Cheers, Kelvin. On 27/09/06, Yang ZHONG [EMAIL PROTECTED] wrote: I've just attached a demo into http://issues.apache.org/jira/browse/TUSCANY-751 Please review by unzip http://issues.apache.org/jira/secure/attachment/12341763/NewSdoOverview.zip and use a browser to open sdo_index.html; the overview diagram can be clicked into respective introduction. Looking forward to your inputs and I'll incorporate them. Thanks. On 9/22/06, Yang ZHONG [EMAIL PROTECTED] wrote: 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
Re: Comment on SDO overview from Tuscany site
I'm not saying this is/was Java only, just suggesting it could be somewhere else other then on the first page. The java overview was just an example, but maybe java and c++ overview could link to a page describing the sdo object model and then it would bring up your class diagram page... and then you could have more flexibility on getting more descriptive text and mode tech details on those pages as needed Also, removing a 2 line of text referencing DAS won't make a big difference on the page... Well... these are just some of my thoughts... - Luciano On 9/27/06, Yang ZHONG [EMAIL PROTECTED] wrote: Thank Kelvin for diagram(s) input, I'll update the demo once I receive the concrete changes for sending which thank Kelvin again. Thank Luciano and Kelvin for suggesting reducing overview content. Do you have concrete instructions please? Otherwise, how about removing SDO offers a convenient way to work with XML documents...? If not enough, how about removing DAS briefing since it has its own overview now? If still not enough, there were two diagrams before and which one do you propose to remove please? Luciano, thanks for the feedback. By saying probably linked from the SDO Java page, have you got the impression the new clickable diagram is for Java only? If so, could you point out the Java implication so that we can remove since the overview is for general purpose please? -- Yang ZHONG
Re: Comment on SDO overview from Tuscany site
I've just attached a demo into http://issues.apache.org/jira/browse/TUSCANY-751 Please review by unzip http://issues.apache.org/jira/secure/attachment/12341763/NewSdoOverview.zip and use a browser to open sdo_index.html; the overview diagram can be clicked into respective introduction. Looking forward to your inputs and I'll incorporate them. Thanks. On 9/22/06, Yang ZHONG [EMAIL PROTECTED] wrote: 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 -- Yang ZHONG
Re: Comment on SDO overview from Tuscany site
I'm going to give you the same feedback I got for the DAS pages. The overview page should not be very overloaded, in your case, I'd recommend moving the class/object diagram for a secundary page, probably linked from the SDO Java page. - Luciano On 9/26/06, Yang ZHONG [EMAIL PROTECTED] wrote: I've just attached a demo into http://issues.apache.org/jira/browse/TUSCANY-751 Please review by unzip http://issues.apache.org/jira/secure/attachment/12341763/NewSdoOverview.zip and use a browser to open sdo_index.html; the overview diagram can be clicked into respective introduction. Looking forward to your inputs and I'll incorporate them. Thanks. On 9/22/06, Yang ZHONG [EMAIL PROTECTED] wrote: 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 -- Yang ZHONG
Re: Comment on SDO overview from Tuscany site
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
