Common Warehouse Metamodel Avatar
  1. OMG Specification

Common Warehouse Metamodel — Open Issues

  • Acronym: CWM
  • Issues Count: 51
  • Description: Issues not resolved
Open Closed All
Issues not resolved

Issues Summary

Key Issue Reported Fixed Disposition Status
CWM12-17 21.5 SQL-99 Data Types CWM 1.1 open
CWM12-22 Location: 12.1 Overview CWM 1.1 open
CWM12-7 Location: 5.4 CWM 1.1 open
CWM12-11 Annex F: Acknowledgements CWM 1.1 open
CWM12-39 Location: 3 Normative References -- OCL CWM 1.1 open
CWM12-5 Add features for 11404 aggregates CWM 1.1 open
CWM12-14 Annex A: References CWM 1.1 open
CWM12-16 21.6 Type Mapping Examples CWM 1.1 open
CWM12-47 TaggedValue CWM 1.1 open
CWM12-26 Location: 10.3.16 SQLIndex CWM 1.1 open
CWM12-42 Introduction - references CWM 1.1 open
CWM12-50 SQLParameter CWM 1.1 open
CWM12-2 The XML features should support current XML data structures CWM 1.1 open
CWM12-9 Introduction, Page XVII CWM 1.1 open
CWM12-38 Location: 4 Abbreviations and Conventions - ODBC CWM 1.1 open
CWM12-1 Add support for flat and nested N-dimensional arrays CWM 1.1 open
CWM12-24 10.3.18 SQLParameter CWM 1.1 open
CWM12-41 Location: 3 Normative References CWM 1.1 open
CWM12-27 Location: 10.2.8 Procedures CWM 1.1 open
CWM12-21 10.3.20 SQLStructuredType - referencingColumn CWM 1.1 open
CWM12-34 4 Abbreviations and Conventions - SQL-92 and SQL-99 CWM 1.1 open
CWM12-45 figure 6, page 212 CWM 1.1 open
CWM12-20 13.3.9 Schema CWM 1.1 open
CWM12-48 Invalid explicit references for some 'association generalizations' in the CWM 1.1 open
CWM12-3 Support the full set of 11404 aggregates. CWM 1.1 open
CWM12-31 Location: 10.2.4 Structured Types and Object Extension , Figure 10.5 CWM 1.1 open
CWM12-12 Annex D: Legal Information CWM 1.1 open
CWM12-30 Location: 10.2.6 Index CWM 1.1 open
CWM12-33 Location: 10.1 Overview CWM 1.1 open
CWM12-51 We only need one COBOL Data Division metamodel. CWM 1.1 open
CWM12-19 10.4.2 ColumnRefStructuredType CWM 1.1 open
CWM12-13 Annex C: Glossary CWM 1.1 open
CWM12-18 13.1 Overview CWM 1.1 open
CWM12-29 Location: 10.3.15 SQLDistinctType CWM 1.1 open
CWM12-32 Location: 10.2.4 Structured Types and Object Extensions CWM 1.1 open
CWM12-46 Parameter CWM 1.1 open
CWM12-35 Location: 10.1 Overview CWM 1.1 open
CWM12-37 Location: 3 Normative References - ISO/IEC 9075:2003 Database language SQL CWM 1.1 open
CWM12-23 10.3.20 SQLStructuredType CWM 1.1 open
CWM12-49 page 9-276/Section: 9.3.22 of ptc/2002-01-02 -- CWM issue CWM 1.1 open
CWM12-4 Add datatype generators CWM 1.1 open
CWM12-8 Add syntax type to the metamodel. CWM 1.1 open
CWM12-6 value "name" attribute of ModelElement CWM 1.1 open
CWM12-15 Annex B: Compatibility with other Standards CWM 1.1 open
CWM12-36 Location: 4 Abbreviations and Conventions - SQL CWM 1.1 open
CWM12-40 Location: 4 Abbreviations and Conventions CWM 1.1 open
CWM12-44 Foreword CWM 1.1 open
CWM12-43 formal/03-03-02 CWM 1.1 open
CWM12-10 5.4 datatype attributes don't incorporate the features of 11404 datatype CWM 1.1 open
CWM12-25 10.3.17 SQLIndexColumn CWM 1.1 open
CWM12-28 Location: 10.3.14 SQLDataType CWM 1.1 open

Issues Descriptions

