Page 295 -

B.2.9.8 Mapping a

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

]

From:

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

and the subsettedProperty of the

.

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

and the subsettedProperty of the

.

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

, the substitution group affiliation must be s:Augmentation.

Agree with the issue

Page 240 -

Clause A.18:

• Change “Person” to “AdoptingPerson”, subclassing NIEM-Core subset “Person”

Agree with the issue

Page 227 - Replace

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

with

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

Agree with the issue.

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

Agree with the issue

Page 264 -

B.2.6.6 Categorized

[Definition: Category 3

]

Replace text:

3. that is the specific

of exactly one

with:

3. that is the specific

of exactly one

, the general

of which corresponds to a

..

Agree with the issue

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.

Agree with the issue

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:

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

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.

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

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.

Agree with the issue

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

Agree with the proposed changes

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

Agree with the issue

Page 4 - Replace

All instances of ‘© 2012’

With

‘© 2012-2013’

Agree with the issue.