[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [sdo] Groups - Proposal - Containment and Enterprise Data Models (SDO-EnterpriseDataModel.doc) uploaded
Hi Ron, If PhoneNumber had a second FK to another table that satisfies my proposed definition of "containment". SDO 2.1 (and my proposal) allows for multiple containment properties to be of the same type, so we're ok there. The SDO 2.1 spec requires that an instance only be referenced by a single containment relationship. This is supported in the API (i.e. getContainer() returns only one DataObject). My proposal does not address changing this limitation. The RDB to SDO mapping section in my proposal is a proof of concept and not a new ORM spec, but one could imagine providing a mechanism in the mapping to allow a containment relationship to be marked as non-containment. Allowing an instance to have two containers would provide even better support for deriving SDO metadata from other sources (such as relational databases and JPA entities). This however would require API and spec changes that are seperate and distinct from this proposal. -Blaise ----- Original Message ----- From: "Barack, Ron" <ron.barack@sap.com> To: <blaise.doughan@oracle.com>; <sdo@lists.oasis-open.org> Sent: Monday, April 07, 2008 3:00 PM Subject: AW: [sdo] Groups - Proposal - Containment and Enterprise Data Models (SDO-EnterpriseDataModel.doc) uploaded Hi Blaise, I'm looking at the RDB to SDO mapping. On page 22 you derive the containment relationship betweeen PhoneNumber and Employee because PhoneNumber has a FK to employee. What happens PhoneNumber has a second FK to a second table. Would both imply containment relationships? Best Regards, Ron -----Ursprüngliche Nachricht----- Von: blaise.doughan@oracle.com [mailto:blaise.doughan@oracle.com] Gesendet: Montag, 7. April 2008 19:59 An: sdo@lists.oasis-open.org Betreff: [sdo] Groups - Proposal - Containment and Enterprise Data Models (SDO-EnterpriseDataModel.doc) uploaded Hello All, I have uploaded a new version of the proposal. This version contains an example of how SDO containment metadata can be derived from JPA entities. To see the change bars in MS Word: Tools | Track Changes | Highlight Changes -Blaise -- Mr. Blaise Doughan The document revision named Proposal - Containment and Enterprise Data Models (SDO-EnterpriseDataModel.doc) has been submitted by Mr. Blaise Doughan to the OASIS Service Data Objects (SDO) TC document repository. This document is revision #1 of SDO-EnterpriseDataModel.doc. Document Description: The SDO spec to date has primarily concerned itself with deriving SDO metadata from XML schema. As such containment has come to represent the concept of nesting as it relates to XML elements. We prefer to think of containment as it relates to data sharing between types. For the association "residence" between types "Employee" and "Address" if instances of "Employee" may not share references to instances of "Address" then it is a containment relationship: Containment: employeeDO1.get("residence") == employeeDO2.get("residence"); // This can never be true Non-Containment: employeeDO1.get("residence") == employeeDO2.get("residence"); // This can be true Using the above interpretation of containment it becomes easy to derive SDO metadata from other sources, such as JPA entities, JAXB objects, relational databases, etc. (the doc provides examples of deriving SDO metadata from a relational database & JPA entities). These sources may not have a concept of nesting, but they are aware of data sharing rules. Of course DataObjects require an XML representation, and containment has been an important part of that. The attached proposal contains an algorithm that makes use of containment properties when they are present and handles things when they are not. View Document Details: http://www.oasis-open.org/apps/org/workgroup/sdo/document.php?document_id=27869 Download Document: http://www.oasis-open.org/apps/org/workgroup/sdo/download.php/27869/SDO-EnterpriseDataModel.doc Revision: This document is revision #1 of SDO-EnterpriseDataModel.doc. The document details page referenced above will show the complete revision history. PLEASE NOTE: If the above links do not work for you, your email application may be breaking the link into two pieces. You may be able to copy and paste the entire link address into the address field of your web browser. -OASIS Open Administration
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]