[mdht-dev] Property Redefinition Constraint

["sean.muir@xxxxxxxxxxxxxxx" <sean.muir@xxxxxxxxxxxxxxx>]

There was an issue as part of the eclipse transformation

I wanted to confirm the expected results with everyone on 0..* and 1..* constraints


If not strict 
a redefinition of 0..1 or 1..1 will require at least 1 
ocl 
(self.id->isEmpty() or self.id->exists(element | element.isNullFlavorUndefined())) implies (self.id->size() >= 1)

if strict
a redefinition of 0..1 or 1..1 will require at least one and not more then 1 and a total of 1
(self.id->isEmpty() or self.id->exists(element | element.isNullFlavorUndefined())) implies (self.id->size() = 1)


this will also apply to other variations 

a redefinition of n..m where 

if not strict  (this seems a bit non sensical because we do not implement constraint of upper bound)
(self.id->isEmpty() or self.id->exists(element | element.isNullFlavorUndefined())) implies (self.id->size() >= n)

if strict
(self.id->isEmpty() or self.id->exists(element | element.isNullFlavorUndefined())) implies (self.id->size() >= n and self.id->size() <= m)


We can discuss on the dev call today 

Thanks

Sean

Attachment: smime.p7s
Description: S/MIME cryptographic signature