- From: Michael Steidl via GitHub <sysbot+gh@w3.org>
- Date: Thu, 24 Nov 2016 10:20:42 +0000
- To: public-poe-archives@w3.org
@riannella my view on your proposal is: that makes processing more complicated than a filtering category of a class. 1. Start processing a Party 2. Check all the constraints if one or more apply/ies to this party (this raises the issue we discussed already: how to link constraint and party, a link from the constraint to "assignee" is not sufficient as there could be multiple of them.) 3. A hand-written constraint processor is required to interpret the left operand correctly. 4. The results of all constraints have to be ANDed for making the final result. With a property of a Party: the processor doesn't have to parse all constraints, the "filter" is attached to a specific instance of Party. The challenge of "how to get a result" is similar: how to check if this filtering item applies to the party - but the constraint-searching and -matching overhead does not exist. -- GitHub Notification of comment by nitmws Please view or discuss this issue at https://github.com/w3c/poe/issues/59#issuecomment-262740835 using your GitHub account
Received on Thursday, 24 November 2016 10:20:48 UTC