- From: <bugzilla@wiggum.w3.org>
- Date: Fri, 25 May 2007 11:19:03 +0000
- To: public-ws-policy-qa@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4584 ------- Comment #1 from sergey.beryozkin@iona.com 2007-05-25 11:19 ------- If the requester initiates the intersection and it has ignorable assertions then if those assertions are truly ignorable, that is, the requester has not marked them as ignorable by mistake, then it might be harmless for suchs assertions be included in the post-intersection policy even though no match has been found during the intersection. The value of it is unclear though so it all needs to be clarified. It's not clear why the assertion which the requester has marked as ignorable (thus presumably telling about the nature of such an assertion to the consumers of this requester's policy) is still in the intersected policy even though no match is there.
Received on Friday, 25 May 2007 11:19:09 UTC