xsd:QName intrepreation in BPMN 2.0 is not same as WSDL

[riceyeh]

Hi,
  A lot of elements in BPMN 2.0 use xsd:QName to refer to another element. For example, itemDefinition is referenced by xsd:QName. In a WSDL definition, the xsd:QName stands for namespace:name. In BPMN supplied examples, it is namespace:id. But in the BPMN 2.0, this is not clearly described. In activiti user guide, it follows the namespace:id interpretation. For XML spec itself, namespace is used to qualify a local name. This is my first time to see namespace is ued to qualify id. It is weird for me because id in BPMN 2.0 is defined to be with type xsd:ID, which by its definition already "define unique
identifiers that are global to a document" by itself and no need to have namespace to qualify it. More weird is that if we follow the namespace:name explanation but the itemDefinition element does not have a 'name' attribute. Any one can clear this confusion?

Rice

[jbarrez]

I agree that the BPMN spec is not clear on what exactly is the meaning of the QName.
However, i do believe that when writing some of the examples, I ran into problems with the id approach, as the schema didnt validate.
Could be I was doing it wrong, since I'm no big fan of strange XML schema constructs.