21.5 SQL-99 Data Types

  • Key: CWM12-17
  • Legacy Issue Number: 12325
  • Status: open  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    SQL-99 is superseded by SQL:2003 (see comment on 3), which is mainly the same except that BIT and BIT VARYING data types are no longer included.
    Proposed Solution: None proposed by source

  • Reported: CWM 1.1 — Wed, 19 Mar 2008 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

Location: 12.1 Overview

  • Key: CWM12-22
  • Legacy Issue Number: 12322
  • Status: open  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    "...and several examples are provided in Volume 2, Extensions, of the CWM Specification." This document is not referenced in either Clause 3 or the References Annex, and its role in this specification is not defined.

  • Reported: CWM 1.1 — Wed, 19 Mar 2008 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

Location: 5.4

  • Key: CWM12-7
  • Legacy Issue Number: 12334
  • Status: open  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    The list of datatypes are incomplete.
    Proposed Solution:
    Include all the datatypes of ISO/IEC 11404.

  • Reported: CWM 1.1 — Wed, 19 Mar 2008 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

Annex F: Acknowledgements

  • Key: CWM12-11
  • Legacy Issue Number: 12331
  • Status: open  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    This annex is not appropriate for an ISO standard, and cannot be normative.
    Proposed Solution: None proposed by source

  • Reported: CWM 1.1 — Wed, 19 Mar 2008 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

Location: 3 Normative References -- OCL

  • Key: CWM12-39
  • Legacy Issue Number: 12301
  • Status: open  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    Nature of Problem:
    A normative reference for OCL is required, because it is used in Clause 8 (and elsewhere)
    Proposed Solution: None proposed by source

  • Reported: CWM 1.1 — Wed, 19 Mar 2008 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

Add features for 11404 aggregates

  • Key: CWM12-5
  • Legacy Issue Number: 12338
  • Status: open  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    The record and multidimensional arrays are aggregate datatypes and the common features of 11404 aggregates should be supported.
    Proposed Solution:
    Add features for 11404 aggregates.

  • Reported: CWM 1.1 — Wed, 19 Mar 2008 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

Annex A: References

  • Key: CWM12-14
  • Legacy Issue Number: 12327
  • Status: open  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    This annex should not be described as Normative, since all normative references should be in Clause 3. Some of the non-normative reference should be normative and be moved to Clause 3. All references should be to current specifications.
    Proposed Solution: None proposed by source

  • Reported: CWM 1.1 — Wed, 19 Mar 2008 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

21.6 Type Mapping Examples

  • Key: CWM12-16
  • Legacy Issue Number: 12326
  • Status: open  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    These tables gives data types from X/Open CLI SQL, which is not referenced in either Clause 3 or the References Annex but should not be used because they should be data types defined by SQL and the mappings defined by the current version (4) of JDBC.
    Proposed Solution: None proposed by source

  • Reported: CWM 1.1 — Wed, 19 Mar 2008 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

TaggedValue

  • Key: CWM12-47
  • Legacy Issue Number: 5697
  • Status: open  
  • Source: International Business Machines ( Dan Chang)
  • Summary:

    CWM_1.0.dtd is missing the following element:
    <!ELEMENT CWM:ModelElement.taggedValue (CWM:TaggedValue)*>
    This element should be a child element of CWM:ModelElement and all elements
    that correspond to subclasses of ModelElement.

    Without this element, CWM_1.0.dtd does not conform to the CWM 1.0
    Metamodel. According to the metamodel, any ModelElement (or its subclass)
    can own TaggedValue through the TaggedElement aggregation.

  • Reported: CWM 1.1 — Thu, 24 Oct 2002 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

Location: 10.3.16 SQLIndex

  • Key: CWM12-26
  • Legacy Issue Number: 12316
  • Status: open  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    Nature of Problem:
    see comment on 10.2.6
    Proposed Solution: None proposed by source

  • Reported: CWM 1.1 — Wed, 19 Mar 2008 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

Introduction - references

  • Key: CWM12-42
  • Legacy Issue Number: 12299
  • Status: open  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    The references to MOF and XMI should be the ISO documents, as in the Foreword
    Proposed Solution: None proposed by source

  • Reported: CWM 1.1 — Wed, 19 Mar 2008 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

