gitgabrio commented on issue #1019: URL: https://github.com/apache/incubator-kie-issues/issues/1019#issuecomment-2074369570
@tiagobento @ljmotta @yesamer There is an ongoing discussion on the OMG group. My personal understanding of that (but also share by @baldimir ) is that 1. the spec themselves define/imply a given behavior (i.e. the usage of `?` expression types, also on inherited properties), 2. the idea is somehow enforced by the new typeConstraints, and the only difference with allowedValues is the projection inside collection elements 3. the introduction of typeConstraint, with its consequences, was dictated bny a sort of contradiction in the specs themselves (that somehow defined constraints as UnaryTests to be applied to base type, but on the other side restriected the full usage of them) 4. there was an "agreement" in the past, about interpretation of the spec, based on a sentence that has been removed from new specs So, we are currently discussing of that. I'm new to this decisional mechanism, and I have no idea of the outcome. Regardless, the way we interpeted (and already implemented) the specs would allow much powerful behavior, and IMO it would be interesting to provide it to customer (being, anyway, backward and spec compatible) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
