BPMN2 — LaneSet should have an optional ‘name’ attribute

Since a LaneSet represents a “a different way” of slicing up a process (e.g. by role or by department) then it should have a name, not just a (potentially unreadable) id to represent that way. Allowing different diagrams for the same Process to be distinguished.

There should be also a notation to allow for this: for example <Process Name>: <LaneSet Name>

So for example Figure 10.121 would have Supplier: By Department

Make the following changes to the MM (version Beta 1)

• Add attribute "name" of type "String" to class "LaneSet"
  Make the following changes to the XSD (version Beta 1)
• Change
  <xsd:complexType name="tLaneSet">
  <xsd:complexContent>
  <xsd:extension base="tBaseElement">
  <xsd:sequence>
  <xsd:element ref="lane" minOccurs="0" maxOccurs="unbounded"/>
  </xsd:sequence>
  </xsd:extension>
  </xsd:complexContent>
  </xsd:complexType>
  to
  <xsd:complexType name="tLaneSet">
  <xsd:complexContent>
  <xsd:extension base="tBaseElement">
  <xsd:sequence>
  <xsd:element ref="lane" minOccurs="0" maxOccurs="unbounded"/>
  </xsd:sequence>
  <xsd:attribute name="name" type="xsd:string"/>
  </xsd:extension>
  </xsd:complexContent>
  </xsd:complexType>
  Make the following changes to the specification text:
• Insert a new row at the top of table 10.127 (LaneSet attributes and model associations) with the following content:
  Column "Attribute Name":
  name: string
  Column "Description/Usage":
  The name of the LaneSet. A LaneSet is not visually displayed on a BPMN diagram. Consequently, the name of the LaneSet is not displayed as well.
  Disposition: Resolved