headers
Lunjian Mu | 1 Dec 2005 06:52
Favicon

the status of chat document

Hi All,
    Who can tell me the status of documents:draft-niemi-simple-chat-03.txt. A new version will be published or not ?
 
Thanks and Best regards,
 
Lunjian Mu
_______________________________________________
Simple mailing list
Simple <at> ietf.org
https://www1.ietf.org/mailman/listinfo/simple
Permalink | Reply | 0 comments |
headers
Jari Urpalainen | 1 Dec 2005 08:56
Picon

Re: I-D ACTION:draft-ietf-simple-xml-patch-ops-00.txt

Hi all!

Changes  since the individual version:
-fixed a bug when replacing a comment or a PI node; a "< " character can 
be present within them, within text nodes it must be escaped
-clarified attribute value and text node replace behavior when the 
replacement text is empty
-added some conventions used in this memo which don't exist e.g. in the 
XPath 1.0 spec
-clarified that the root node of a document as well as the full XML 
prolog cannot be patched with XPath semantics
-absolute location paths in XPath selector values are allowed but not 
encouraged
-added a patch element type for text content patching. This is still 
somewhat controversial mostly because of ipr issues. However, it was 
just added in order to show how to use it if some application really 
wants/needs it. AFAIK vcdiff seems to be the most sane way to handle 
these, but does anybody know whether the ipr limits its usage only to 
e.g. rfc3229 ?
-did not include multi-select "msel" selector which could be used e.g. 
to remove multiple attributes or elements with one patch operation 
request. The reference implementation at 
<http://xmlpatch.sourceforge.net/> includes it, however. The possible 
nested element case has to be handled then, but it is mostly not 
included in the spec because I can't see enough motivation for it. If 
there's really need for it it can be done in an extension later. The 
same can be said e.g. about a move operation.

A couple of other nits here and there but I'd really appreciate some 
feedback/comments.
br,
Jari
Permalink | Reply | 0 comments |
headers
Chantal Ladouce | 1 Dec 2005 15:12
Picon

Wireless/WiFi Convergence Conference - Call for Papers

The Wireless/WiFi Convergence Conference will be held in Paris on May 16 to May 19, 2006

 

http://www.upperside.fr/wirelessconvergence2006/wwconvergence2006cfp.htm

 

It is still time to submit proposals. Organizers are looking for UMA papers.

 

_______________________________________________
Simple mailing list
Simple <at> ietf.org
https://www1.ietf.org/mailman/listinfo/simple
Permalink | Reply | 0 comments |
headers
Hisham Khartabil | 2 Dec 2005 12:27
Picon

WGLC: User Agent Capability Extension to PIDF (prescaps)

The WG chairs would like to start a Working Group Last Call on the  
following drafts:

http://www.ietf.org/internet-drafts/draft-ietf-simple-prescaps-ext 
-05.txt

This WGLC will end on December 16th, 2005.

Please send your comments to this mailing list and to the authors.

Thanks,
Hisham
Permalink | Reply | 0 comments |
headers
Burger, Eric | 5 Dec 2005 19:32

IMDN Issue #2: Date Stamp in IMDN

Add a date element to the IMDN.  Does anyone care?  I don't, so it goes
in unless someone besides me squeaks.
Permalink | Reply | 0 comments |
headers
Burger, Eric | 5 Dec 2005 19:33

IMDN Issue #4: Disposition-Notification-To

IETF 64 SIMPLE meeting consensus in room was to take out 3rd-party or
3rd-party transport notifications *for now*.

Proposal is to simply have the presence of a Disposition-Notification
header, leaving the possibility for adding a URI in the future (and
restoring the mechanism from the current draft).

Anyone need this functionality today?
Permalink | Reply | 0 comments |
headers
Burger, Eric | 5 Dec 2005 19:31

IMDN Issue #1: Security of IMDN

Proposal is that if the body of the message was encrypted or signed, the
IMDN MUST be encrypted or signed, otherwise it MAY be plain text.

Any dissent?
Permalink | Reply | 1 comment |
headers
Burger, Eric | 5 Dec 2005 20:05

IMDN Issue #5: "deleted" state

I had proposed dropping the deleted state, as it (1) did not make sense
to me in an IM context and (2) has a ton of privacy implications.

HOWEVER, it was mentioned that someone thought someone needed the
"deleted" disposition.  They thought they heard that someone in Paris
(IETF 63) said they needed it.

Speak now, or "deleted" will be deleted from the next draft.
Permalink | Reply | 0 comments |
headers
Cullen Jennings | 6 Dec 2005 06:17
Picon
Favicon
Gravatar

draft-ietf-simple-xml-patch-ops-00


I was somewhat surprised to see this as a WG item. When do we use this and
when do we use xcap?

I was also sort of wondering about how to deal with the issues of elements
that used name spaces inside of the data portion of attributes. For
example... 

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>
wrote:

> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the SIP for Instant Messaging and Presence
> 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 today's
>    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 (XPath)
>    selectors.  With the aid of these selector values and updated data
>    content a set of patches can then be applied to an existing initial
>    XML document.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-simple-xml-patch-ops-00.txt
> 
> 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
> message.  
> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
> 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
> http://www.ietf.org/shadow.html
> 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
> Internet-Draft.
> 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
> https://www1.ietf.org/mailman/listinfo/i-d-announce
Permalink | Reply | 4 comments |
headers
Robert Sparks | 6 Dec 2005 22:27
Favicon

Re: draft-ietf-simple-xml-patch-ops-00


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  
solution for
xcap-diff and the partial-* work based on the output of the patch bof  
and the
SIMPLE WG discussion in Vancouver. It went beyond its mandate  
including patch
operations for general text elements - this is something the group  
explicitly decided
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  
a very
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  
agreed to
in Vancouver.

RjS

>
> I was also sort of wondering about how to deal with the issues of  
> elements
> that used name spaces inside of the data portion of attributes. For
> example...
>
> 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>
> wrote:
>
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>> This draft is a work item of the SIP for Instant Messaging and  
>> Presence
>> 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  
>> today's
>>    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  
>> (XPath)
>>    selectors.  With the aid of these selector values and updated data
>>    content a set of patches can then be applied to an existing  
>> initial
>>    XML document.
>>
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-ietf-simple-xml-patch- 
>> ops-00.txt
>>
>> 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
>> message.
>> You can also visit https://www1.ietf.org/mailman/listinfo/I-D- 
>> announce
>> 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
>> http://www.ietf.org/shadow.html
>> 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
>> Internet-Draft.
>> 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
>> https://www1.ietf.org/mailman/listinfo/i-d-announce
>
> _______________________________________________
> Simple mailing list
> Simple <at> ietf.org
> https://www1.ietf.org/mailman/listinfo/simple
Permalink | Reply | 2 comments |

Gmane