Issue 18174: NIEM-UML Issue - General Information Models (niem-uml-ftf)
Source: Model Driven Solutions (Mr. Cory B. Casanave, cory-c(at)modeldriven.com)
Nature: Uncategorized Issue
Severity: 
Summary: Issue: NIEM has very specific namespace types such as subset, reference and constraints. These correspond directly to NIEM-UML information model types.  User experience has shown that segmenting a model in this way is complex for users and couples the PIM design with the PSM (XSD) representation.  It would be preferable that, in the PIM, there was a higher level representation.

 

Suggested resolution: Add an information model kind “General” that can subset any other model(s), add properties and include property redefinitions of cardinality and type.  To support this king od model, augment the QVT such that a General information model produces, as required, subset schema, constraint schema and extension schema that capture the semantics of the general model using legal NIEM schema.

Resolution: 
Revised Text: 
Actions taken:
October 17, 2012: received issue
Discussion: 

End of Annotations:=====

m: Cory Casanave <cory-c@modeldriven.com>
To: "issues@omg.org" <issues@omg.org>
CC: Tom Digre <tom-d@modeldriven.com>, Ed Seidewitz <ed-s@modeldriven.com>,
        "Dean, Michael (Michael.Dean@courts.wa.gov)" <Michael.Dean@courts.wa.gov>,
        "Vijay Mehra (vijaym@dni.gov)" <vijaym@dni.gov>,
        "'Stekervetz, Justin'
 (Justin.Stekervetz@hq.dhs.gov)" <Justin.Stekervetz@hq.dhs.gov>,
        "peter.mork@noblis.org" <peter.mork@noblis.org>,
        "jim.logan@cgifederal.com"
        <jim.logan@cgifederal.com>
Date: Wed, 17 Oct 2012 14:37:07 -0400
Subject: NIEM-UML Issue - General Information Models
Thread-Topic: NIEM-UML Issue - General Information Models
Thread-Index: Ac2slkLQYD8+g83eShmN12Y6uMFmmQ==
Accept-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
X-Mailprotector-Decision: deliver
X-Mailprotector-Connection: TLSv1|[10.1.50.226]|10.1.50.226|outbound.mailprotector.net|0.0|0.0|0|||0|0|0|0
X-Mailprotector-Results: null_ptr clean
X-Mailprotector-Score: 40
X-Mailprotector-IP-Analysis: 0, 10.1.50.226, Ugly c=0.819193 p=-0.994354 Source White
X-Mailprotector-Scan-Diagnostics:  0-0-0-6813-c
X-Mailprotector-ID: f651feb1-b33d-4ab9-a74a-7cdb19091ffc


Issue: NIEM has very specific namespace types such as subset, reference and constraints. These correspond directly to NIEM-UML information model types.  User experience has shown that segmenting a model in this way is complex for users and couples the PIM design with the PSM (XSD) representation.  It would be preferable that, in the PIM, there was a higher level representation.

 

Suggested resolution: Add an information model kind .General. that can subset any other model(s), add properties and include property redefinitions of cardinality and type.  To support this king od model, augment the QVT such that a General information model produces, as required, subset schema, constraint schema and extension schema that capture the semantics of the general model using legal NIEM schema.