Issue 17572: NIEM-UML FTF Issue: Namespace prefix (niem-uml-ftf) Source: Model Driven Solutions (Mr. Cory B. Casanave, cory-c(at)modeldriven.com) Nature: Uncategorized Issue Severity: Summary: The NIEM community as well as IEPD developers have accepted prefixes for namespaces. There is no way to represent these prefixes in the profile resulting in meaningless machine generated prefixes in generated XSDs and XML documents. While this does not impact the formal interpretation of the namespaces, it does impact the human usability of those namespaces. However, due to possible redundancy only a default can be guaranteed. Recommended resolution: The “Namespace” stereotype should include a “DefaultPrefix” tag of type string to represent these common prefixes. This prefix should be used on all XML/XSD serializations using that namespace unless it conflicts with another. If there is a conflict the mapping should append a number to the default prefix to make it unique. Resolution: Revised Text: Actions taken: August 29, 2012: received issue Discussion: End of Annotations:===== m: Cory Casanave To: "issues@omg.org" CC: "Melo, Walt (Walcelio.Melo@noblis.org)" , "Sumant Kapoor (skapoor@radiantt.com) (skapoor@radiantt.com)" , Tom Digre , Ed Seidewitz Date: Wed, 29 Aug 2012 16:44:07 -0400 Subject: NIEM-UML FTF Issue: Namespace prefix Thread-Topic: NIEM-UML FTF Issue: Namespace prefix Thread-Index: Ac2GJeGtIDQLqGMDQAi3HzaX3nP/sA== 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.225]|10.1.50.225|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.225, Ugly c=0.844247 p=-0.985058 Source White X-Mailprotector-Scan-Diagnostics: 0-0-0-6734-c X-Mailprotector-ID: 704e6ee3-8c9e-44c0-9c62-e1d9881e2ac1 The NIEM community as well as IEPD developers have accepted prefixes for namespaces. There is no way to represent these prefixes in the profile resulting in meaningless machine generated prefixes in generated XSDs and XML documents. While this does not impact the formal interpretation of the namespaces, it does impact the human usability of those namespaces. However, due to possible redundancy only a default can be guaranteed. Recommended resolution: The .Namespace. stereotype should include a .DefaultPrefix. tag of type string to represent these common prefixes. This prefix should be used on all XML/XSD serializations using that namespace unless it conflicts with another. If there is a conflict the mapping should append a number to the default prefix to make it unique. Submitted by: Cory Casanave