SQLParameter

  • Key: CWM12-50
  • Legacy Issue Number: 5106
  • Status: open  
  • Source: International Business Machines ( Jean-Jacques Daudenarde)
  • Summary:

    An SQLParameter has no attribute. It should have some of the Column attribute: length, precision, scale and isNullable at minimum. This is valid for all the RDBMS.

  • Reported: CWM 1.1 — Wed, 3 Apr 2002 05:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

The XML features should support current XML data structures

  • Key: CWM12-2
  • Legacy Issue Number: 12341
  • Status: open  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    The XML features should support current XML data structures.
    Proposed Solution:
    Add current technology.

  • Reported: CWM 1.1 — Wed, 19 Mar 2008 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

Introduction, Page XVII

  • Key: CWM12-9
  • Legacy Issue Number: 12332
  • Status: open  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    The URLs do not work for the "three key industry standards"
    Proposed Solution:
    Change the final / to a period in each URL.

  • Reported: CWM 1.1 — Wed, 19 Mar 2008 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

Location: 4 Abbreviations and Conventions - ODBC

  • Key: CWM12-38
  • Legacy Issue Number: 12304
  • Status: open  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    Nature of Problem:
    ODBC is Open Database Connectivity
    Proposed Solution: None proposed by source

  • Reported: CWM 1.1 — Wed, 19 Mar 2008 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

Add support for flat and nested N-dimensional arrays

  • Key: CWM12-1
  • Legacy Issue Number: 12339
  • Status: open  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    The multidimensional arrays should support the notion of APL arrays, including rank and shape attributes.
    Proposed Solution:
    Add support for flat and nested N-dimensional arrays (not just arrays nested as arrays).

  • Reported: CWM 1.1 — Wed, 19 Mar 2008 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

10.3.18 SQLParameter

  • Key: CWM12-24
  • Legacy Issue Number: 12318
  • Status: open  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    There should be a constraint that an SQL parameter can only be of type SQLDataType
    Proposed Solution: None proposed by source

  • Reported: CWM 1.1 — Wed, 19 Mar 2008 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

Location: 3 Normative References

  • Key: CWM12-41
  • Legacy Issue Number: 12300
  • Status: open  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    The references to MOF and XMI should be the ISO documents, as in the Foreword
    Proposed Solution: None proposed by source

  • Reported: CWM 1.1 — Wed, 19 Mar 2008 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

Location: 10.2.8 Procedures

  • Key: CWM12-27
  • Legacy Issue Number: 12313
  • Status: open  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    Nature of Problem:
    It is inappropriate to use the name Procedure for referring to both procedures and functions (see 10.3.9). SQL uses the term routine for this purpose.
    Proposed Solution: None proposed by source

  • Reported: CWM 1.1 — Wed, 19 Mar 2008 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

10.3.20 SQLStructuredType - referencingColumn

  • Key: CWM12-21
  • Legacy Issue Number: 12320
  • Status: open  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    The description of referencingColumn implies that only a 'column' (i.e. an attribute) of a structured type can be of a type REF, whereas any column of a table can be so.
    Proposed Solution: None proposed by source

  • Reported: CWM 1.1 — Wed, 19 Mar 2008 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

4 Abbreviations and Conventions - SQL-92 and SQL-99

  • Key: CWM12-34
  • Legacy Issue Number: 12307
  • Status: open  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    SQL-92 and SQL-99 should not be used since they are no longer valid, and should NOT be described as ANSI documents
    Proposed Solution: None proposed by source

  • Reported: CWM 1.1 — Wed, 19 Mar 2008 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

figure 6, page 212

  • Key: CWM12-45
  • Legacy Issue Number: 5925
  • Status: open  
  • Source: Anonymous
  • Summary:

    Anyway, I think that there is a little error on the figure 6-6 chapter 6.2.4 of the v1.1 (wich is the figure 6, page 212 in the PDF, chapter 9.2.4 on the "old" document) : the Person has a "salary Column" instead of a "name column".

  • Reported: CWM 1.1 — Tue, 29 Apr 2003 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

13.3.9 Schema

  • Key: CWM12-20
  • Legacy Issue Number: 12324
  • Status: open  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    The attribute XMLNamespace (also shown in Figure 13.1) is defined as a string, but it is an XML concept described by a specification separate from the referenced [XML], and quite distinct from the CWM concept of Namespace, and so should be referenced and described appropriately.
    Proposed Solution: None proposed by source

  • Reported: CWM 1.1 — Wed, 19 Mar 2008 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

Invalid explicit references for some 'association generalizations' in the

  • Key: CWM12-48
  • Legacy Issue Number: 5695
  • Status: open  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    This applies to CWM 1.1 (and also CWM 1.0).
    Sun MDR user Vincent Lombart spotted that he was getting the same
    association exported twice, which I tracked down to the following problem in
    the metamodel.

    There should be no explicit association between ClassifierMap and
    TransformationMap: the diagram in the CWM spec just documents the fact that
    the inherited ownedElement association is used to link these classes.
    The CWM XMI file is produced by the Unisys Rose integration which explicitly
    ignores such associations (signalled by '/' on the association ends - normal
    derived associations have '/' on the association name). This is used in
    several places e.g. in Relational model to show that Column and ColumnSet
    are linked using the owner-feature association.

    However in the ClassifierMap case there are also corresponding references
    explicitly defined as pseudo-attributes on Classifier and TransformationMap
    which has caused the references erroneously to be generated into the XMI
    file.

    On further investigation, the following inherited associations have
    superfluous references:

    XML:ElementType <-> XML:Schema
    XML:ElementType <-> XML:Attribute
    Transformation:TransformationMap <-> Transformation:ClasifierMap
    Transformation:TransformationActivity <-> TransformationStep (in this case
    the references are called 'step' and 'activity')
    BusinessNomenclature:Taxonomy <-> Concept
    BusinessNomenclature:Glossary <-> Term
    BusinessNomenclature:BusinessDomain <-> Taxonomy (in this case one
    reference is called just 'domain')

    Proposed resolution:
    Delete the above references/pseudo-attributes (with stereotype of
    <<reference>> though this is hidden on the diagram).

  • Reported: CWM 1.1 — Wed, 23 Oct 2002 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

Support the full set of 11404 aggregates.

  • Key: CWM12-3
  • Legacy Issue Number: 12340
  • Status: open  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    The full set of 11404 aggregates (record, array, set, bag, sequence, etc.) should be supported.
    Proposed Solution:
    Support the full set of 11404 aggregates.

  • Reported: CWM 1.1 — Wed, 19 Mar 2008 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

Location: 10.2.4 Structured Types and Object Extension , Figure 10.5

  • Key: CWM12-31
  • Legacy Issue Number: 12311
  • Status: open  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    Nature of Problem:
    The figure does not enclose emp_t in parenthesis (..) as shown correctly in the associated text.
    Proposed Solution: None proposed by source

  • Reported: CWM 1.1 — Wed, 19 Mar 2008 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

Annex D: Legal Information

  • Key: CWM12-12
  • Legacy Issue Number: 12330
  • Status: open  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    This normative annex appears to conflict with the intellectual property rights of ISO standards, and does not take account of the ISO requirement that all potential patents should be declared.
    Proposed Solution: None proposed by source

  • Reported: CWM 1.1 — Wed, 19 Mar 2008 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

Location: 10.2.6 Index

  • Key: CWM12-30
  • Legacy Issue Number: 12312
  • Status: open  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    Nature of Problem:
    This should make it clear that indexing is not part of SQL, and the use of SQLIndex in Figure 10.10 is entirely inappropriate.
    Proposed Solution: None proposed by source

  • Reported: CWM 1.1 — Wed, 19 Mar 2008 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

Location: 10.1 Overview

  • Key: CWM12-33
  • Legacy Issue Number: 12308
  • Status: open  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    Nature of Problem:
    The referenced [SQL], the basis of this clause, is given as SQL:1999, which is no longer valid because it has been superseded by SQL:2003
    Proposed Solution: None proposed by source

  • Reported: CWM 1.1 — Wed, 19 Mar 2008 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

We only need one COBOL Data Division metamodel.

  • Key: CWM12-51
  • Legacy Issue Number: 4744
  • Status: open  
  • Source: International Business Machines ( Dan Chang)
  • Summary:

    CWM vol. 2 3.1 says "The concepts and ideas implicit in the definition of the COBOL language's DATA DIVISION were one of the earliest (if not the first) formalizations of the ubiquitous record model. A COBOL program contains much more than just record descriptions. However, because neither CWM nor UML attempt to describe programming languages directly, only the DATA DIVISION is described here. The model presented here is compliant to the COBOL 85 language standard [COBOL]."

    UML Profile for EAI 14.1 says "The goal of this COBOL model is to capture the information that would be found in the Data Division." .

    Both define COBOL Data Division metamodels with different levels of detail. We only need one COBOL Data Division metamodel.

  • Reported: CWM 1.1 — Tue, 11 Dec 2001 05:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

10.4.2 ColumnRefStructuredType

  • Key: CWM12-19
  • Legacy Issue Number: 12321
  • Status: open  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    Nature of Problem:
    see comment on 10.3.20
    Proposed Solution: None proposed by source

  • Reported: CWM 1.1 — Wed, 19 Mar 2008 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

Annex C: Glossary

  • Key: CWM12-13
  • Legacy Issue Number: 12329
  • Status: open  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    This annex should not be described as Normative, since it does not provide any requirement on the application of this standard as well as being incomplete and missing or being in conflict with the terminology of other normative references, such as SQL. The reference to RM-ODP is inappropriate, not being one of the listed sources.
    Proposed Solution: None proposed by source

  • Reported: CWM 1.1 — Wed, 19 Mar 2008 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

13.1 Overview

  • Key: CWM12-18
  • Legacy Issue Number: 12323
  • Status: open  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    "XML Schema is an ongoing activity in the W3C. As future standards are adopted by the W3C on XML Schema, this package will be revised and extended accordingly." This document is not referenced in either Clause 3 or the References Annex, and the claimed revision has clearly not occurred.
    Proposed Solution: None proposed by source

  • Reported: CWM 1.1 — Wed, 19 Mar 2008 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

Location: 10.3.15 SQLDistinctType

  • Key: CWM12-29
  • Legacy Issue Number: 12315
  • Status: open  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    The attributes length, precision and scale should not be present, because they are exactly the same as those for the related sqlSimpleType. What should be included are the methods that can be defined for distinct types.
    Proposed Solution: None proposed by source

  • Reported: CWM 1.1 — Wed, 19 Mar 2008 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

Location: 10.2.4 Structured Types and Object Extensions

  • Key: CWM12-32
  • Legacy Issue Number: 12310
  • Status: open  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    Nature of Problem:
    "A structured type is defined in terms of columns" - the SQL standard defines a structured type in terms of attributes and it is totally confusing to define it in terms of columns. A column can exist only within tables and can have constraints, which are not allowed for attributes of a structured type.
    Proposed Solution: None proposed by source

  • Reported: CWM 1.1 — Wed, 19 Mar 2008 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

Parameter

  • Key: CWM12-46
  • Legacy Issue Number: 5921
  • Status: open  
  • Source: HTL Villach ( Lassnig Gernot)
  • Summary:

    I think a parameter must have a multiplicity, because otherwise there can be never ever overgiven/returned an array to/from an behavioralfeature. I think this is not correct, i think maybe this is right for input parameters, but i think for output or return parameters there must be an multiplicity to model an behavioralfeauture correct.

  • Reported: CWM 1.1 — Tue, 29 Apr 2003 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

Location: 10.1 Overview

  • Key: CWM12-35
  • Legacy Issue Number: 12309
  • Status: open  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    Nature of Problem:
    The inclusion of 'indexing' as part of Relational implies that it is part of SQL, but this is not true.

  • Reported: CWM 1.1 — Wed, 19 Mar 2008 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

Location: 3 Normative References - ISO/IEC 9075:2003 Database language SQL

  • Key: CWM12-37
  • Legacy Issue Number: 12302
  • Status: open  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    Nature of Problem:
    A normative reference for ISO/IEC 9075:2003 Database language SQL is required, because it is the basis of Clause 10 (any previous edition has been superseded)
    Proposed Solution: None proposed by source

  • Reported: CWM 1.1 — Wed, 19 Mar 2008 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

10.3.20 SQLStructuredType

  • Key: CWM12-23
  • Legacy Issue Number: 12319
  • Status: open  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    An essential feature of SQL structured types is that they have methods, whose properties should be recorded
    Proposed Solution: None proposed by source

  • Reported: CWM 1.1 — Wed, 19 Mar 2008 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

page 9-276/Section: 9.3.22 of ptc/2002-01-02 -- CWM issue

  • Key: CWM12-49
  • Legacy Issue Number: 5299
  • Status: open  
  • Source: International Business Machines ( Jean-Jacques Daudenarde)
  • Summary:

    Table: this currently reference a Table. However, most RDBMS support "instead of" triggers which can be applied to views. Table should be replaced by a reference to a NamedColumnSet

  • Reported: CWM 1.1 — Thu, 16 May 2002 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

