Issues for Mailing list of the MOF 2.0 Facility and Object Lifecycle Finalization Task Force

To comment on any of these issues, send email to mof-facility-ftf@omg.org. (Please include the issue number in the Subject: header, thusly: [Issue ###].) To submit a new issue, send email to issues@omg.org.

List of issues (green=resolved, yellow=pending Board vote, red=unresolved)

List options: All ; Open Issues only; or Closed Issues only

Issue 6904: Need to specify URI structure
Issue 6909: Migration of package relationships
Issue 15642: Incomplete URIStore definition
Issue 15643: Issues on MOF Facility formal/10-03-04
Issue 15647: Section 7 of formal/2010-03-04

Issue 6904: Need to specify URI structure (mof-facility-ftf)

Click here for this issue's archive.
Source: Adaptive (Mr. Pete Rivett, pete.rivett(at)adaptive.com)
Nature: Uncategorized Issue
Severity:
Summary:
Summary: 
isID semantics - the 'may be used' is too weak. I think myself and Joaquin have made the point that we
need to specify the URI structure to get interoperability (and I don't mean the W3C standard - I mean how to construct
the URI from the objects/extents/properties/containers being identified).

Resolution: mof-facility-ftf
Revised Text:
Actions taken:
January 15, 2004: received issue
January 20, 2011: Transferred to MOF2 Facility (now adopted)

Discussion:
This will be addressed by the MOF 2 Facility RFP where it is a specific requirement.

Disposition:	Transferred to MOF2 Facility (now adopted)


Issue 6909: Migration of package relationships (mof-facility-ftf)

Click
here for this issue's archive.
Source: Adaptive (Mr. Pete Rivett, pete.rivett(at)adaptive.com)
Nature: Uncategorized Issue
Severity:
Summary:
Summary:
At MOF 1.4, packages can be related through: 
- import 
- nesting 
- inheritance 
- clustering 
We haven't really addressed this aspect of migration which should be added to Chapter 9. 
Personally I think there's little value in MOF 1.4 nesting and inheritance relationships and they're infrequently used in real metamodels (if people know what they're doing - occasionally people nest packages in UML Profile for MOF without realizing the implications).

In UML2 though we do still have a nesting relationship between packages so should consider the implications in terms of MOF constraints and extents.

Conversely we no longer have clustering (the most useful relationship in MOF 1.4) though we do have merging (with 2 flavors): we need to consider the runtime implications of instantiating a package that merges other packages. Is it the same as clustering?

Resolution:
Revised Text:
Actions taken:
January 15, 2004: received issue
January 20, 2011: Transferred to MOF2 Facility (now adopted)

Discussion:
This will be addressed by the MOF 2 Facility RFP where it is a specific requirement.

Disposition:	Transferred to MOF2 Facility (now adopted)


Issue 15642: Incomplete URIStore definition (mof-facility-ftf)

Click
here for this issue's archive.
Nature: Uncategorized Issue
Severity:
Summary:
The diagram on p6 includes URIStore but with incomplete lines.

There is no subsection for it in 6.2.


Resolution:
Revised Text:
Actions taken:
September 26, 2010: received issue

Discussion:
Issue on MOF Facility and Object Lifecycle formal/10-03-04


Issue 15643: Issues on MOF Facility formal/10-03-04 (mof-facility-ftf)

Click
here for this issue's archive.
Source: Adaptive (Mr. Pete Rivett, pete.rivett(at)adaptive.com)
Nature: Uncategorized Issue
Severity:
Summary:
1.       The figures should have numbers and captions

 



 


Resolution:
Revised Text:
Actions taken:
September 26, 2010: received issue

Discussion:


Issue 15647: Section 7 of formal/2010-03-04 (mof-facility-ftf)

Click
here for this issue's archive.
Source: Adaptive (Mr. Pete Rivett, pete.rivett(at)adaptive.com)
Nature: Uncategorized Issue
Severity:
Summary:
2.       Section 7 should be applied to the other specifications not left in this specification

Resolution:
Revised Text:
Actions taken:
September 26, 2010: received issue