Issue 14879: The spec should clearly state what visual features are available for extensions and which are restricted to core spec (bpmn2-rtf) Source: Tekgensis (Mr. Mariano Benitez, mariano(at)benitez.nu) Nature: Clarification Severity: Minor Summary: Right now there is no clear separation on which graphical features (like line thickness, type of lines, color, etc) vendors are free to use as extensions, and which are restricted for the specification to use. We should define which features we want to use in the spec and which ones vendors are free to use. The reason for this is that if a vendor chooses line thickness for some visual extension and in a revision we choose to use the same feature, the vendor is forced to change to adapt (most importantly end-users). For example: it is clear that color is open for vendor extensions, and we should pick lines (thickness, dotted, etc) as restricted for our use. Resolution: Revised Text: Actions taken: December 17, 2009: received issue Discussion: It would be important for the spec to clearly specify the limits where graphical extensions can be added, and what is exclusive to the specification. It is not important right now, but I think we need to fix this. specially looking forward. So I propose to defer the issue. Disposition: Deferred End of Annotations:===== m: webmaster@omg.org Date: 17 Dec 2009 12:12:39 -0500 To: Subject: Issue/Bug Report ******************************************************************************* Name: Mariano Benitez Company: Oracle mailFrom: mariano.benitez@oracle.com Notification: No Specification: BPMN 2.0 Section: 13 FormalNumber: DTC-09-08-14 Version: Beta RevisionDate: Aug 09 Page: 361 Title: The specification should clearly state what visual features are available for extensions and which are restricted to the core spec Nature: Clarification Severity: Minor test: 3qw8 B1: Report Issue Description: Right now there is no clear separation on which graphical features (like line thickness, type of lines, color, etc) vendors are free to use as extensions, and which are restricted for the specification to use. We should define which features we want to use in the spec and which ones vendors are free to use. The reason for this is that if a vendor chooses line thickness for some visual extension and in a revision we choose to use the same feature, the vendor is forced to change to adapt (most importantly end-users). For example: it is clear that color is open for vendor extensions, and we should pick lines (thickness, dotted, etc) as restricted for our use.