${taskforce.name} Avatar
  1. OMG Task Force

2nd NIEM-UML FTF — Closed Issues

Open Closed All
Issues resolved by a task force and approved by Board

Issues Descriptions

Page 295 -

  • Legacy Issue Number: 18900
  • Status: closed  
  • Source: Advanced Systems Management Group Ltd. ( Mr. Vijay Mehra)
  • Summary:

    Page 295 -

    B.2.9.8 Mapping a

    {schema:element declaration}

    Change line item in paragraph [Rule: Mapping for an Unstereotyped Content Element Declaration

    {uml:Property}

    ]

    From:

    5. (substitution group affiliation property) A mapping must exist between the substitution group affiliation of the

    {schema:element declaration}

    and the subsettedProperty of the

    {uml:Property}

    .

    To:

    5. (substitution group affiliation property) The mapping for the substitution group affiliation property is as follows:

    a. If there is exactly one subsettedProperty, a mapping must exist between the substitution group affiliation of the

    {schema:element declaration}

    and the subsettedProperty of the

    {uml:Property}

    .

    b. If there is not any subsettedProperty and if the type is a categorized

    {stereotype:AugmentationType}

    , the substitution group affiliation must be s:Augmentation.

  • Reported: NIEM-UML 1.0b2 — Wed, 11 Sep 2013 04:00 GMT
  • Disposition: Resolved — NIEM-UML 1.0
  • Disposition Summary:

    Agree with the issue

  • Updated: Fri, 6 Mar 2015 21:49 GMT

Page 240 editorial

  • Key: UMLNIEM_-9
  • Legacy Issue Number: 18897
  • Status: closed  
  • Source: Advanced Systems Management Group Ltd. ( Mr. Vijay Mehra)
  • Summary:

    Page 240 -

    Clause A.18:

    • Change “Person” to “AdoptingPerson”, subclassing NIEM-Core subset “Person”
  • Reported: NIEM-UML 1.0b2 — Wed, 11 Sep 2013 04:00 GMT
  • Disposition: Resolved — NIEM-UML 1.0
  • Disposition Summary:

    Agree with the issue

  • Updated: Fri, 6 Mar 2015 21:49 GMT

Page 227 - typo

  • Key: UMLNIEM_-8
  • Legacy Issue Number: 18896
  • Status: closed  
  • Source: Advanced Systems Management Group Ltd. ( Mr. Vijay Mehra)
  • Summary:

    Page 227 - Replace

    Also, the roles a person play may change over time.

    with

    Also, the roles a person plays may change over time.

  • Reported: NIEM-UML 1.0b2 — Wed, 11 Sep 2013 04:00 GMT
  • Disposition: Resolved — NIEM-UML 1.0
  • Disposition Summary:

    Agree with the issue.

  • Updated: Fri, 6 Mar 2015 21:49 GMT

P)age 226

  • Key: UMLNIEM_-7
  • Legacy Issue Number: 18895
  • Status: closed  
  • Source: Advanced Systems Management Group Ltd. ( Mr. Vijay Mehra)
  • Summary:

    Page 226 - Replace

    What we did is just pick 2 properties that we want out NIEM-Core person

    with

    What we did is just pick 2 properties that we want out of NIEM-Core person

  • Reported: NIEM-UML 1.0b2 — Wed, 11 Sep 2013 04:00 GMT
  • Disposition: Resolved — NIEM-UML 1.0
  • Disposition Summary:

    Agree with the issue

  • Updated: Fri, 6 Mar 2015 21:49 GMT

Page 264 text update

  • Legacy Issue Number: 18899
  • Status: closed  
  • Source: Advanced Systems Management Group Ltd. ( Mr. Vijay Mehra)
  • Summary:

    Page 264 -

    B.2.6.6 Categorized

    {uml:Class}

    [Definition: Category 3

    {uml:Class}

    ]

    Replace text:

    3. that is the specific

    {uml:Classifier}

    of exactly one

    {uml:Generalization}

    with:

    3. that is the specific

    {uml:Classifier}

    of exactly one

    {uml:Generalization}

    , the general

    {uml:Classifier}

    of which corresponds to a

    {schema:complex type definition with complex content}

    ..

  • Reported: NIEM-UML 1.0b2 — Wed, 11 Sep 2013 04:00 GMT
  • Disposition: Resolved — NIEM-UML 1.0
  • Disposition Summary:

    Agree with the issue

  • Updated: Fri, 6 Mar 2015 21:49 GMT

Page 243 - typo

  • Legacy Issue Number: 18898
  • Status: closed  
  • Source: Advanced Systems Management Group Ltd. ( Mr. Vijay Mehra)
  • Summary:

    Page 243 - Replace

    For each such exchange type we need to add a property to the “Exchange Schema”, this is done my just making one property for each exchange type in a property holder.

    with

    For each such exchange type we need to add a property to the “Exchange Schema”, this is done by just making one property for each exchange type in a property holder.

  • Reported: NIEM-UML 1.0b2 — Wed, 11 Sep 2013 04:00 GMT
  • Disposition: Resolved — NIEM-UML 1.0
  • Disposition Summary:

    Agree with the issue

  • Updated: Fri, 6 Mar 2015 21:49 GMT

