Issues for BOCA RTF-(defunct list)

To comment on any of these issues, send email to boca-rtf@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 1168: Inconsistency of Section 7.2, pages 234-288 with other partsd of doc.
Issue 1238: IDL map for relationship/Framework alignment
Issue 1412: OBV additions to CORBA core Model
Issue 1479: Issue with InvocationArgument
Issue 1481: Attributes that are supposed to be relationships

Issue 1168: Inconsistency of Section 7.2, pages 234-288 with other partsd of doc. (boca-rtf)

Click here for this issue's archive.
Nature: Revision
Severity:
Summary:
Summary: Section 7.2, pages 234-288 will be inconsistent with other parts of
 document due to:
 1.  Several issues/resolutions arising from mof-rtf on transformation of
 MOF meta model to IDL.
 2.  Specific problems with MODL to MOF IDL, as identified in mof-rtf
 issues.
 3.  Probable (minor) changes to  BOCA meta model (as expressed in CDL),
 to correct inconsistencies in document.
 
 Recommendation:
 Re-issue the IDL section following resolution of  issues impacting BOCA
 meta model (as expressed in CDL).
 

Resolution:
Revised Text:
Actions taken:
April 22, 1998: received issue
June 23, 1998: closed issue

Discussion:


Issue 1238: IDL map for relationship/Framework alignment (boca-rtf)

Click
here for this issue's archive.
Nature: Revision
Severity:
Summary:
Summary: p. 152, line currently states:
 <relationship_get> is generated if relationship::is_naviagable=-=TRUE
 
 In the Interoperability Specification (bom/98-04-05), page 40, the
 mapping for a one-to-many relationship does not include
 <relationship_get>, with justification on pages 38-40.   
 
 Recommendation:
 To align with the Interoperability Specification, referenced line above
 should read:
 
 <relationship_get> is generated if (relationship::is_navigable &&
 relationship::multiplicity.upper==1)
 
 Also, on p. 151 the first production in the IDL Map definition should
 make it clear that <relationship_get> is optional  and should read:
 
 <relationship> ::= [<relationship_get> ] [[";"] <relationship_set> ]
 [[";"] <relationship_import>] [[";"] <relationship_inherit>]
 

Resolution: :is_naviagable=-=TRUE
Revised Text:
Actions taken:
April 27, 1998: received issue
June 23, 1998: closed issue

Discussion:


Issue 1412: OBV additions to CORBA core Model (boca-rtf)

Click
here for this issue's archive.
Nature: Uncategorized Issue
Severity:
Summary:
Summary: The BocaErrata document, bom/98-03-15, on page 2, section "Appendix 5 -
 Objects By Value (OBV)" states:
 
 "The Corba-Core meta-model (as reflected in BOCA) has not been updated
 to reflect OBV, it is recommended that a Corba-Core Meta-Model that
 reflects the OBV additions be developed by the revision task force."
 
 This statement explicitly requests the boca-rtf to extend the CORBA-CORE
 model documented in the BOCA submission (bom/98-01-07) to incorporate
 CORBA Objects By Value.
 

Resolution:
Revised Text:
Actions taken:
June 1, 1998: received issue

Discussion:


Issue 1479: Issue with InvocationArgument (boca-rtf)

Click
here for this issue's archive.
Nature: Revision
Severity:
Summary:
Summary: 
 Another issue with InvocationArguement:  The relationship call is the inverse of a Composes relationship, so 
 it is incorrect to declare it as an IsPartOf relationship.
 
 Recommendation: In the CDL declaration of the relationship call, IsPartOf shold be changed to IsOwnedBy.
 

Resolution: The relationship call is the inverse of a Composes relationship, so
Revised Text:
Actions taken:
June 3, 1998: received issue
June 23, 1998: closed issue

Discussion:
 Accept recommendation. issue closed


Issue 1481: Attributes that are supposed to be relationships (boca-rtf)

Click
here for this issue's archive.
Nature: Revision
Severity:
Summary:
Summary: 
 The following UML classifiers describing BOCA meta-types have attributes that are actually supposed to be 
 relationships.  The following table specifies the meta-types that have this problem and the problematic 
 attributes:
 
 BocaMeta-type
 Attribute
 Target BocaMeta-type
 CorbaCollection
 content_type
 Classifier
 CorbaAlias
 alias_of
 Classifier
 CorbaUnion
 discriminator_type
 CorbaType
 
 Recommendation: Remove the attributes or else mark them as derived attributes.  Draw the associations 
 where practical.
 

Resolution:
Revised Text:
Actions taken:
June 3, 1998: received issue
June 23, 1998: closed issue
April 25, 2011: closed issue

Discussion: