Robert Sparks <rjsparks <at> nostrum.com>
2005-12-06 21:27:44 GMT
On Dec 5, 2005, at 11:17 PM, Cullen Jennings wrote:
> I was somewhat surprised to see this as a WG item. When do we use
> this and
> when do we use xcap?
This draft is intended to be what the group agreed to adopt as the
xcap-diff and the partial-* work based on the output of the patch bof
SIMPLE WG discussion in Vancouver. It went beyond its mandate
operations for general text elements - this is something the group
to not try to tackle by my memory.
I can see your confusion given that the draft doesn't reference
partial at all.
Jari - could you provide a revision quicky that includes a section
pointing to how this
would be used with xcap and with partial?
All - comment on the text modifying proposal quickly. Unless there is
strong "Oh yeah - we all want to do this this way", and soon, I will
ask Jari to remove
this mechanism from this draft and return to exactly the scope we
> I was also sort of wondering about how to deal with the issues of
> that used name spaces inside of the data portion of attributes. For
> if I have namesace xmlns:z="urn:foo"
> then I have sel="z:doc"
> Would I ever have the case where the some xml parser library
> changed my
> namespace to xmlns:z="urn:foo" (it would do this perhaps because x was
> already in use)? If this happened, it seems like the "z:doc" would
> not get
> changed to "x:doc" and things would break badly.
> Thoughts? Is this a problem or is it all avoided some how?
> On 11/30/05 12:50 PM, "Internet-Drafts <at> ietf.org" <Internet-
> Drafts <at> ietf.org>
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> This draft is a work item of the SIP for Instant Messaging and
>> Leveraging Extensions Working Group of the IETF.
>> Title : An Extensible Markup Language (XML) Patch
>> Operations Framework Utilizing XML Path
>> Language (XPath) Selectors
>> Author(s) : J. Urpalainen
>> Filename : draft-ietf-simple-xml-patch-ops-00.txt
>> Pages : 21
>> Date : 2005-11-30
>> Extensible Markup Language (XML) documents are widely used as
>> containers for the exchange and storage of arbitrary data in
>> systems. Updates to this data require transporting of the
>> entire XML
>> document between hosts, unless there's a mechanism that allows
>> exchanging only the updates of XML documents. This document
>> describes an XML patch framework utilizing XML Path language
>> selectors. With the aid of these selector values and updated data
>> content a set of patches can then be applied to an existing
>> XML document.
>> A URL for this Internet-Draft is:
>> To remove yourself from the I-D Announcement list, send a message to
>> i-d-announce-request <at> ietf.org with the word unsubscribe in the
>> body of the
>> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-
>> to change your subscription settings.
>> Internet-Drafts are also available by anonymous FTP. Login with
>> the username
>> "anonymous" and a password of your e-mail address. After logging in,
>> type "cd internet-drafts" and then
>> "get draft-ietf-simple-xml-patch-ops-00.txt".
>> A list of Internet-Drafts directories can be found in
>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>> Internet-Drafts can also be obtained by e-mail.
>> Send a message to:
>> mailserv <at> ietf.org.
>> In the body type:
>> "FILE /internet-drafts/draft-ietf-simple-xml-patch-ops-00.txt".
>> NOTE: The mail server at ietf.org can return the document in
>> MIME-encoded form by using the "mpack" utility. To use this
>> feature, insert the command "ENCODING mime" before the "FILE"
>> command. To decode the response(s), you will need "munpack" or
>> a MIME-compliant mail reader. Different MIME-compliant mail readers
>> exhibit different behavior, especially when dealing with
>> "multipart" MIME messages (i.e. documents which have been split
>> up into multiple messages), so check your local documentation on
>> how to manipulate these messages.
>> Below is the data which will enable a MIME compliant mail reader
>> implementation to automatically retrieve the ASCII version of the
>> Content-Type: text/plain
>> Content-ID: <2005-11-30114220.I-D <at> ietf.org>
>> I-D-Announce mailing list
>> I-D-Announce <at> ietf.org
> Simple mailing list
> Simple <at> ietf.org