1. XCAP-Diff Jonathan Rosenberg Cisco Systems

2. Changes • Split into two documents • Draft-ietf-simple-xcap-diff: wrapper format that contains etags and document URI, extensible to indicate what changes • This is all that is needed for -08 xcap • May not need this at all…. • Draft-rosenberg-simple-xcap-change-log • Specifies changes to xcap document • Fixes problem Jari pointed out about XML wrapping and CDATA based on XML directorate input

3. Results from XML-Patch • Will be using patch-ops for xcap-diff • But still want to separate the change parts from the etag wrapper if needed • Plan of attack • Discard draft-rosenberg-simple-change-log – now only insurance in case W3C or others puke on patch-ops • XCAP-diff to use patch-ops again • As a future extension if we need a separate shim still

4. Approach I: <xs:any ns=“##other”/> - there now Requires two namespaces once extended Need to mandate patch-ops else have a negotiation mechanism for change format Approach II: Revise schema itself and include patch-ops directly as children using chameleon namespace Proposal If we agreed to xcap change proposal, do approach II – no schema revision required, just hold xcap-diff till done If we didn’t agree, do approach I Extending XCAP-Diff