Issue 18715: Clarify that stereotypes can be applied to UML DI (uml25-ftf) Source: NIST (Mr. Conrad Bock, conrad.bock(at)nist.gov) Nature: Clarification Severity: Significant Summary: [From Ed S in http://www.omg.org/archives/uml25-ftf/msg00357.html] Perhaps we can clarify this by simply adding some text to Annex B explicitly saying that stereotypes can be applied to UML DI elements and that a conforming tool is to interpret such stereotype application per 12.3.3 -- that is, with the MOF equivalent semantics and XMI serialization. This would simply become part of the requirement for UML diagram interchange conformance. It seems like a useful capability to me. Resolution: Revised Text: Actions taken: May 14, 2013: received issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 14 May 2013 16:02:43 -0400 To: Subject: Issue/Bug Report X-Brightmail-Tracker: AAAAAR15Qr0= X-Brightmail-Tracker: AAAAAA== ******************************************************************************* Name: Conrad Bock Employer: NIST mailFrom: conrad.bock@nist.gov Terms_Agreement: I agree Specification: Unified Modeling Language Section: FormalNumber: ptc/2012-10-24 Version: 2.5 beta 1 Doc_Year: 2012 Doc_Month: October Doc_Day: 01 Page: Title: Clarify that stereotypes can be applied to UML DI Nature: Clarification Severity: Significant CODE: 3TMw8 B1: Report Issue Remote Name: antlia.mel.nist.gov Remote User: HTTP User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; .NET4.0C; .NET4.0E; MS-RTC LM 8) Time: 04:02 PM Description: [From Ed S in http://www.omg.org/archives/uml25-ftf/msg00357.html] Perhaps we can clarify this by simply adding some text to Annex B explicitly saying that stereotypes can be applied to UML DI elements and that a conforming tool is to interpret such stereotype application per 12.3.3 -- that is, with the MOF equivalent semantics and XMI serialization. This would simply become part of the requirement for UML diagram interchange conformance. It seems like a useful capability to me.