8-1, 8-3, 8-5

  • Key: UMLNIEM_-2
  • Legacy Issue Number: 18878
  • Status: closed  
  • Source: Model Driven Solutions ( Mr. Cory Casanave)
  • Summary:

    Some prior resolutions for NIEM-UML issues did not specify that the diagrams should be updated to reflect the model and text changes as well as the changes in the specification URIs. The following diagrams should replace diagrams: 8-1, 8-3, 8-5, respectively.

    Replace 8-1 with:

    Replace 8-3 with:

    Replace 8-5 with:

  • Reported: NIEM-UML 1.0b2 — Fri, 23 Aug 2013 04:00 GMT
  • Disposition: Resolved — NIEM-UML 1.0
  • Disposition Summary:

    Agree with the issue, and diagrams 8-1, 8-3, and 8-5 will be updated

  • Updated: Fri, 6 Mar 2015 21:49 GMT

"Pet" example has errors

  • Key: UMLNIEM_-1
  • Legacy Issue Number: 18238
  • Status: closed  
  • Source: Model Driven Solutions ( Mr. Cory Casanave)
  • Summary:

    The "pet" example has errors that should be fixed as the example provides guidence on the proper use of NIEM-UML.

    Issues include:

    • New types should not be defined in the exchange model
    • Properties (as association ends) should not be added to subset types.
  • Reported: NIEM-UML 1.0b2 — Tue, 30 Oct 2012 04:00 GMT
  • Disposition: Resolved — NIEM-UML 1.0
  • Disposition Summary:

    The mode and text have been revised as indicated below. This includes:

    • Proper use of Subsets Vs References (Issue 18538 impacts Issue 18238 being correct thus changes to the “Pet” example for issue 18538 are included here)
    • Person from NIEM Core should not have new properties, AdoptingPerson is added as a substype.
    • “Identification” is consistently named “IdentificationType”
    • Clarification are added
  • Updated: Fri, 6 Mar 2015 21:49 GMT

Page 3 wording change

  • Key: UMLNIEM_-4
  • Legacy Issue Number: 18892
  • Status: closed  
  • Source: Advanced Systems Management Group Ltd. ( Mr. Vijay Mehra)
  • Summary:

    Page 3 – Replace:

    The FTF Recommendation and Report for this specification will be published on November 12, 2012. If you are reading this after that date, please download the available specification from the OMG Specifications Catalog.

    With

    The FTF Recommendation and Report for this specification will be published in November, 2013. If you are reading this after that date, please download the available specification from the OMG Specifications Catalog.

  • Reported: NIEM-UML 1.0b2 — Wed, 11 Sep 2013 04:00 GMT
  • Disposition: Resolved — NIEM-UML 1.0
  • Disposition Summary:

    Agree with the issue

  • Updated: Fri, 6 Mar 2015 21:49 GMT

XSDRestrictionComplexTypeSimpleContent OCL Issue

  • Key: UMLNIEM_-3
  • Legacy Issue Number: 18879
  • Status: closed  
  • Source: Model Driven Solutions ( Mr. Cory Casanave)
  • Summary:

    The OCL for the constraint titled “XSDRestrictionComplexTypeSimpleContent” is incorrect, the following changes should be made:

    Change “NIEMSimpleContent” to “XSDSimpleContent” on lines 3 and 6

    Change “specificl” to “specific” on line 5

  • Reported: NIEM-UML 1.0b2 — Fri, 23 Aug 2013 04:00 GMT
  • Disposition: Resolved — NIEM-UML 1.0
  • Disposition Summary:

    Agree with the proposed changes

  • Updated: Fri, 6 Mar 2015 21:49 GMT

Page 225

  • Key: UMLNIEM_-6
  • Legacy Issue Number: 18894
  • Status: closed  
  • Source: Advanced Systems Management Group Ltd. ( Mr. Vijay Mehra)
  • Summary:

    Page 225 - Replace

    A subset information model has a <<Subsets>> to the model it subsets. Everything in that subset namespace will be automatically (by name) subsets the corresponding element in the reference namespace.

    with

    A subset information model has a <<Subsets>> relationship to the model it subsets. Everything in that subset namespace automatically (by name) subsets the corresponding element in the reference namespace

  • Reported: NIEM-UML 1.0b2 — Wed, 11 Sep 2013 04:00 GMT
  • Disposition: Resolved — NIEM-UML 1.0
  • Disposition Summary:

    Agree with the issue

  • Updated: Fri, 6 Mar 2015 21:49 GMT

Page 4 typo

  • Key: UMLNIEM_-5
  • Legacy Issue Number: 18893
  • Status: closed  
  • Source: Advanced Systems Management Group Ltd. ( Mr. Vijay Mehra)
  • Summary:

    Page 4 - Replace

    All instances of ‘© 2012’

    With

    ‘© 2012-2013’

  • Reported: NIEM-UML 1.0b2 — Wed, 11 Sep 2013 04:00 GMT
  • Disposition: Resolved — NIEM-UML 1.0
  • Disposition Summary:

    Agree with the issue.

  • Updated: Fri, 6 Mar 2015 21:49 GMT