AW: [sdo] Containment discussion

["Barack, Ron" <ron.barack@sap.com>]

Hi,

 

I'd like to revive this mail thread.  I think the first question has been answered in Xcalia's document.  To me, the compelling use-case is that we have two SDO based applications that want to communicated.  Neither cares about specifying an XSD to which the message should conform, they just want to send SDOs over an XML wire.

 

That leaves the second question... now, the question is specifically to Oracle.  Technical Root can transform *any* graph to XML.  I think there is no tuning that can be done to the Oracle proposal to achive this, because Oracle's proposal tries to do something that is impossible:  it tries to add properties to the basic structure to achieve closure *based on examining the metadata*.  TechRoot does something else... it works directly with the data in the graph, not with the metadata.

 

That being the case, what are the reasons for preferring Oracle's algorithm over TechRoot?

 

 

Ron

 

---

Von: Barack, Ron [mailto:ron.barack@sap.com]
Gesendet: Mittwoch, 9. April 2008 00:33
An: sdo@lists.oasis-open.org
Betreff: [sdo] Containment discussion

Hi Blaise and Xcalia

 

Two questions...

 

1.  Before we embark on a long discussion of this (or any other) proposal for dealing with containment, I think it's first important to get our use-cases straight.  Which use cases are you aiming at here, and why is the functionality provided by issue 66, and in particular the convenience methods based on it, not the best means to deal with it.  As I understand your use-case, it seems to fit very well indeed to issue-66.

 

2. This propoal does not generate a closed XML document from an arbitrary SDO data graph.  There are other algorithms that do, for instance, Xcalia's TechnicalRoot proposal.  I would think that the main requirement of such an approach to containing is that it can produce XML out of any data graph.  What is the advantage of prefering this approach to Technical Root?

 

Best Regards,

Ron