- From: Michael Steidl via GitHub <sysbot+gh@w3.org>
- Date: Tue, 04 Jul 2017 07:21:03 +0000
- To: public-poe-archives@w3.org
I've raised where should andSequence reside at the call on Monday and heard it should be moved to the Binary Constraint as it should process only two Constraint results. That's why I've put it there in my suggestion. Re @riannella suggestion: * re the facts: * how to deal with the types of collections of object values: using rdf:Seq for sequences requires to use rdf:List for a simple set of values - right? (I see no alternative.) * I think using the operator odrl:and and a rdf:Seq as type of the object needs more to define the same as currently odrl:andSequence defines. I miss the definition that only after the first Constraint (leftOperand) in the sequence has been satisfied the next operand (rightOperand) in the sequence can be evaluated. Using a Boolean "and" with a sequence only sidelines the commutativity of the and operation, nothing else. * what about the Boolean or and the xor1 with rdf:Seq? * the emotional facet: I recall from Monday that having to use explicitly rdf:Seq was not liked -- GitHub Notification of comment by nitmws Please view or discuss this issue at https://github.com/w3c/poe/issues/206#issuecomment-312800517 using your GitHub account
Received on Tuesday, 4 July 2017 07:21:09 UTC