Docstoc

SubCommittee Name

Document Sample
SubCommittee Name Powered By Docstoc
					                                                  ISO/IEC JTC 1/SC 32 N 1849
                                                                                Date: 2009-03-10
                                                                              REPLACES:______



                                      ISO/IEC JTC 1/SC 32

                            Data Management and Interchange

                        Secretariat: United States of America (ANSI)
                      Administered by Farance Inc. on behalf of ANSI



DOCUMENT TYPE              Disposition of Comments
TITLE                      Disposition of comments in 32N1668 Summary of Voting on FCD2 19763-2
                           Information technology - Metamodel framework for interoperability (MFI) Part 4:
                           Metamodel for model mapping
SOURCE                     WG2 - Masaharu Obayashi & Doo-Kwon Baik - project editors
PROJECT NUMBER             1.32.22.01.02.00
STATUS                     Disposition of comments in SoV 32N1668 (comments on FCD2 19763-2 ballot
                           32N1591). This accompanies FCD3 19763-2 sent to NBs for 4 month letter
                           ballot
REFERENCES
ACTION ID.                 FYI
REQUESTED
ACTION
DUE DATE
Number of Pages            23
LANGUAGE USED              English
DISTRIBUTION               P & L Members
                           SC Chair
                           WG Conveners and Secretaries

Dr. Timothy Schoechle, Secretary, ISO/IEC JTC 1/SC 32
Farance Inc *, 3066 Sixth Street, Boulder, CO, United States of America
Telephone: +1 303-443-5490; E-mail: Timothy@Schoechle.org
available from the JTC 1/SC 32 WebSite http://www.jtc1sc32.org/
*Farance Inc. administers the ISO/IEC JTC 1/SC 32 Secretariat on behalf of ANSI
Template for comments and secretariat observations                                                                         Date: 09-02-27                    Document: ISO/IEC FCD2 19763-2


    1             2               (3)              4                                       5                                                           (6)                                            (7)

MB1          Clause No./     Paragraph/          Type           Comment (justification for change) by the MB                            Proposed change by the MB                          Secretariat observations
              Subclause     Figure/Table          of                                                                                                                                       on each comment submitted
                 No./           /Note            com-
                Annex       (e.g. Table 1)       ment2
               (e.g. 3.1)



    RESOLUTION OF COMMENTS FROM FCD2 19763-2

Template for comments and secretariat observations                                                                         Date: 2007-12-05                  Document: ISO/IEC FCD2 19763-2
1        2                  (3)              4           5                                                                 (6)                                                         (7)
MB1      Clause No./        Paragraph/       Type of     Comment (justification for change) by the MB                      Proposed change by the MB                                   Secretariat observations
         Subclause No./     Figure/Table/    com-                                                                                                                                      on each comment submitted
         Annex              Note             ment2
         (e.g. 3.1)         (e.g. Table 1)
CA       2                  11179-3          ed          FCD2 19763-2 is dependent on features specified in Edition 2 of   Specify ISO/IEC 11179-3:2003.                               Accepted
01                                                       11179-3, which may change in Edition 3. Therefore, the specific   Add 'and basic attributes' after 'Registry metamodel'       COMPLETE
                                                         edition should be cited. Also, the cited name is incomplete.
CA       2                  11179-6          ed          FCD2 19763-2 is dependent on features specified in Edition 2 of   Specify ISO/IEC 11179-6:2005                                Accepted
02                                                       11179-6, which may change in a future Edition.                                                                                COMPLETE
CA       2                  new              ed          The document uses terms from ISO/IEC 19501:2005 UML in a          Add a reference to:                                         Accepted
03                                                       normative way, but does not list it in the Normative references                                                               COMPLETE
                                                                                                                           ISO/IEC 19501:2005 Information technology -- Open
                                                                                                                           Distributed Processing -- Unified Modeling Language
                                                                                                                           (UML) Version 1.4.2
CA       2                  new              ed          The document uses terms from ISO/IEC 19502:2005 MOF in a          Add a reference to:                                         Accepted
04                                                       normative way, but does not list it in the Normative references   ISO/IEC 19502:2005 Information technology -- Meta           COMPLETE
                                                                                                                           Object Facility (MOF)
CA       3.2.18             definition       ed          'specifining' should be 'specifying'                              Change 'specifining' to 'specifying'                        Accepted
05                                                                                                                                                                                     COMPLETE
CA       3.2.20             definition       ed          'contex' should be 'context'                                      Change 'contex' to 'context'                                Accepted
06                                                                                                                                                                                     COMPLETE
CA       4                  data model       ge/te       We are still validating the data model, but wish to reserve the   We will submit detailed comments to the ballot resolution   -
07                                                       right to submit detailed comments later.                          meeting in Korea, or sooner if possible.

CA       4.1.3              Figure3          ed          Correct spelling to „MFI‟                                         YOW:ACCEPTED                                                Accepted
08                                                                                                                                                                                     COMPLETE
CA       4.2.3                               ed          “A conceputalization type specifies the association between       YOW:ACCEPTED                                                Accepted

    1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)
    2 Type of comment: ge = general         te = technical   ed = editorial
    NOTE   Columns 1, 2, 4, 5 are compulsory.
                                                                                                                                                                                                            page 1 of 24
    ISO electronic balloting commenting template/version 2001-10
Template for comments and secretariat observations                                                                   Date: 09-02-27                     Document: ISO/IEC FCD2 19763-2


 1            2                (3)             4                                    5                                                             (6)                                        (7)

MB1     Clause No./       Paragraph/       Type           Comment (justification for change) by the MB                            Proposed change by the MB                       Secretariat observations
         Subclause       Figure/Table       of                                                                                                                                    on each comment submitted
            No./             /Note         com-
           Annex         (e.g. Table 1)    ment2
          (e.g. 3.1)


09                                                 ModelClassifier and ModelComponent.”                                                                                       COMPLETE
                                                   Correct spelling to „conceptualization‟
CA    4.2.3              (2)                       “A conceptualization type defines the type of association that    YOW-ACCEPTED - Change to 1:1 keep sentence same          Accepted
10                       conceptualiz              exists between the contained ModelComponents and the                                                                       COMPLETE
                         ation type                ModelClassifier represented by the “conceputalized
                                                   by“ ModelConcept. “
                                                   DEFFRRED Because there is no guaranteed path to
                                                   ModelClassifier, change ModelConcept classified by
                                                   ModelClassifier constraint to 1..1 .
                                                   Sentence should read … A conceptualization type defines the
                                                   type of association that exists between the contained
                                                   ModelComponenents and the ModelClassifier
CA    4.2.3              (2)              te       “A code identifying the type of ModelComponent.”                  YOW:ACCEPTED …in the component set                       Accepted
11                       component                 DEFERRED Should this be ComponentSet as in figure                 (Editor‟s Note)                                          COMPLETE
                         type
                                                                                                                     In the ModelComponentSet
CA    4.2.3              (2)              te       “The some candidates of component type are listed in table G.1    YOW:ACCEPTED - sentence now reads…Component              Accepted
12                       component                 of Annex G.”                                                      types are listed in Table G.2 of Annex G                 COMPLETE
                         type                      Delete “the”
CA    4.2.3              (2)              te       “The some candidates of component type are listed in table G.1    YOW-see CA12 resolution                                  Accepted
13                       component                 of Annex G.”                                                                                                               COMPLETE
                         type                      Codes are in G3
CA    4.2.3              (3)              te       “ModelConcept [0..1], Mandatory”                                                                                           Accepted
14                       conceputaliz              ACCEPTED [1] in figure 4                                                                                                   COMPLETE
                         ed by
CA    4.2.3              (4)              te       “ModelComponentSet should be a set of ModelComponents             YOW: will not apply after rewording                      -
15                                                 derived from the ModelClassifier that is referenced by the        see CA66
                                                   “conceputalized by“ ModelConcept.”
                                                   DEFERRED Change referenced by to Classified by
CA    4.2.3              (4)              te       “A component type and its code system should be specified in      ACCEPTED. Note: change all occurrences of code           Accepted
16                                                 the corresponding ModelDomainProfile profiles.”                   system to code list.                                     COMPLETE
                                                   Change code system to Code List
CA    4.2.3              (4)              te       “A component type and its code system should be specified in      YOW: DEFERRED Need to revisit the model with Profile -   Accepted
 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)
 2 Type of comment: ge = general         te = technical   ed = editorial
 NOTE   Columns 1, 2, 4, 5 are compulsory.
                                                                                                                                                                                                   page 2 of 24
 ISO electronic balloting commenting template/version 2001-10
Template for comments and secretariat observations                                                                    Date: 09-02-27                    Document: ISO/IEC FCD2 19763-2


 1            2               (3)              4                                    5                                                             (6)                                           (7)

