Part 1 Original text: An assertion MAY indicate that it is an ignorable policy assertion (see 4.4 Ignorable Policy Assertions). An ignorable policy assertion is an assertion that may be ignored for policy intersection (as defined in Section 4.5 Policy Intersection). By default, an assertion is not ignorable for policy intersection. No change. Change 2 Original text: If the mode is lax, two policy alternatives are compatible if each assertion in one that is not an ignorable assertion is compatible with an assertion in the other, and vice-versa. Revised text: If the mode is lax, two policy alternatives A and B are compatible: a) if each assertion in A that is not an ignorable assertion is compatible with an assertion in B, and b) if each assertion in B that is not an ignorable assertion is compatible with an assertion in A. Change 3 Old text: If the mode is strict Ttwo policy alternatives are compatible if each assertion in one is compatible with an assertion in the other, and vice-versa Revise for symmetry with Change 2. Change 4: New text (add commutative back in) Intersection is a commutative function that takes two policies and returns a policy. Change 5: This is an optional attribute of type xs:boolean New text: This attribute is of type xs:boolean Action to Editors: Apply to template edit to other cases of "optional element" or "optional attribute". Change 6: Name of the attribute: Preference Cannot live with Current proposal: MayBeIgnored 0 Candidate name1: Ignorable 8 0 Candidate name2: Ignore 1 Candidate name3: Informational 3 Candidate name4: Advisory 3 No objection to Ignorable Change 7: There are two modes for intersection: strict and lax. How the mode is indicated for the policy intersection is outside the scope of this specification. New text: There are two modes for intersection: strict and lax. How the mode is selected or indicated for the policy intersection is outside the scope of this specification.