- From: Michael Steidl via GitHub <sysbot+gh@w3.org>
- Date: Mon, 28 Nov 2016 14:58:24 +0000
- To: public-poe-archives@w3.org
What is a Constraing on a Constraint? I think for a deeper discussion on 5 December we need a description of what exactly that should be. The referenced Requirement DM.06 raises this need: "Extend the temporal constraints by setting a time reference, any period in the rightOperand refers to this point in time." The referred UCs for that requirement are UC16 (combining two constraints: c1 = monthly access, c2=over 7 years) and UC19 (exercising the action of a permission only after the end of an event) For both UCs I see no urgent need for a Constraint on Constraints: - UC 16 could be solved by applying two constraints to the permission (... is it really needed to combine both into a single one?) - see https://www.w3.org/2016/poe/wiki/Use_Cases#POE.UC.16_Accessing_Historical_Data - UC 19 could be solved by a constraint covering that use case, e.g. eventEndPeriod in https://www.w3.org/2016/poe/wiki/Constraints I'd like to remind of the general approach liked at the Constraints conference call on 15 November: it is better to express a complex scenario in a single, special constraint definition than expressing it by a rich set of constraint graphs which primarily add complexity and do not simplify the processing. (Simon raised concerns about endless loops of nested constraints.) -- GitHub Notification of comment by nitmws Please view or discuss this issue at https://github.com/w3c/poe/issues/62#issuecomment-263292181 using your GitHub account
Received on Monday, 28 November 2016 14:58:30 UTC