BPMN 2.0 FTF Avatar
  1. OMG Issue

BPMN2 — Section 8.1.5 [Infra] Import statement description is not clear enough

Open Closed All
  • Key: BPMN2-196
  • Legacy Issue Number: 14776
  • Status: closed  
  • Source: Object Management Group ( Mr. Mariano Benitez)
  • Summary:

    The intention of the import statement is to include an ENTIRE file as a namespace, so I can reference elements defined inside that file.

    The current text says:
    "The Import class is used when referencing external element, either BPMN elements contained in other BPMN Definitions or non-BPMN elements. Imports must be explicitly defined."

    It is not clear that you are importing the entire file (ala BPEL). Also, it is not clear what is the meaning of "Imports must be explicitly defined"

    – Proposal by Mariano Benitez 23/Oct —
    Change the wording to:

    The import class is used to import elements defined externally and make them available for use by elements defined within the scope of the import element.
    The importType attribute defines the style of associated with the element. Both BPMN and non-BPMN imports are allowed.
    For example: This allows importing an XML Schema that will be used inside StructureDefinition elements, or invoking a global task defined in another file.
    Import elements can be defined globally as part of the definitions, so it is available to all elements defined in that definitions, or it can be defined inside a StructureDefinition, which restricts the scope to that element only.
  • Reported: BPMN 2.0b1 — Mon, 23 Nov 2009 05:00 GMT
  • Disposition: Resolved — BPMN 2.0
  • Disposition Summary:

    Change in Table 8.2 Import Attributes, the description of the importType attribute to:
    "Identifies the type of document being imported by providing an absolute URI that identifies the encoding language used in the document.The value of the importType
    attribute MUST be set to http://www.w3.org/2001/XMLSchema when importing XML Schema 1.0 documents, to http://www.w3.org/TR/wsdl20/ when importing
    WSDL 2.0 documents, and http://schema.omg.org/spec/BPMN/2.0 when importing BPMN 2.0 documents. Other types of documents MAY be supported.
    Importing Xml Schema 1.0, WSDL 2.0 and BPMN 2.0 types MUST be supported."
    Note on 2010-04-26:
    The FTF acknowldges the proposed namespace does not follow OMG guidelines for namespace conventions. The final namespaces will be:
  • Updated: Fri, 6 Mar 2015 20:57 GMT