NEW Issue: Matching assertion with empty nested Policy with assertion with no nested policy

[Frederick Hirsch <frederick.hirsch@nokia.com>]

PLEASE DO NOT REPLY TO THIS EMAIL OR START A DISCUSSISON THREAD UNTIL  
THE ISSUE IS ASSIGNED A NUMBER.
The issues coordinators will notify the list when that has occurred.

Protocol:  ws-sp

ws-securitypolicy-1.2-spec-ed-01-r07-diff

<http://www.oasis-open.org/apps/org/workgroup/ws-sx/download.php/ 
18836/ws-securitypolicy-1.2-spec-ed-01-r07-diff.doc>

Artifact:  spec, policy

Type: design

Title: Matching assertion with empty nested Policy with assertion  
with no nested policy

Description:
The spec states at line 372 "An assertion with an empty nested policy  
does not intersect with the same assertion without nested policy."

This does not make sense, they both  mean exactly the same thing.

Perhaps this is an issue for W3C Policy group, but <assertion /> and  
<assertion><policy /></assertion> should mean the same thing?  
Shouldn't an engine treat them as equal?

Should policy normalization process include this.

Related issues: none

regards, Frederick

Frederick Hirsch
Nokia