MOF2 Versioning and Development Lifecycle Avatar
  1. OMG Specification

MOF2 Versioning and Development Lifecycle — All Issues

  • Acronym: MOFVD
  • Issues Count: 5
  • Description: All Issues
Open Closed All
All Issues

Issues Descriptions

AnnexB: Links to Constraint OCL Files Crossed


MOF Versioning & Development Lifecycle Spec (MOF VD) 2.0: How are VersionedExtents created?

  • Key: MOF26-33
  • Legacy Issue Number: 18905
  • Status: open  
  • Source: NASA ( Dr. Nicolas F. Rouquette)
  • Summary:

    The MOF Facilities Object Lifecycle (MOF FOL) 2.0 spec defines "factory" methods in MOFFOL::Facility::createExtent(…)

    This method can create either an Extent or a URIExtent.

    MOF VD defines VersionedExtent as a specialization of URIExtent and Extent.
    However MOF VD provides no operation for creating a VersionedExtent.
    Are are such entities to be created?

  • Reported: MOFVD 2.1 — Wed, 11 Sep 2013 04:00 GMT
  • Updated: Tue, 29 Mar 2016 15:44 GMT

MOF2 Versioning Issue: Include annotated examples from presentation

  • Key: MOF26-32
  • Legacy Issue Number: 9810
  • Status: open  
  • Source: Adaptive ( Mr. Pete Rivett)
  • Summary:

    The slides produced by Geoff Clemm for the submission presentation were very helpful and should be included in the specification itself along with a bit of detail as to how they relate to the metamodel

  • Reported: MOFVD 2.0b1 — Thu, 8 Jun 2006 04:00 GMT
  • Updated: Tue, 29 Mar 2016 15:44 GMT

Sections 5.3 and 5.5

  • Key: MOFVD2-2
  • Legacy Issue Number: 8999
  • Status: closed  
  • Source: Tata Consultancy Services Limited ( Suresh Babu Datla)
  • Summary:

    The "MOF2.0 Core Specification" states that a package may contain other packages, which may in turn contain other Packages. But the "MOF2 Versioning Final Adopted Specification" doesn't mention about the versioning semantics related to containment of packages. Following are few concerns: If 'checkIn()' operation of a VersionedExtent object is called and if this VersionedExtent object contains other VersionedExtents, then should new versions be created even for the contained VersionedExtents ? If 'delete()' operation of a Version object is called and if this Version object contains other Versions, then should the deletion be performed even for the contained Versions ?

  • Reported: MOFVD 2.0b1 — Tue, 13 Sep 2005 04:00 GMT
  • Disposition: Resolved — MOFVD 2.0
  • Disposition Summary:

    see above, closed, no change

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Section: section 5.5

  • Key: MOFVD2-3
  • Legacy Issue Number: 9021
  • Status: closed  
  • Source: Tata Consultancy Services Limited ( Suresh Babu Datla)
  • 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?

  • Reported: MOFVD 2.0b1 — Wed, 28 Sep 2005 04:00 GMT
  • Disposition: Resolved — MOFVD 2.0
  • Disposition Summary:

    see above, closed, no change

  • Updated: Fri, 6 Mar 2015 20:58 GMT