Issue 9021: Section: section 5.5 (mof2versioning-ftf) Source: (, ) Nature: Clarification Severity: Critical Summary: From the MOF versioning specification its not clear , how to determine whether Extent is changed or not. In order to version an extent, first there is need to determine whether extent is changed or not. Is addition/modification/deletion of objects/slots/links considered as a change for an Extent? Can links go beyond extent? Can there be inter-versionedExtent links? If yes, then which extent 'owns' such links? and which extent is considered as changed? Is there any relationship with navigation of association, for determining which extent is changed? Resolution: see above, closed, no change Revised Text: Actions taken: September 28, 2005: received issue October 30, 2006: closed issue Discussion: In a versioning environment the extent must versioned and checked out before any changes can be made, otherwise it is read only. Links can go beyond extents and are resolved in the context of the version that is in the current workspace: in that sense it does not matter which extent owns the link. The storage of links (as instances of Associations) in extents is a general MOF issue and is not directly related to MOF versioning. Resolution: In a versioning environment the extent must versioned and checked out before any changes can be made, otherwise it is read only. Links can go beyond extents and are resolved in the context of the version that is in the current workspace: in that sense it does not matter which extent owns the link. The storage of links (as instances of Associations) in extents is a general MOF issue and is not directly related to MOF versioning. End of Annotations:===== m: webmaster@omg.org Date: 28 Sep 2005 00:24:19 -0400 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Suresh Babu Datla Company: Tata Consultancy Services Limited mailFrom: suresh.datla@tcs.com Notification: Yes Specification: MOF2 Versioning Final Adopted Specification Section: section 5.5 FormalNumber: Ptc/05-08-01 Version: finalization version RevisionDate: August 2005 Page: 6-7 Nature: Clarification Severity: Critical HTTP User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322) Description From the MOF versioning specification its not clear , how to determine whether Extent is changed or not. In order to version an extent, first there is need to determine whether extent is changed or not. Is addition/modification/deletion of objects/slots/links considered as a change for an Extent? Can links go beyond extent? Can there be inter-versionedExtent links? If yes, then which extent 'owns' such links? and which extent is considered as changed? Is there any relationship with navigation of association, for determining which extent is changed? To: Juergen Boldt Cc: issues@omg.org, mof2versioning-ftf@omg.org Subject: Re: issue 9021 -- MOF 2 Versioning FTF issue X-Mailer: Lotus Notes Release 6.0.2CF1 June 9, 2003 From: Geoffrey M Clemm Date: Sun, 2 Oct 2005 09:54:58 -0400 X-MIMETrack: Serialize by Router on D01ML261/01/M/IBM(Build V70_08142005|August 14, 2005) at 10/02/2005 09:54:41, Serialize complete at 10/02/2005 09:54:41 As to whether links can cross extents, I believe the answer is unequivocably yes. But as to where the information about such links is stored, I believe it is likely that we will have to leave that unspecified, since different implementations want/need to make different choices. Logically, the information could be stored in just one of the linked extents, in both extents, or as a separate artifact that is independent of both extents (i.e., some kind of "link table"). For links that are declared to be navigable in only one direction, we might be able to get consensus that the state of that link is stored in the "from" side of the link (although the "link table" implementors will probably object). But for links that can be navigated in both directions, it is not clear whether the link should be stored in just one side or in both (or in a separate artifact). So it is probably worth trying to get consensus, but I would not be especially optimistic about it being achieved so I would defer the resolution of this issue to a later version of the specification. Cheers, Geoff From: webmaster@omg.org Date: 28 Sep 2005 00:24:19 -0400 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Suresh Babu Datla Company: Tata Consultancy Services Limited mailFrom: suresh.datla@tcs.com Notification: Yes Specification: MOF2 Versioning Final Adopted Specification Section: section 5.5 FormalNumber: Ptc/05-08-01 Version: finalization version RevisionDate: August 2005 Page: 6-7 Nature: Clarification Severity: Critical HTTP User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322) Description >From the MOF versioning specification its not clear , how to determine whether Extent is changed or not. In order to version an extent, first there is need to determine whether extent is changed or not. Is addition/modification/deletion of objects/slots/links considered as a change for an Extent? Can links go beyond extent? Can there be inter-versionedExtent links? If yes, then which extent 'owns' such links? and which extent is considered as changed? Is there any relationship with navigation of association, for determining which extent is changed? ================================= Jürgen Boldt Director, Member Services Object Management Group 250 First Avenue, Suite 100 Needham, MA 02494 Tel. +1 781 444 0404 ext. 132 Fax: +1 781 444 0320 email: juergen@omg.org www www.omg.org ================================ Subject: RE: issue 9021 -- MOF 2 Versioning FTF issue Date: Sun, 2 Oct 2005 07:21:35 -0700 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: issue 9021 -- MOF 2 Versioning FTF issue Thread-Index: AcXHWODuDrk3HYDOTaqhLsARYsgDawAAR4Ag From: "Pete Rivett" To: "Geoffrey M Clemm" , Cc: Responding to the questions in the original Issue... From the MOF versioning specification its not clear , how to determine whether Extent is changed or not. In order to version an extent, first there is need to determine whether extent is changed or not. It's the other way round - in a versioning environment you have to version an extent before you can make any changes - otherwise it is read only. Is addition/modification/deletion of objects/slots/links considered as a change for an Extent? Yes Can links go beyond extent? Yes Can there be inter-versionedExtent links? Geoff is right that links can cross extents. The links are version-independent and it is the current workspace that will resolve the target version when navigating such links. If yes, then which extent 'owns' such links? The storage of links (as instances of Associations) in extents is a general MOF issue and is not directly related to MOF versioning: the alternatives are as Geoff states. I agree with Geoff that it is underspecified and this does need to be addressed - though not specifically for versioning (possibly in the MOF Facility specification still in preparation). and which extent is considered as changed? This too needs more specification: I would say the extent containing the link and any extent containing an element which has an ownedAttribute referencing that link. Is there any relationship with navigation of association, for determining which extent is changed? Not with navigation of association but with ownership of the association ends (these aspects were separated in the UML FTF): see previous response. Note that the above responses assume CMOF. EMOF does not have associations and hence does not have links in this sense: there are only ownedAttributes referencing other elements. In which case these are directly tied to the element owning the attribute (in the same extent etc). Regards Pete -------------------------------------------------------------------------------- From: Geoffrey M Clemm [mailto:geoffrey.clemm@us.ibm.com] Sent: Sunday, October 02, 2005 2:55 PM To: Juergen Boldt Cc: issues@omg.org; mof2versioning-ftf@omg.org Subject: Re: issue 9021 -- MOF 2 Versioning FTF issue As to whether links can cross extents, I believe the answer is unequivocably yes. But as to where the information about such links is stored, I believe it is likely that we will have to leave that unspecified, since different implementations want/need to make different choices. Logically, the information could be stored in just one of the linked extents, in both extents, or as a separate artifact that is independent of both extents (i.e., some kind of "link table"). For links that are declared to be navigable in only one direction, we might be able to get consensus that the state of that link is stored in the "from" side of the link (although the "link table" implementors will probably object). But for links that can be navigated in both directions, it is not clear whether the link should be stored in just one side or in both (or in a separate artifact). So it is probably worth trying to get consensus, but I would not be especially optimistic about it being achieved so I would defer the resolution of this issue to a later version of the specification. Cheers, Geoff From: webmaster@omg.org Date: 28 Sep 2005 00:24:19 -0400 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Suresh Babu Datla Company: Tata Consultancy Services Limited mailFrom: suresh.datla@tcs.com Notification: Yes Specification: MOF2 Versioning Final Adopted Specification Section: section 5.5 FormalNumber: Ptc/05-08-01 Version: finalization version RevisionDate: August 2005 Page: 6-7 Nature: Clarification Severity: Critical HTTP User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322) Description From the MOF versioning specification its not clear , how to determine whether Extent is changed or not. In order to version an extent, first there is need to determine whether extent is changed or not. Is addition/modification/deletion of objects/slots/links considered as a change for an Extent? Can links go beyond extent? Can there be inter-versionedExtent links? If yes, then which extent 'owns' such links? and which extent is considered as changed? Is there any relationship with navigation of association, for determining which extent is changed? ================================= Jürgen Boldt Director, Member Services Object Management Group 250 First Avenue, Suite 100 Needham, MA 02494 Tel. +1 781 444 0404 ext. 132 Fax: +1 781 444 0320 email: juergen@omg.org www www.omg.org ================================