MB1     Clause No./       Paragraph/       Type           Comment (justification for change) by the MB                              Proposed change by the MB                        Secretariat observations
         Subclause       Figure/Table       of                                                                                                                                       on each comment submitted
            No./             /Note         com-
           Annex         (e.g. Table 1)    ment2
          (e.g. 3.1)


17                                                 the corresponding ModelDomainProfile profiles.”                    concept - component set - component path and alternate        COMPLETE
                                                   DEFERRED Model Domain Profile does not have a code list…           Profile - component to correspond with the chronology of
                                                                                                                      steps.
                                                   the meaning of this sentence is not clear
                                                                                                                      Also, identified requirement for a component type attribute
                                                                                                                      for ModelComponent.
                                                                                                                      (Editor‟s Note)
                                                                                                                      Rewording..
                                                                                                                      “A component type and its code list should be provided in
                                                                                                                      the out of this part of ISO/IEC 19763.”


                                                                                                                      Adding..
                                                                                                                      4.2.3ModelCompnentSet(ModelInstances)
                                                                                                                      “NOTE A ModelComponentSet may be conceptualized
                                                                                                                      independently by a ModelConcept. The ModelComponent
                                                                                                                      in the ModelCompnentSet is enforced to be classified by
                                                                                                                      the ModelClassifier.”
                                                                                                                      (4)constraints
                                                                                                                      -The component type of a ModelComponent in a
                                                                                                                      ModelComponentSet shall be same component type or its
                                                                                                                      subtype of one in the ModelComponentSet.

                                                                                                                      Adding
                                                                                                                      4.3.6ModelComponent
                                                                                                                      (2) Attributes
                                                                                                                      1. component type: typeCode[1..1]
                                                                                                                      -Use: Mandatory
                                                                                                                      -Description: A code identifying the type of
                                                                                                                      ModelComponent.


CA    4.2.4                               te       “In the core MFI model, ModelSelection is a metaclass that holds   YOW: DEFERRED – Need to examine other like                    Accepted
18                                                 a condition. “                                                     statements with a must-have vs. may-have meaning in           COMPLETE
                                                   May hold a condition because it is optional in the figure?         the sentence vis-a-vis as shown in the diagrams, because
                                                                                                                      as per the standard, the text takes precedence over the

 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)
 2 Type of comment: ge = general         te = technical   ed = editorial
 NOTE   Columns 1, 2, 4, 5 are compulsory.
                                                                                                                                                                                                      page 3 of 24
 ISO electronic balloting commenting template/version 2001-10
Template for comments and secretariat observations                                                                   Date: 09-02-27                     Document: ISO/IEC FCD2 19763-2


 1           2                (3)            4                                    5                                                               (6)                                       (7)

MB1     Clause No./       Paragraph/      Type            Comment (justification for change) by the MB                            Proposed change by the MB                      Secretariat observations
         Subclause       Figure/Table      of                                                                                                                                    on each comment submitted
            No./             /Note        com-
           Annex         (e.g. Table 1)   ment2
          (e.g. 3.1)


                                                                                                                     diagram rules.
                                                                                                                     SEE CA26
                                                                                                                     (Editor‟s Note)
                                                                                                                     4.2.1ModelSign
                                                                                                                     In the core MFI model, ModelSign is a metaclass that
                                                                                                                     holds (1..1,Mandatory: shall hold)a sign and a namespace
                                                                                                                     where the sign is unique within the namespace.
                                                                                                                     ModelSign instances each identify a thing of interest,
                                                                                                                     such as a package, class, or association. A ModelSign is
                                                                                                                     specified by (1..1,Mandatory: shall designates)the
                                                                                                                     associated ModelConcept and may express (0..*: may
                                                                                                                     express)multiple ModelSelections. A ModelSign is an
                                                                                                                     Administered Item.


                                                                                                                     4.2.2ModelConcept
                                                                                                                     In the core MFI model, ModelConcept is a metaclass that
                                                                                                                     holds (1..1,Mandatory: shall hold)a model type. A
                                                                                                                     ModelConcept is specified by (1..1,Maandatory: shall be
                                                                                                                     specified by )ModelDomainProfile and may be classified
                                                                                                                     by (0..1,Optional:may be classified by)a ModelClassifier.
                                                                                                                     A ModelConcept is an Administered Item.
                                                                                                                     ModelConcept associates the concept that is classified by
                                                                                                                     a ModelClassifier with the context that is specified by a
                                                                                                                     ModelDomainProfile.


                                                                                                                     4.2.3ModelCompnentSet
                                                                                                                     In the core MFI model, ModelComponentSet is a
                                                                                                                     metaclass that holds (1..1,Mandatory:shall hold)a
                                                                                                                     conceptualization type, a component type and its format.
                                                                                                                     A ModelCoponentSet is conceptualized
                                                                                                                     by(1..1,Mandatory: shall be conceptualized) a
                                                                                                                     ModelConcept and has (0..*,Mandatory: shall have)a set
                                                                                                                     of ModelComponents.
                                                                                                                     A ModelComponentSet is a referent of ModelConcept

 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)
 2 Type of comment: ge = general         te = technical   ed = editorial
 NOTE   Columns 1, 2, 4, 5 are compulsory.
                                                                                                                                                                                                  page 4 of 24
 ISO electronic balloting commenting template/version 2001-10
Template for comments and secretariat observations                                                                   Date: 09-02-27                     Document: ISO/IEC FCD2 19763-2


 1           2                (3)            4                                    5                                                               (6)                                       (7)

MB1     Clause No./       Paragraph/      Type            Comment (justification for change) by the MB                            Proposed change by the MB                      Secretariat observations
         Subclause       Figure/Table      of                                                                                                                                    on each comment submitted
            No./             /Note        com-
           Annex         (e.g. Table 1)   ment2
          (e.g. 3.1)


                                                                                                                     designated by a ModelSign and classified by a
                                                                                                                     ModelClassifier. A conceptualization type specifies the
                                                                                                                     association between ModelClassifier and
                                                                                                                     ModelComponent. A ModelComponentSet is an
                                                                                                                     Administered Item.
                                                                                                                     (Adding)
                                                                                                                     NOTE A ModelComponentSet may be conceptualized
                                                                                                                     independently by a ModelConcept. The ModelComponent
                                                                                                                     in the ModelCompnentSet is enforced to be classified by
                                                                                                                     the ModelClassifier.


                                                                                                                     4.2.4ModelSelection
                                                                                                                     In the core MFI model, ModelSelection is a metaclass that
                                                                                                                     holds(1..1,Optional:may hold) a condition. A
                                                                                                                     ModelSelection selects(1..1,Mandatory:shall select) a
                                                                                                                     modelComponentSet and is expressed by(1..1,Mandatory;
                                                                                                                     shall is expressed by) a ModelSign. A ModelSelection
                                                                                                                     relates a ModelSign to a ModelComponentSet.
                                                                                                                     A subset of ModelComponentSet may be retrieved using
                                                                                                                     the condition in ModelSelection from the
                                                                                                                     ModelComponentSet. A ModelComponent may include
                                                                                                                     other ModelSelections as a sub component by external
                                                                                                                     reference (see 4.3.6). A ModelSelection is an
                                                                                                                     Administered Item.


                                                                                                                     4.3.1ModelDomainProfile
                                                                                                                     In the core MFI model, ModelDomainProfile is a metaclass
                                                                                                                     that holds(1..1,Mandatory; shall hold) a name and
                                                                                                                     (0..*,Optional: may hold)a conformance where the
                                                                                                                     named domain profile has the conformance statements. A
                                                                                                                     ModelDomainProfile is described by(0..*,Optional; may be
                                                                                                                     secribed by) ModelSpecifications and
                                                                                                                     consists(0..*,Optional: may consist) of ModelComponents
                                                                                                                     and is specified by(0..*,Optional; may be specified by)
                                                                                                                     the associated ModelByMOF. A ModelDomainProfile is an
                                                                                                                     Administered Item.
 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)
 2 Type of comment: ge = general         te = technical   ed = editorial
 NOTE   Columns 1, 2, 4, 5 are compulsory.
                                                                                                                                                                                                  page 5 of 24
 ISO electronic balloting commenting template/version 2001-10
Template for comments and secretariat observations                                                                   Date: 09-02-27                     Document: ISO/IEC FCD2 19763-2


 1           2                (3)            4                                    5                                                               (6)                                        (7)

MB1     Clause No./       Paragraph/      Type            Comment (justification for change) by the MB                            Proposed change by the MB                       Secretariat observations
         Subclause       Figure/Table      of                                                                                                                                     on each comment submitted
            No./             /Note        com-
           Annex         (e.g. Table 1)   ment2
          (e.g. 3.1)




                                                                                                                     4.3.2ModelSpecification
                                                                                                                     In the core MFI model, ModelSpecification is a metaclass
                                                                                                                     that holds metadata on human-readable documents
                                                                                                                     concerning a standard or its related profile. A
                                                                                                                     ModelSpecification may include the document for
                                                                                                                     ModelByMOF and ModelComponent.


                                                                                                                     4.3.3Modelconstruct
                                                                                                                      (This is removed by refining the core model, see B291))
                                                                                                                     In the core MFI model, ModelConstruct is a metaclass
                                                                                                                     representing a set of NamedElements in UML. A
                                                                                                                     ModelConstruct shall have(1..*,Optional; may have)
                                                                                                                     named elements such as pattern (template), stereotype
                                                                                                                     (tagged value), coded value and constraint.

                                                                                                                     4.3.4ModelClassifier
                                                                                                                     In the core MFI model, ModelClassifier is a metaclass that
                                                                                                                     holds(1..1,Optional;may hold) a model type, a usage
                                                                                                                     type, an xmi text, an attachment type and an attachment.
                                                                                                                     A ModelClassifier is identifying ModelConstruct and typed
                                                                                                                     model as a concept. A ModelClassifier is
                                                                                                                     defined(0..1,Optional; may be defined) with UML by a
                                                                                                                     ModelByMOF.


                                                                                                                     4.3.5ModelByMOF
                                                                                                                     In the core MFI model, ModelByMOF is a metaclass that
                                                                                                                     holds(1..1,Mandatory; shall hold) a model layer level, an
                                                                                                                     isMOFcompiliant and a MOFversion. A ModelByMOF may
                                                                                                                     have (0..1,Mandatory; shall have) a PackagedObject
                                                                                                                     using UML.


                                                                                                                     4.3.6ModelComponent
                                                                                                                     In the core MFI model, ModelComponent is a metaclass
 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)
 2 Type of comment: ge = general         te = technical   ed = editorial
 NOTE   Columns 1, 2, 4, 5 are compulsory.
                                                                                                                                                                                                   page 6 of 24
 ISO electronic balloting commenting template/version 2001-10
Template for comments and secretariat observations                                                                   Date: 09-02-27                     Document: ISO/IEC FCD2 19763-2


 1           2                (3)            4                                    5                                                               (6)                                           (7)

MB1     Clause No./       Paragraph/      Type            Comment (justification for change) by the MB                            Proposed change by the MB                          Secretariat observations
         Subclause       Figure/Table      of                                                                                                                                        on each comment submitted
            No./             /Note        com-
           Annex         (e.g. Table 1)   ment2
          (e.g. 3.1)


                                                                                                                     that holds(1..1,Mandatory; shall hold) component type. A
                                                                                                                     ModelComponent has(0..*,Optional; may have)
                                                                                                                     ModelClassifiers and ModelSelections that plays a role of
                                                                                                                     connecting external elements with like “plug and play”
                                                                                                                     manner. A ModelComponent is an Administered Item.
                                                                                                                     NOTE ModelComponent may have(0..*,Optional; may
                                                                                                                     have) some ModelClassifiers as model element.
                                                                                                                     Meanwhile, ModelComponent may be conceptualized
                                                                                                                     independently by the ModelConcept, which is classified by
                                                                                                                     another ModelClassifier.


                                                                                                                     4.4.1ModelAssociation
                                                                                                                     ModelAssociation is a metaclass specifying an association
                                                                                                                     among ModelClassifiers. A ModelAssociation defines a
                                                                                                                     classification for a set of links on ModelClassifier. A link,
                                                                                                                     which is an instance of ModelAssociation, is a connection
                                                                                                                     between object instances of a ModelClassifier.


                                                                                                                     4.4.2ModelAssociationEnd
                                                                                                                     ModelAssociationEnd is a metaclass designating two ends
                                                                                                                     of a ModelAssociation. Each ModelAssociationEnd defines
                                                                                                                     a role of a ModelConcept participant in the
                                                                                                                     ModelAssociation and constraints on sets of the
                                                                                                                     ModelConcepts.

                                                                                                                     (Editor‟s Note)
                                                                                                                     The packaging of MFI-2 core model has been changed. In
                                                                                                                     WG2N1191 at Vilamoura version as follows.
                                                                                                                     ModelComponentSet
                                                                                                                     In the core MFI model, ModelComponentSet is a
                                                                                                                     metaclass that shall hold a component type and its
                                                                                                                     format. A ModelComponentSet shall have
                                                                                                                     ModelComponents as lower model. A
                                                                                                                     ModelComponentSet is an Administered Item.

                                                                                                                  ModelInstances
 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)
 2 Type of comment: ge = general         te = technical   ed = editorial
 NOTE   Columns 1, 2, 4, 5 are compulsory.
                                                                                                                                                                                                      page 7 of 24
 ISO electronic balloting commenting template/version 2001-10
Template for comments and secretariat observations                                                                   Date: 09-02-27                     Document: ISO/IEC FCD2 19763-2


 1            2                (3)             4                                     5                                                            (6)                                         (7)

MB1     Clause No./       Paragraph/       Type           Comment (justification for change) by the MB                            Proposed change by the MB                        Secretariat observations
         Subclause       Figure/Table       of                                                                                                                                     on each comment submitted
            No./             /Note         com-
           Annex         (e.g. Table 1)    ment2
          (e.g. 3.1)


                                                                                                                     In the core MFI model, ModelInstances is a metaclass
                                                                                                                     that shall hold a conceptualization type. A ModelInstances
                                                                                                                     shall be conceptualized by a ModelConcept and shall be
                                                                                                                     grouped by ModelComponentSets.

CA    4.2.4                               te       “ A ModelSelection is a link between a ModelSign and a            YOW: DEFERRED                                                Accepted
19                                                 ModelComponentSet.                                                                                                             COMPLETE
                                                   Is this statemengt necessary…what is “a link”?
                                                   Change to A ModelSelection relates a ModelSign to a
                                                   ModelComponentSet
CA    4.2.4                               ed       “A subset of ModelComponet may be retrieved with the condition    YOW: ACCEPTED                                                Accepted
20                                                 from the ModelComponentSet.”                                                                                                   COMPLETE
                                                   Change to „ModelComponent
CA    4.2.4                               te       “A subset of ModelComponet may be retrieved with the condition    YOW:DEFERRED                                                 Accepted
21                                                 from the ModelComponentSet.”                                      (Editor‟s Note)                                              COMPLETE
                                                   Are there selection criteria for condition?
                                                                                                                     Change to: A subset of ModelComponentSet may be
                                                   Change to: A subset of ModelComponent may be retrieved using      retrieved using the condition in ModelSelection from the
                                                   the condition in ModelSelection from the ModelComponentSet.       ModelComponentSet.
CA    4.2.4              (2)              te       “string [1..1]”                                                   YOW: DEFERRED                                                Accepted
22                       condition                 Models shows [0..1]. Make this [0..1]                             (Editor‟s Note)                                              COMPLETE
                                                                                                                     Mandatory / Optional attribute is missing
                                                                                                                     Add Optional as USE
CA    4.2.4              (2)              te       “A string specifing the condtion filtering for the                YOW:ACCEPTED                                                 Accepted
                                                   ModelComponentSet.”
23                       condition                                                                                                                                                COMPLETE
                                                   Specifying the filtering condition…
CA    4.3                Figure 5         te       “Figure 5- Target package in MFI Core”                            YOW: DEFERRED                                                Accepted
24                                                 The object classes common in Fig 4 and 5 should be consistently   (Editor‟s Note)                                              COMPLETE
                                                   defined. E.g. Fig 5 has ModelSelection references                 Add the NOTE under Figure 3.
                                                   ModelComponent but this association is missing in Fig 4, same
                                                   with ModelComponent has ModelClassifier.
                                                   Add in Note under Figure 3: The model diagrams in each of the
                                                   packages only portray the relevant associations as required for

 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)
 2 Type of comment: ge = general         te = technical   ed = editorial
 NOTE   Columns 1, 2, 4, 5 are compulsory.
                                                                                                                                                                                                    page 8 of 24
 ISO electronic balloting commenting template/version 2001-10
Template for comments and secretariat observations                                                                      Date: 09-02-27                  Document: ISO/IEC FCD2 19763-2


 1            2                (3)             4                                     5                                                            (6)                                    (7)

MB1     Clause No./       Paragraph/       Type           Comment (justification for change) by the MB                                Proposed change by the MB              Secretariat observations
         Subclause       Figure/Table       of                                                                                                                               on each comment submitted
            No./             /Note         com-
           Annex         (e.g. Table 1)    ment2
          (e.g. 3.1)


                                                   that particular package.
CA    4.3.1                               te       “In the core MFI model, ModelDomainProfile is a metaclass that                                                           Withdrawn
                                                   holds a name and a comformance where the named domain
25
                                                   profile has the conformance statements.”
                                                   WITHDRAWN.Reword to indicate optional conformance…‟holds
                                                   a name and any conformance statements where they exist.‟
CA    4.3.1                                        “A ModelDomainProfile is described by ModelSpecifications and        YOW: SEE CA 18
                                          te       consists of ModelComponents and is specified by the associated
26                                                 ModelByMOF using UML.”
                                                   Implies mandatory association, change „is specified‟ to „may be
                                                   specified‟
CA    4.3.1                               te       “A ModelDomainProfile is described by ModelSpecifications and        YOW: DEFERRED                                       Accepted
                                                   consists of ModelComponents and is specified by the associated
27                                                                                                                                                                          COMPLETE
                                                   ModelByMOF using UML.”
                                                   Where is „using UML implied?
                                                   Move „using UML‟ to the end of the sentence in para in 4.3.5
                                                   ModelByMOF
CA    4.3.1              (2)              te       “A string identifying the level of conformance defined in the        YOW: DEFERRED                                       Accepted
                         conformance               ModelSpecification.”
28                                                                                                                                                                          COMPLETE
                                                   Is this referring to conformance in ModelDomainProfile or the
                                                   conformance in ModelSpecification…
                                                   Reword to: A string identifying conformance in the
                                                   ModelDomainProfile relating to the conformance level in the
                                                   ModelSpecification.
                                                   Change the „conformance‟ attribute in 4.3.2 ModelSpecification
                                                   to : „conformance level‟
CA    4.3.1              (3)              te       “ModelSpecification [1..*], Optional”                                YOW: DEFERRED                                       Accepted
29                       described by              [1..*] Mandatory or as in Fig 5, [0..*] Optional. Change [1..*] to   (Editor‟s note.)                                    COMPLETE
                                                   [0..*]                                                               Change [1..*] to [0..*]
CA    4.3.1              (3)              te       “The ModelComponent that is the elements aggregated in the           YOW: DEFERRED                                       Accepted
                         consists of               ModelDomainProfile”                                                  (Editor‟s note.)
30                                                                                                                                                                          COMPLETE
                                                   …Reword: ‟The model components in ModelComponent that are            Reword:
 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)
 2 Type of comment: ge = general         te = technical   ed = editorial
 NOTE   Columns 1, 2, 4, 5 are compulsory.
                                                                                                                                                                                               page 9 of 24
 ISO electronic balloting commenting template/version 2001-10
Template for comments and secretariat observations                                                                       Date: 09-02-27                   Document: ISO/IEC FCD2 19763-2


 1            2                (3)             4                                     5                                                              (6)                                          (7)

MB1     Clause No./       Paragraph/       Type           Comment (justification for change) by the MB                                 Proposed change by the MB                      Secretariat observations
         Subclause       Figure/Table       of                                                                                                                                        on each comment submitted
            No./             /Note         com-
           Annex         (e.g. Table 1)    ment2
          (e.g. 3.1)


                                                   aggregated in the ModelDomainProfile                                  ‟The ModelComponents that are aggregated in the
                                                                                                                         ModelDomainProfile


CA    4.3.1              (4)              te       “The attribute „name‟ is not necessary to be a globally unique        YOW: ACCEPTED sentence should read….”not                    Accepted
                                                   identifier.”                                                          necessarily a globally unique identifier”
31                                                                                                                                                                                   COMPLETE
                                                   Change „necessary to be‟ to: „necessarily
CA    4.3.2              (2)              te       “string [1..1], Optional”                                             YOW: Relates to reformatting of descriptions to be listed   Accepted
                         source                                                                                          in named vertical order
32                                                 Mandatory---change throughout the document according to the                                                                       COMPLETE
                                                   usage of attribute as „mandatory attribute‟ or „optional attribute‟   (Editor‟s note.)
                                                                                                                         Reformatting as follows:
                                                                                                                         (2) Attributes
                                                                                                                         n. attribute name: datatype and multiplicity
                                                                                                                         -Use: Mandatory or Optional condition for attribute
                                                                                                                         -Description: description for content and purpose of
                                                                                                                         attribute
                                                                                                                         (3) References
                                                                                                                         n. reference name : Class name and multiplicity
                                                                                                                         -Use: Mandatory or Optional condition for reference
                                                                                                                         -Description: description for content and purpose of
                                                                                                                         reference


CA    4.3.2              (2)              te       “number[1..1], Optional”                                              YOW: Relates to reformatting of descriptions to be listed   Accepted
                         version                   Mandatory---see CA32                                                  in named vertical order
33                                                                                                                                                                                   COMPLETE
CA    4.3.2              (2)              te       “string [1..1], Optional”                                             YOW: Relates to reformatting of descriptions to be listed   Accepted
                         status                    Mandatory---see CA32                                                  in named vertical order
34                                                                                                                                                                                   COMPLETE
CA    4.3.2              (2)              te       “string [1..1], Optional”                                             YOW: Relates to reformatting of descriptions to be listed   Accepted
                         purpose                   Mandatory---see CA32                                                  in named vertical order
35                                                                                                                                                                                   COMPLETE
CA    4.3.2              (2)              te       “string [1..1], Optional”                                             YOW: Relates to reformatting of descriptions to be listed   Accepted

 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)
 2 Type of comment: ge = general         te = technical   ed = editorial
 NOTE   Columns 1, 2, 4, 5 are compulsory.
                                                                                                                                                                                                   page 10 of 24
 ISO electronic balloting commenting template/version 2001-10
Template for comments and secretariat observations                                                                     Date: 09-02-27                   Document: ISO/IEC FCD2 19763-2


 1            2                (3)             4                                    5                                                             (6)                                       (7)

MB1     Clause No./       Paragraph/       Type           Comment (justification for change) by the MB                               Proposed change by the MB                   Secretariat observations
         Subclause       Figure/Table       of                                                                                                                                   on each comment submitted
            No./             /Note         com-
           Annex         (e.g. Table 1)    ment2
          (e.g. 3.1)


36                       scope                     Mandatory---see CA32                                                in named vertical order                                  COMPLETE

CA    4.3.3                               te       “A ModelConstruct may have named elements such as pattern                                                                    Accepted
                                                   (template), stereotype (tagged value), coded value and
37                                                 constraint.”                                                                                                                 COMPLETE
                                                   ACCEPTED Figure shows mandatory?.
                                                   Change text to read…A ModelConstruct shall have named
                                                   elements …where exists.
CA    4.3.3              (2)              te       “NamedElement [0..*], Optional”                                                                                              Accepted
38                       has                       ACCEPTED Figure 5 shows mandatory...[1..*] .                                                                                 COMPLETE
                                                   Change text to 1..*]
CA    4.3.4                               ed       “In the core MFI model, ModelClassifier is a mataclass that holds                                                            Accepted
                                                   a model type, a usage type, an xmi text, an attachment type and
39                                                 an attachment.”                                                                                                              COMPLETE
                                                   ACCEPTED Change to metaclass
CA    4.3.4                               te       “A ModelClassifier is identifying modelling unit and typed model                                                             Accepted
                                                   as a concept.”
40                                                                                                                                                                              COMPLETE
                                                   ACCEPTED Missing - Where is this in the diagram?
                                                   Change „modelling unit‟ to „ModelConstruct‟
CA    4.3.4              (1)              te       “ModelConstructs”                                                                                                            Accepted
                         ModelConstr               ACCEPTED Not shown in any figure as a superclass in this
41                       ucts                                                                                                                                                   COMPLETE
                                                   standard. Change to ModelConstruct
CA    4.3.4              (2)              te       “type code [1..1] , Optional “                                                                                               Accepted
42                       model type                ACCEPTED. Mandatory in figure ---see CA32                                                                                    COMPLETE
CA    4.3.4              (2)              te       “type code [1..1], Optional”                                                                                                 Accepted
43                       usage type                ACCEPTED Mandatory in figure ---see CA32                                                                                     COMPLETE
CA    4.3.4              (2)              te       “A string specifying the file type of attachment format. For        (Editor‟s note.)                                         Accepted
                                                   example, ppt, pdf, http, and xls.”                                  Rewording:
44                       attachment                                                                                                                                             COMPLETE
                         type                      ACCEPTD Should not this be a predefined code list –
                                                                                                                       “A string specifying attachment data format. It may be
                                                   Add reference using MIME types, RFC2046; and change „http‟ to       described by media type of RFC2046.”
 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)
 2 Type of comment: ge = general         te = technical   ed = editorial
 NOTE   Columns 1, 2, 4, 5 are compulsory.
                                                                                                                                                                                              page 11 of 24
 ISO electronic balloting commenting template/version 2001-10
Template for comments and secretariat observations                                                                       Date: 09-02-27                   Document: ISO/IEC FCD2 19763-2


 1            2                (3)             4                                   5                                                                (6)                                        (7)

MB1     Clause No./       Paragraph/       Type             Comment (justification for change) by the MB                               Proposed change by the MB                    Secretariat observations
         Subclause       Figure/Table       of                                                                                                                                      on each comment submitted
            No./             /Note         com-
           Annex         (e.g. Table 1)    ment2
          (e.g. 3.1)


                                                   „html‟


CA    4.3.4              (2)              te       ACCEPTED Need a note constraint saying (attachment is null            (Editor‟s note.)                                          Accepted
                         attachment                and attachment type is null) or (attachment is not null and           Rewording:
45                                                 attachment type is not null)                                                                                                    COMPLETE
                                                                                                                         “The value of attachment shall exist if attachment type
                                                                                                                         exists or the value of attachment shall not exit if
                                                                                                                         attachment type does not exist.”
CA    4.3.4              (4)              te       “A ModelClassifier and its code system should be specified in         RESOLUTION: Add a constraint to denote the value of       Accepted
                                                   particular ModelDomainProfile profiles.”                              model type in ModelConcept and ModelClassifier shall be
46                                                                                                                       the same where both exist.                                COMPLETE
                                                   ACCEPTED There is no association path between model
                                                   classifier and model domain profile, unless the association is with
                                                   (“specified by”) ModelByMOF..change to „may be specified…‟.
CA    4.3.5                               ed       “An ModelByMOF mat have a PackagedObject.”                                                                                      Accepted
47                                                 ACCEPTED An should be A                                                                                                         COMPLETE
CA    4.3.5                               ed       “An ModelByMOF mat have a PackagedObject.”                                                                                      Accepted
48                                                 ACCEPTED. Change mat to may                                                                                                     COMPLETE
CA    4.3.5              (2)              te       “string [1..1], Optional”                                                                                                       Accepted
49                       MOFversion                ACCEPTED Mandatory---see CA32                                                                                                   COMPLETE
CA    4.3.5              (3)              te       “PackagedObject [0..1], Mandatory”                                                                                              Accepted
50                       has                       ACCEPTED Optional---see CA32                                                                                                    COMPLETE
CA    4.3.5              (3)              ed       “The PackagedObject representing a metamodel. A MOF                   YOW: DEFERRED                                             Accepted
                         has                       compliant model is recommended.”                                      (Editor‟s note.)
51                                                                                                                                                                                 COMPLETE
                                                   Reword …”represents..” ?                                              Rewording:
                                                                                                                         “A PackagedObject represents a metamodel or model.”




 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)
 2 Type of comment: ge = general         te = technical   ed = editorial
 NOTE   Columns 1, 2, 4, 5 are compulsory.
                                                                                                                                                                                                 page 12 of 24
 ISO electronic balloting commenting template/version 2001-10
Template for comments and secretariat observations                                                                     Date: 09-02-27                   Document: ISO/IEC FCD2 19763-2


 1            2                 (3)            4                                      5                                                           (6)                                         (7)

MB1     Clause No./       Paragraph/       Type           Comment (justification for change) by the MB                               Proposed change by the MB                     Secretariat observations
         Subclause       Figure/Table       of                                                                                                                                     on each comment submitted
            No./             /Note         com-
           Annex         (e.g. Table 1)    ment2
          (e.g. 3.1)


CA    4.3.6              NOTE             te       “!Meanwhile, ModelComponent may be conceptualized                   YOW: DEFERRED                                              (Note: Edited in WG2-N1097)
                                                   independently by the ModelConcept, which is classified by           (Editor‟s note.)
52                                                 another ModelClassifier.”                                                                                                      Accepted
                                                                                                                       Rewording and move it to 4.2.3 ModelComponentset;          COMPLETE
                                                   There is no association path…only path exists from
                                                   ModelComponentSet                                                   “NOTE A ModelComponentSet may be conceptualized
                                                                                                                       independently by a ModelConcept. The ModelComponent
                                                                                                                       in the ModelCompnentSet is enforced to be classified by
                                                                                                                       the ModelClassifier.”

                                                                                                                       SEE CA17
                                                                                                                       (Editor‟s note.)
                                                                                                                       Rewording again:
                                                                                                                       -binding constraint 1: A ModelInstances may be
                                                                                                                       conceptualized independently by a ModelConcept. The
                                                                                                                       ModelComponent in the ModelComponentSets of a
                                                                                                                       ModelInstances shall be enforced to be classified by the
                                                                                                                       ModelClassifier.


CA    4.3.6              (2)              te       “!ModelClassifier [1..*], Optional”                                 YOW: DEFERRED                                              Accepted
53                       has                       [0..*] Optional                                                     (Editor‟s note.)                                           COMPLETE
                                                                                                                       Change [1..*] to [0..*]
CA    4.3.6              (2)              ed       “The ModelSelection that is used in the ModelComponet and           YOW: ACCEPTED                                              Accepted
                         references                referes to registered ModelComponentSet”
54                                                                                                                                                                                COMPLETE
                                                   ModelComponent and refers…
CA    4.3.6              (3)              te       “ModelSelection should be used according to the                     YOW: DEFERRED                                              Accepted
                                                   ModelComponentSet that is pointed by the ModelSelection.”           (Editor‟s note.)
55                                                                                                                                                                                COMPLETE
                                                   change „be used according to…‟ to „ selects                         Rewording:
                                                   ModelComponentSet that is selected by ModelSelection…(Use
                                                   the predicates in the diagram)                                      “ModelComponent may reference ModelComponentSet
                                                                                                                       that is selected by the ModelSelection.”
CA    4.4.1              (2)              te       “ModelAssociationEnd [2..*], Mandatory”                             YOW: DEFERRED                                              Accepted
56                       ends                      is missing in Fig 6 if more than 2 or is it [2..2] (text says 2)?   (Editor‟s note.)                                           COMPLETE
                                                                                                                       Change [2..*] to [2..2]
 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)
 2 Type of comment: ge = general         te = technical   ed = editorial
 NOTE   Columns 1, 2, 4, 5 are compulsory.
                                                                                                                                                                                                page 13 of 24
 ISO electronic balloting commenting template/version 2001-10
Template for comments and secretariat observations                                                                   Date: 09-02-27                     Document: ISO/IEC FCD2 19763-2


 1            2                (3)             4                                  5                                                               (6)                                       (7)

MB1     Clause No./       Paragraph/       Type           Comment (justification for change) by the MB                             Proposed change by the MB                     Secretariat observations
         Subclause       Figure/Table       of                                                                                                                                   on each comment submitted
            No./             /Note         com-
           Annex         (e.g. Table 1)    ment2
          (e.g. 3.1)


CA    4.4.2                               ed       “ModelAssociationEnd is a metaclass designating two end of a      YOW: ACCEPTED                                              Accepted
                                                   ModelAssociation.”
57                                                                                                                                                                              COMPLETE
                                                   ends
CA    4.4.2              (2)name          te       String [1..1] , Optional                                          YOW: DEFERRED                                              Accepted
58                                                 [0..1] as in figure                                               (Editor‟s note.)                                           COMPLETE
                                                                                                                     Change [1..1] to [0..1]
CA    4.4.2              (2)annotation    te       String [1..1] , Optional                                          YOW: DEFERRED                                              Accepted
59                                                 [0..1] as in figure                                               (Editor‟s note.)                                           COMPLETE
                                                                                                                     Change [1..1] to [0..1]
CA    G.3                Table G.2        te       “Table G.2- Possible Example on Component Types”                  YOW: ACCEPTED                                              Accepted
60                                                 (YOW): Caption needs to be consistent with sentence above                                                                    COMPLETE
                                                   (candidates vs. examples).: YOW : Change caption to
                                                   “Candidate list for Component Type”
CA    G.3                                 te       “Table G.2 lists part of candidates of Component Type.”           YOW: ACCEPTED                                              Accepted
61                                                 (YOW): To make consistent with caption, reword sentence to                                                                   COMPLETE
                                                   :Table G.2 lists candidates for Component Type.
CA    G.3                Table G.2                  (YOW): should be “CoreComponent”                                 YOW: ACCEPTED                                              Accepted
                         1.2              ed
62                                                                                                                                                                              COMPLETE
CA    G.3                Table G.2                 (YOW): should be “RegistryRepository”                             YOW: ACCEPTED                                              Accepted
                         2.6              ed
63                                                                                                                                                                              COMPLETE
CA    G.3                Table G.2                 (YOW): should be CollaborationProtocol…(both lines 2.3 and 2.4    YOW: ACCEPTED                                              Accepted
                         2.4              ed       )”
64                                                                                                                                                                              COMPLETE

CA    4.2.3              (3)                       “conceputalized by”                                                                                                          Accepted
                         conceputaliz     ed       (YOW):
65                                                                                                                                                                              COMPLETE
                         ed by                     ACCEPTED should be “conceptualized..”
CA    4.2.3              (4)                       “ModelComponentSet should be a set of ModelComponents             YOW:DEFERRED - Either fix model or Reword to ensure        Accepted
                                          te       derived from the ModelClassifier that is referenced by the        triangulation anomaly cannot occur for model classifier.
66                                                 “conceputalized by“ ModelConcept.”                                                                                           COMPLETED
                                                                                                                     (Editor‟s note.)
 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)
 2 Type of comment: ge = general         te = technical   ed = editorial
 NOTE   Columns 1, 2, 4, 5 are compulsory.
                                                                                                                                                                                              page 14 of 24
 ISO electronic balloting commenting template/version 2001-10
Template for comments and secretariat observations                                                                     Date: 09-02-27                    Document: ISO/IEC FCD2 19763-2


 1             2              (3)              4                                    5                                                              (6)                                        (7)

MB1     Clause No./       Paragraph/       Type           Comment (justification for change) by the MB                               Proposed change by the MB                     Secretariat observations
         Subclause       Figure/Table       of                                                                                                                                     on each comment submitted
            No./             /Note         com-
           Annex         (e.g. Table 1)    ment2
          (e.g. 3.1)


                                                   (YOW):                                                              Rewording:
                                                   The model concept that conceptualizes the model component set       “The ModelConcept that conceptualizes the
                                                   is classified by the same model classifier that classifies the      ModelComponentSet shall be classified by the same
                                                   model components that comprise the model component set.             ModelClassifier that classifies the ModelComponents that
                                                                                                                       comprise the ModelComponentSet.”
                                                                                                                       (Editor‟s note.)
                                                                                                                       Rewording, again in ModelInstances
                                                                                                                       -binding constraint 1: A ModelInstances may be
                                                                                                                       conceptualized independently by a ModelConcept. The
                                                                                                                       ModelComponent in the ModelComponentSets of a
                                                                                                                       ModelInstances shall be enforced to be classified by the
                                                                                                                       ModelClassifier.




JP    3 Terms and                         ed       5.2.4 Paragraph, ISO/IEC Directives, Part 2, 2004 says              (Editor‟s note)                                            Accepted
      definitions                                  “”Hanging paragraphs” such as those shown in the following
01                                                                                                                     Wrap the hanging paragraph as sub clause 3.1 and           COMPLETE
                                                   example shall be avoided since reference to them is ambiguous.”     change following sub clause number as 3.2 and 3.3.
JP    3.1.37                              te       Two different definitions of “metamodel” are given.                 (Editor‟s note)                                            Accepted
02    3.1.38                                       Both are different from the description of “metamodel” at 4.1.1.1   Delete 3.1.38                                              COMPLETE
                                                   .
                                                   Only one definition which can be applied for this standard shall
                                                   be given.
JP    3.1.55                              te       Two different definitions of “reference pointer” are given.         (Editor‟s note)                                            Accepted
03    3.1.56                                       Only one definition which can be applied for this standard shall    Delete 3.1.55                                              COMPLETE
                                                   be given.
JP    4.1.1                               te       The sentence “In this document, the term “metamodel” is used        (Editor‟s note)                                            Withdrawn
                                                   broadly to include both models and metamodels.” contradicts         Adding the note in the term definition.
04                                                 both definitions 3.1.37 and 3.1.38.
                                                                                                                       NOTE 1      In this document, the term “metamodel” is
                                                                                                                       used broadly to include both models and metamodels.



 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)
 2 Type of comment: ge = general         te = technical   ed = editorial
 NOTE   Columns 1, 2, 4, 5 are compulsory.
                                                                                                                                                                                                page 15 of 24
 ISO electronic balloting commenting template/version 2001-10
Template for comments and secretariat observations                                                                          Date: 09-02-27                   Document: ISO/IEC FCD2 19763-2


 1            2               (3)              4                                      5                                                                (6)                                         (7)

MB1     Clause No./       Paragraph/       Type           Comment (justification for change) by the MB                                   Proposed change by the MB                      Secretariat observations
         Subclause       Figure/Table       of                                                                                                                                          on each comment submitted
            No./             /Note         com-
           Annex         (e.g. Table 1)    ment2
          (e.g. 3.1)


JP    4.1.2                               te       Cardinality should be multiplicity according to the definition                                                                      Accepted
05                                                 3.1.9 cardinality and 3.1.44 multiplicity                                                                                           COMPLETE

JP    4.1.1.2.2                           te       To describe the relationship between MFI part3 and ODM is out            (Editor‟s note)                                            Accepted
                                                   of the scope of MFI part2.                                               Deleted
06                                                                                                                                                                                     COMPLETE

JP    Figure2                             te       “M2 or M1 Layer” does not make sense. According to this figure,                                                                     Withdrawn
                                                   Target Models lie on M2 Layer, which seems strange because
07                                                 usually Target Models lie on M1 Layer.
JP    4.2.3                               te       The name „ModelInstances‟ should not be changed since it is              NY: ACCEPTED                                               Accepted
      ModelCompone                                 cited in ISO/IEC19763-1 and ISO/IEC 19763-3.                             YOW:DEFERRED
08    tSet                                                                                                                                                                             COMPLETE
                                                   Moreover, The name “ModelComponentSet” is inappropriate                  (Editor‟s note)
                                                   since ModelDomainProfile also consists of ModelComponents
                                                   and the name “ModelComponentSet” does not reflect its                    Adding Model Instances in the Definition as synonym.
                                                   characteristics. Its name should reflect its characteristic that it is   3.3.22
                                                   covered by ModelConcept.
                                                                                                                            Model Component Set
                                                                                                                            Model Instances
                                                                                                                            metaclass for specifying the set of registered elements
                                                                                                                            4.2.3ModelComponentSet (ModelInstances)
                                                                                                                            (Editor‟s note)
                                                                                                                            No change on ModelInstances by claim from JP (see
                                                                                                                            B288)


JP    4.3.1                               te       The attribute “name” should be removed since                             (Editor‟s note)                                            Accepted
      ModelDomainPr                                ModelDomainProfile is a subclass of Administered Item and                Change „name‟ to „domain name‟
09                                                                                                                                                                                     COMPLETE
      ofile                                        Designation (of Administered Item) already has an attribute
                                                   “name”.                                                                  Move the sentence “The attribute „name‟ is not necessary
                                                                                                                            to be a globally unique identifier.” Into NOTE of (2)
                                                   The meaning of the sentence “The attribute „name‟ is not                 attribute „domain name‟ .
                                                   necessary to be a globally unique identifier.” at (4) Constraints is
                                                   unclear.
JP    4.2.xx 4.3.XX      (4)              te       There are a lot of descriptions that does not seem constraints.          (Editor‟s note)                                            Accepted
                         Constraints               For example, 4.2.3 ModelComponentSet (4) Constraints says                Change the format of Constraint with itemization.          COMPLETE
10
                                                   “selected by : ModelSelection [0..*], Optional”, which is a

 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)
 2 Type of comment: ge = general         te = technical   ed = editorial
 NOTE   Columns 1, 2, 4, 5 are compulsory.
                                                                                                                                                                                                     page 16 of 24
 ISO electronic balloting commenting template/version 2001-10
Template for comments and secretariat observations                                                                   Date: 09-02-27                     Document: ISO/IEC FCD2 19763-2


 1           2                (3)              4                                  5                                                               (6)                                          (7)

MB1     Clause No./       Paragraph/       Type           Comment (justification for change) by the MB                             Proposed change by the MB                        Secretariat observations
         Subclause       Figure/Table       of                                                                                                                                      on each comment submitted
            No./             /Note         com-
           Annex         (e.g. Table 1)    ment2
          (e.g. 3.1)


                                                   description of a reference.


JP    3 Annex A                           ed       The title„MDR-ByMOF‟ is inappropriate since A.2 has no relation   (Editor‟s note)                                               Accepted
      (normative)                                  to MDR-ByMOF.                                                     Change the title to
11                                                                                                                                                                                 COMPLETE
      MDR-ByMOF                                                                                                      „MOF Representation of MDR and naming rule‟
JP    Annex A            Table A.1,       te       The meanings of DI-1, DI-2, (sign) (concept) (componentset)       DEFERRED                                                      Accepted
                                                   etc. need to be specified.                                                                                                      COMPLETE
12                                                                                                                   (Editor‟s note)
                                                                                                                     Add the format of IRDI as follows:
                                                                                                                     IRDI (International Registration Data Identifier) is a
                                                                                                                     concatenated string specified by DI-1, DI-2, DI-3, Postfix1
                                                                                                                     and Postfix2. The table A.1 provides the naming
                                                                                                                     convention of Administered Items in MFI core. The
                                                                                                                     description conventions are as follows;
                                                                                                                     1) DI-1 is a prime name of Data Identifier, DI-2 and DI-3
                                                                                                                     is a qualified name for DI-1. Postfix1 and Postfix2 is
                                                                                                                     additional information on stewardship.
                                                                                                                     2) The strings of sign, domain name, component name
                                                                                                                     should be the attribute value of ModelSign,
                                                                                                                     ModelDomainProfile and ModelComponent respectively.
                                                                                                                     3)The strings of concept id, instances id, componentset
                                                                                                                     id and selection id may be provided appropriately
                                                                                                                     corresponding to ModelConcept, ModelInstances,
                                                                                                                     ModelCompnentSet and ModelSelection.
                                                                                                                     4)The strings of rai and version are postfixes for
                                                                                                                     registration authority identifier and version identifier.
                                                                                                                     5) The character „/‟ is used as separator of DI-1, DI-2,
                                                                                                                     DI-3, Postfix1 and Postifix2.
                                                                                                                     Format: sign/concept/domain/rai/version

JP    Annex A            Table A.1,       te       This naming convention for IRDI does not conform to ISO/IEC                                                                     NOT Accepted
                                                   11179-6.
13

 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)
 2 Type of comment: ge = general         te = technical   ed = editorial
 NOTE   Columns 1, 2, 4, 5 are compulsory.
                                                                                                                                                                                                 page 17 of 24
 ISO electronic balloting commenting template/version 2001-10
Template for comments and secretariat observations                                                                         Date: 09-02-27                   Document: ISO/IEC FCD2 19763-2


    1           2                (3)              4                                    5                                                              (6)                                            (7)

MB1        Clause No./       Paragraph/       Type           Comment (justification for change) by the MB                               Proposed change by the MB                         Secretariat observations
            Subclause       Figure/Table       of                                                                                                                                         on each comment submitted
               No./             /Note         com-
              Annex         (e.g. Table 1)    ment2
             (e.g. 3.1)


JP       General                             te       There seem to be several redundant references.                       DEFERRED                                                      Accepted
14                                                    It is better to eliminate redundancy.                                (Editor‟s note)                                               COMPLETE
                                                      At least, constraints among redundant references need to be          Adding the constraint ;
                                                      specified so that semantic contradictions may not occur.
                                                                                                                           4.2.3ModelSelection
                                                      Example:
                                                                                                                           (4)Constraints
                                                      Country/Country and Regison/Global Boundary : ModelSign
                                                                                                                           -binding constraint 3: The ModelConcept designated by
                                                      Country and Regison/Global Boundary : ModelConcept                   the „expresses‟ ModelSign of the ModelSelection, shall be
                                                      Bicycle/Vehicle:ModelConcept                                         same as one conceptualized by its „selected by‟
                                                                                                                           ModelInstances.
                                                      InvalidSelection/Country/Bicycle : ModelSelection
                                                                                                                           ( See also CA17 and CA 52)
                                                       “InvalidSelection/Country/Bicycle : ModelSelection” is allowed,
                                                      although it does not make sense because it selects a bicycle that
                                                      has no relation to a country.



US       Clause 2                            Ed       This standard relates to Edition 2 of ISO/IEC 11179. It should       Make the change to include the year as follows:               Accepted
                                                      reference the year. A future Edition of 19763 should reference
1                                                                                                                          ISO/IEC 11179-3:2003, Information technology –                COMPLETE
                                                      Edition 3 of 11179.                                                  Metadata registries (MDR) - Part 3: Registry metamodel
                                                                                                                           ISO/IEC 11179-6:2005, Information technology –
                                                                                                                           Metadata registries (MDR) - Part 6: Registration
US       Clause 2                            Ed       The standard references ISO/IEC 19502. These should be               Add a normative reference to ISO/IEC 19502 – MOF with         Accepted
2                                                     shown as a normative references. The reference should show           the year of publication for each.
                                                                                                                                                                                         COMPLETE
                                                      the year of publication, since this Edition of 19763-2 is based on
                                                      that specific version of the MOF and ISO/IEC 11179-6.
US       General                             Ed       There are several places where apparently revised text is in the     Change to black all text revisions that were marked by        Accepted
                                                      color blue or purple, e.g., see Clause 4.1.2 on page 22. These       using the text color blue. This does not apply to text from
3                                                     seem to be from prior editing sessions, although they are not        the ISO template that is in blue, e.g., see page IX.          COMPLETE
                                                      marked as such. Since all of these revisions are accepted, the
                                                      blue color no longer has relevance.
US       General                             Ed       There are several places where the English needs proofreading.       A marked up version with tracking changes turned on,          Accepted
                                                      Changes in grammar, wording, and punctuation are needed.             will be provided directly to the project editor. The marked
4                                                                                                                                                                                        COMPLETE
                                                                                                                           up version is not intended to make any technical changes.


    1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)
    2 Type of comment: ge = general         te = technical   ed = editorial
    NOTE   Columns 1, 2, 4, 5 are compulsory.
                                                                                                                                                                                                       page 18 of 24
    ISO electronic balloting commenting template/version 2001-10
Template for comments and secretariat observations                                                                           Date: 09-02-27                 Document: ISO/IEC FCD2 19763-2


 1           2                (3)            4                                       5                                                                (6)                                    (7)

MB1     Clause No./       Paragraph/      Type            Comment (justification for change) by the MB                                    Proposed change by the MB              Secretariat observations
         Subclause       Figure/Table      of                                                                                                                                    on each comment submitted
            No./             /Note        com-
           Annex         (e.g. Table 1)   ment2
          (e.g. 3.1)




B28                                                Ballot comment CA 17 notes that the meaning of this constraint            See CA17.
7                                                  is unclear. The constraint states: “A component type and its
                                                   code system should be specified in the corresponding
                                                   ModelDomainProfile profiles.”
                                                   However, ModelDomainProfile does not have a code list… the
                                                   meaning of this sentence is not clear.
B28                                                J08 was discussed and accepted as it proposed unofficially in             (Editor‟s note)
8                                                  WG2 NY meeting,                                                           See J08
                                                   July 2007 and we WG2 confirmed that officially at the comment             Confirmed at Vilamoura meeting.
                                                   resolution session of FCD2 19763-2 in WG2 Seoul meeting,
                                                   December 2007.
                                                   See WG2 1095, even though it is “Interim Draft Disposition on
                                                   08/01/22” and not the outcome of the comment resolution
                                                   session of FCD2 19763-2 in WG2 Seoul meeting in December.
                                                   But the editor‟s draft FDIS 19763-2 (WG2 N1097) treats J08
                                                   differently.
                                                   Any new change proposal or comment by anybody, including
                                                   editor, need to be put on this Bugzilla first before it is reflected in
                                                   the editor‟s draft FDIS 19763-2. Then we WG2 can discuss it and
                                                   resolve it. Only after that the editor‟s draft FDIS 19763-2 can
                                                   reflect it specifically in accordance with the consensus of WG2
                                                   since it is a draft for FDIS, and not for CD.
B28                                                J09 was resolved as it proposed at the comment resolution                 (Editor‟s note)
9                                                  session of FCD2 19763-2 in WG2 Seoul meeting, December
                                                   2007.                                                                     Confirmed at Vilamoura meeting.

                                                   See WG2 1095, even though it is “Interim Draft Disposition on
                                                   08/01/22” and not the outcome of the comment resolution
                                                   session of FCD2 19763-2 in WG2 Seoul meeting in December.
                                                   But the editor‟s draft FDIS 19763-2 (WG2 N1097) treats J09
                                                   differently.
                                                  Any new change proposal or comment by anybody, including
                                                  editor, should be put on this Bugzilla first before it is reflected in
                                                  the editor‟s draft FDIS 19763-2. Then we WG2 can discuss it and
 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)
 2 Type of comment: ge = general         te = technical     ed = editorial
 NOTE   Columns 1, 2, 4, 5 are compulsory.
                                                                                                                                                                                               page 19 of 24
 ISO electronic balloting commenting template/version 2001-10
Template for comments and secretariat observations                                                                   Date: 09-02-27                     Document: ISO/IEC FCD2 19763-2


 1           2                (3)            4                                     5                                                              (6)                                       (7)

MB1     Clause No./       Paragraph/      Type            Comment (justification for change) by the MB                            Proposed change by the MB                      Secretariat observations
         Subclause       Figure/Table      of                                                                                                                                    on each comment submitted
            No./             /Note        com-
           Annex         (e.g. Table 1)   ment2
          (e.g. 3.1)


                                                   resolve it. Only after that the editor‟s draft FDIS 19763-2 can
                                                   reflect it specifically in accordance with the consensus of WG2
                                                   since it is a draft for FDIS, and not for CD.
B29                                                ModelAssociationEnd is analogous to AssociationEnd of ISO/IEC     (Editor‟s note)                                            Withdrawn
0                                                  19502 MOF1.4 metamodel.
                                                                                                                     Withdrawn by the discussion within Japan NB.
                                                   In ISO/IEC 19502 MOF1.4, an AssociationEnd defines a
                                                   Classifier participant in the Association via IsOfType of
                                                   TypedElement, which is a super class of AssociationEnd, and
                                                   AssociationEnd is not a subclass of Classifier.
                                                   See Figure B.1- MOF Package at page 56 of WG2 N1097
                                                   Editor‟s draft FDIS 19763-2.
                                                   Similarly, a ModelAssociationEnd defines a Modelconcept
                                                   participant in the ModelAssociation and ModelAssociationEnd is
                                                   not a subclass of ModelConcept.
                                                   Change proposal:
                                                   ModelAssociationEnd should be change not to be a subclass of
                                                   ModelConcept.
                                                   A new reference from ModelAssociation to ModelConcept called
                                                   “isOfType” should be introduced.
B29                                                Model Construct should be merged to Model Classifier since        Change proposal:                                           Accepted
1                                                  there is no reason to distinguish Model Construct and Model       Delete 4.3.3 ModelConstruct
                                                   Classifier                                                                                                                   COMPLETE
                                                                                                                     Move its reference “has” to 4.3.4 ModelClassifier.
                                                                                                                     Change “ModelConstruct” at 4.3.4 ModelClassifier (1)
                                                                                                                     Superclass to “none”.
                                                                                                                     (Editor‟s note)


B29                                                J10 says there are a lot of descriptions that do not seem         Proposal:                                                  Accepted
2                                                  constraints, and does not say they should be itemized.
                                                                                                                     Check all the descriptions at (4) Constraints of all the   COMPLETE
                                                   For example, the second sentence at (4) Constraints, 4.3.4        metaclasses and delete the irrelevant ones.
                                                   ModelClassifier says “One unit of model consists of one
                                                   package”. It is unclear how this sentence constrains the          (Editor‟s note)
                                                   metaclass “ModelClassifier”.                                      Delete 4) Constraints, 4.3.4 ModelClassifier says “One

 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)
 2 Type of comment: ge = general         te = technical   ed = editorial
 NOTE   Columns 1, 2, 4, 5 are compulsory.
                                                                                                                                                                                              page 20 of 24
 ISO electronic balloting commenting template/version 2001-10
Template for comments and secretariat observations                                                                          Date: 09-02-27                    Document: ISO/IEC FCD2 19763-2


 1           2                (3)            4                                        5                                                                 (6)                                             (7)

MB1     Clause No./       Paragraph/      Type            Comment (justification for change) by the MB                                   Proposed change by the MB                           Secretariat observations
         Subclause       Figure/Table      of                                                                                                                                                on each comment submitted
            No./             /Note        com-
           Annex         (e.g. Table 1)   ment2
          (e.g. 3.1)


                                                   Another example is the third sentence at (4) Constraints, 4.3.5          unit of model consists of one package”.
                                                   ModelByMOF, that is, . It is also unclear how this sentence
                                                   constrains the metaclass “ModelByMOF”.


B29                                                There are still possible redundancies.                                   Proposal:                                                       Accepted
3                                                  For example, an attribute “model type” of 4.2.2 ModelConcept is          Change the Use of an attribute “model type” of 4.3.4            COMPLETE
                                                   exactly same as an attribute “model type” of 4.3.4                       ModelClassifier from Optional to Mandatory and delete an
                                                   ModelClassifier if the multiplicity of an attribute “claasified by” is   attribute “model type” of 4.2.2 ModelConcept in
                                                   changed from 0..1 to 1..1.                                               accordance with a good criterion “one fact in one place”.
                                                   Another example is that there are possibly related composite             (Editor‟s note)
                                                   relations between ModelDomainProfile and ModelClassifier.
                                                                                                                            Delete “modeltype” of 4.2.2 ModelConcepts
                                                   One is through ModelByMof and the other is through
                                                   ModelComponentSet (see Figure 5 – Target package in MFI                  And
                                                   Core).                                                                   Change multiplicity of an attribute “alassified by” from 0..1
                                                   It is unclear whether they are redundant, related or independent.        to 1..1 and into Mandatory.


                                                                                                                            Proposal:
                                                                                                                            At least a suitable constraint needs to be added in a
                                                                                                                            proper place unless they are independent.
                                                                                                                            (Editor‟s note)
                                                                                                                            Change the definition of ModelDomainProfile as follows;
                                                                                                                            -ModelDomainProfile has ModelSpecifications and
                                                                                                                            ModelComponents (not ModelClassifier directly)
                                                                                                                            -ModelComponent has ModelClassifiers


                                                                                                                            And added constraints are
                                                                                                                            -binding constraint 1: A ModelInstances may be
                                                                                                                            conceptualized independently by a ModelConcept. The
                                                                                                                            ModelComponent in the ModelComponentSets of a
                                                                                                                            ModelInstances shall be enforced to be classified by the

 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)
 2 Type of comment: ge = general         te = technical   ed = editorial
 NOTE   Columns 1, 2, 4, 5 are compulsory.
                                                                                                                                                                                                          page 21 of 24
 ISO electronic balloting commenting template/version 2001-10
Template for comments and secretariat observations                                                                   Date: 09-02-27                     Document: ISO/IEC FCD2 19763-2


 1           2                (3)            4                                     5                                                              (6)                                          (7)

MB1     Clause No./       Paragraph/      Type            Comment (justification for change) by the MB                            Proposed change by the MB                         Secretariat observations
         Subclause       Figure/Table      of                                                                                                                                       on each comment submitted
            No./             /Note        com-
           Annex         (e.g. Table 1)   ment2
          (e.g. 3.1)


                                                                                                                     ModelClassifier.
                                                                                                                     -binding constraint 2: The ModelClassifier should be
                                                                                                                     included in the ModelDomainProfile as a ModelClassifier
                                                                                                                     that should belong to some ModelComponent of the
                                                                                                                     ModelDomainProfile.
                                                                                                                     -binding constraint 3: The ModelConcept designated by
                                                                                                                     the „expresses‟ ModelSign of the ModelSelection, shall be
                                                                                                                     same as one conceptualized by its „selected by‟
                                                                                                                     ModelInstances.
B29                                                An instance of mataclass, say, “XXX” is referred at least in      Proposal:                                                     Accepted
4                                                  following three ways. It should follow the same rule.
                                                                                                                     An instance (or instances) of mataclass, say, “XXX”,          COMPLETE
                                                   1) a XXX instance                                                 should be referred only as an instance (or instances ) of
                                                   Example: “A ModelSign instance” at the 5th paragraph of (4)       XXX because this is the clearest way to refer it (or them).
                                                   Constarints, 4.2.1 ModelSign
                                                   2) a XXX
                                                   Example: “A ModelClassifier” at the first paragraph of (4)
                                                   Constraints, 4.3.4 ModelClassifier
                                                   3) XXX-xxx
                                                   Example: ModelDpmainProfile-profiles at the third paragraph of
                                                   (4) Constraints, 4.3.4 ModelClassifier




 ITTF comments were given with marked text and attached following notes.
 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)
 2 Type of comment: ge = general         te = technical   ed = editorial
 NOTE   Columns 1, 2, 4, 5 are compulsory.
                                                                                                                                                                                                 page 22 of 24
 ISO electronic balloting commenting template/version 2001-10
Template for comments and secretariat observations                                                                   Date: 09-02-27                     Document: ISO/IEC FCD2 19763-2


 1           2                (3)            4                                    5                                                               (6)                                    (7)

MB1     Clause No./       Paragraph/      Type            Comment (justification for change) by the MB                            Proposed change by the MB                  Secretariat observations
         Subclause       Figure/Table      of                                                                                                                                on each comment submitted
            No./             /Note        com-
           Annex         (e.g. Table 1)   ment2
          (e.g. 3.1)




 Use of square brackets indicates that the term is taken verbatim from the Terms and definitions clause of the cited document. Convert to a note wherever this is not the
 case.

 Update numbering from here on and redraft in line with 3.1.1 to 3.1.18.

 Follow presentation of Annexes A to C for remaining annexes.

 These documents are either cited informatively or not at all elsewhere in the document; therefore, they may not be given as normative references. Please check all titles
 and years of publication against the ISO online catalogue for documents given in normative references and bibliography.




 1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)
 2 Type of comment: ge = general         te = technical   ed = editorial
 NOTE   Columns 1, 2, 4, 5 are compulsory.
                                                                                                                                                                                           page 23 of 24
 ISO electronic balloting commenting template/version 2001-10

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:2
posted:12/2/2011
language:Afrikaans
pages:24