René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"local Cross Tree Constraints","articleBody":"I work on a industrial tool simulating fluid flow (e.g., air flow on an supersonic airplane).\r\nFor this tool, I developed the [pydop library](https://github.com/onera/pydop), and I would really like to be able to directly use the UVL as input syntax.\r\nHowever, UVL faces a couple of mostly-cosmetics limitations that my physicists colleagues do no like.\r\nThe first one is the fact that the cross-tree constraints are defined globally at the end of the file.\r\nThis makes writing and reading the feature model less natural, since the information related to some features are not close by.\r\nSyntactically, local ctc only requires adding an optional new \"constraints\" block within a feature, at the same level of groups:\r\n```\r\nfeatures\r\n    root\r\n        optional\r\n            f1\r\n                optional\r\n                    f2\r\n                    f3\r\n                constraints\r\n                    f3 =\u003e f2\r\n            f4\r\n                ...\r\n```\r\nThe drawback of such local ctc, as noted by Sebastian Krieter is that it requires some scope analysis to ensures that the features mentioned in a local ctc are declared in the local fm subtree. Then the semantics of such a ctc is simply \"if the including feature is selected, then the ctc must be validated\", which is quite intuitive, as demonstrated by my physicists colleagues who didn't have any prior knowledge of SPL before our collaboration.","author":{"url":"https://github.com/gzoumix","@type":"Person","name":"gzoumix"},"datePublished":"2024-09-04T15:17:37.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/3/Universal-Variability-Language.github.io/issues/3"}