Add datatype generators

  • Key: CWM12-4
  • Legacy Issue Number: 12337
  • Status: open  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    The 11404 datatype generator features should be included via the expressions metamodel capability.
    Proposed Solution:
    Add datatype generators

  • Reported: CWM 1.1 — Wed, 19 Mar 2008 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

Add syntax type to the metamodel.

  • Key: CWM12-8
  • Legacy Issue Number: 12336
  • Status: open  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    The expressions metamodel should have the kind of syntax associated the expression (e.g., is the expression C, APL, ksh, or something else, which all have significantly different parsing and syntax.
    Proposed Solution:
    Add the syntax type to the metamodel.

  • Reported: CWM 1.1 — Wed, 19 Mar 2008 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

value "name" attribute of ModelElement

  • Key: CWM12-6
  • Legacy Issue Number: 12333
  • Status: open  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    There is no requirement that the value "name" attribute of ModelElement correspond to the identifier (i.e., the string) of the model element.
    Proposed Solution:
    Add requirement that the "name" actually corresponds to the identifier of the model element.

  • Reported: CWM 1.1 — Wed, 19 Mar 2008 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

Annex B: Compatibility with other Standards

  • Key: CWM12-15
  • Legacy Issue Number: 12328
  • Status: open  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    This annex is inappropriate in this standard, but if it remains it must be non-normative because it does not provide any requirement on the application of this standard.
    Proposed Solution: None proposed by source

  • Reported: CWM 1.1 — Wed, 19 Mar 2008 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

Location: 4 Abbreviations and Conventions - SQL

  • Key: CWM12-36
  • Legacy Issue Number: 12306
  • Status: open  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    Nature of Problem:
    SQL should not be considered as an abbreviation for Structured Query Language
    Proposed Solution: None proposed by source

  • Reported: CWM 1.1 — Wed, 19 Mar 2008 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

Location: 4 Abbreviations and Conventions

  • Key: CWM12-40
  • Legacy Issue Number: 12303
  • Status: open  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    Nature of Problem:
    DTD is Document Type Definition
    Proposed Solution: None proposed by source

  • Reported: CWM 1.1 — Wed, 19 Mar 2008 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

Foreword

  • Key: CWM12-44
  • Legacy Issue Number: 12298
  • Status: open  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    Nature of Problem:
    "Apart from this Foreword, the text of this International Standard is identical with that for the OMG specification for CWM 1.1 (formal/03-03-02)."
    While true of the current document this cannot hold if changes are made to respond to NB comments.
    Proposed Solution: None proposed by source

  • Reported: CWM 1.1 — Wed, 19 Mar 2008 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

formal/03-03-02

  • Key: CWM12-43
  • Legacy Issue Number: 8707
  • Status: open  
  • Source: btinternet.com ( Bryan Wood)
  • Summary:

    The specification does not identify the exact versions of MOF, UML and XMI that it refers to. Even if more than one version is applicable this needs to be made clear.

  • Reported: CWM 1.1 — Thu, 28 Apr 2005 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

5.4 datatype attributes don't incorporate the features of 11404 datatype

  • Key: CWM12-10
  • Legacy Issue Number: 12335
  • Status: open  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    The datatype attributes don't incorporate the features of 11404 datatype (properties, characterizing operations, value spaces). There is no way to record this kind of standard datatyping information in CWM in a standard way.
    Proposed Solution:
    Add these features to the metamodel. Describe, in a standard way, how datatype characterizing operations would be recorded.

  • Reported: CWM 1.1 — Wed, 19 Mar 2008 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

10.3.17 SQLIndexColumn

  • Key: CWM12-25
  • Legacy Issue Number: 12317
  • Status: open  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    Nature of Problem:
    see comment on 10.2.6
    Proposed Solution: None proposed by source

  • Reported: CWM 1.1 — Wed, 19 Mar 2008 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

Location: 10.3.14 SQLDataType

  • Key: CWM12-28
  • Legacy Issue Number: 12314
  • Status: open  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    The attribute typeNumber is not an SQL concept, and since it is described as being assigned by the owning DBMS this makes it totally useless for any exchange between different DBMSs.
    Proposed Solution: None proposed by source

  • Reported: CWM 1.1 — Wed, 19 Mar 2008 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT