| Re: [mdt-bpmn2.dev] Commit: change the caps for associationDirection to match the xsd |
I changed this as the xsd I was looking at wasn't using caps. Obviously it was wrong and I apologize for the mess. I'll fix it ASAP.On Mon, Oct 25, 2010 at 02:34, Hille-Doering, Reiner <reiner.hille-doering@xxxxxxx> wrote:
_______________________________________________BTW: Chaning the ECore is generally dangerous. Even if changes be masked using ExtendedMetadata (and thus maintaining compatibility to XSD), it would break XMI compatibility.
Von: mdt-bpmn2.dev-bounces@xxxxxxxxxxx [mailto:mdt-bpmn2.dev-bounces@xxxxxxxxxxx] Im Auftrag von Henning Heitkötter
Gesendet: Montag, 25. Oktober 2010 10:53
An: BPMN2 Developers Mailing List
Betreff: [mdt-bpmn2.dev] Commit: change the caps for associationDirection to match the xsd
Hi Antoine,
I'm sorry, but I don't understand the purpose of your last commit:<eClassifiers xsi:type="ecore:EEnum" name="AssociationDirection">
- <eLiterals name="None"/>
- <eLiterals name="One" value="1"/>
- <eLiterals name="Both" value="2"/>
+ <eLiterals name="None" literal="none"/>
+ <eLiterals name="One" value="1" literal="one"/>
+ <eLiterals name="Both" value="2" literal="both"/>
</eClassifiers>
As I see it, the XSD requires upper-case literals as well:<xsd:simpleType name="tAssociationDirection">
<xsd:restriction base="xsd:string">
<xsd:enumeration value="None"/>
<xsd:enumeration value="One"/>
<xsd:enumeration value="Both"/>
</xsd:restriction>
</xsd:simpleType>
If I try to validate the XML serialization of a BPMN document with lower-case literals against the BPMN2 XSD, I get corresponding errors, while the upper-case version works fine, as expected.
I'm referring to this version of the specification: http://www.omg.org/spec/BPMN/2.0/Beta2/
Thanks,
Henning
mdt-bpmn2.dev mailing list
mdt-bpmn2.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-bpmn2.dev