Re: [Simple] [Technical Errata Reported] RFC5261 (3477)

Erik Wilde <dret@berkeley.edu> Tue, 05 February 2013 13:17 UTC

Return-Path: <dret@berkeley.edu>
X-Original-To: simple@ietfa.amsl.com
Delivered-To: simple@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 786BE21F85D6 for <simple@ietfa.amsl.com>; Tue, 5 Feb 2013 05:17:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eZ1sxbBaUYr2 for <simple@ietfa.amsl.com>; Tue, 5 Feb 2013 05:17:48 -0800 (PST)
Received: from cm06fe.IST.Berkeley.EDU (cm06fe.IST.Berkeley.EDU [169.229.218.147]) by ietfa.amsl.com (Postfix) with ESMTP id 9512621F85AC for <simple@ietf.org>; Tue, 5 Feb 2013 05:17:48 -0800 (PST)
Received: from 46-126-158-51.dynamic.hispeed.ch ([46.126.158.51] helo=dretair.local) by cm06fe.ist.berkeley.edu with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.76) (auth plain:dret@berkeley.edu) (envelope-from <dret@berkeley.edu>) id 1U2iP7-0006SS-Ln; Tue, 05 Feb 2013 05:17:42 -0800
Message-ID: <5111066E.8000400@berkeley.edu>
Date: Tue, 05 Feb 2013 14:17:34 +0100
From: Erik Wilde <dret@berkeley.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: Bjoern Hoehrmann <derhoermi@gmx.net>
References: <20130205102514.EC98AB1E002@rfc-editor.org> <t4q1h81mvm2vt7vn5posa7bl5t217gliod@hive.bjoern.hoehrmann.de>
In-Reply-To: <t4q1h81mvm2vt7vn5posa7bl5t217gliod@hive.bjoern.hoehrmann.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Tue, 12 Feb 2013 08:08:30 -0800
Cc: Bas de Bakker <bas.debakker@emc.com>, Cornelia Davis <cornelia.davis@emc.com>, jari.urpalainen@nokia.com, Mark Nottingham <mnot@mnot.net>, Norman Walsh <norman.walsh@marklogic.com>, simple@ietf.org, hisham.khartabil@gmail.com, Jonathan Robie <jonathan.robie@emc.com>, RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [Simple] [Technical Errata Reported] RFC5261 (3477)
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/simple>
List-Post: <mailto:simple@ietf.org>
List-Help: <mailto:simple-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Feb 2013 13:17:49 -0000

hello bjoern.

thanks a lot for the quick feedback!

On 2013-02-05 12:16 , Bjoern Hoehrmann wrote:
> * RFC Errata System wrote:
>> Notes
>> -----
>> The original text is not easy to understand, but seems to assume that
>> an unprefixed name in XPath 2.0 matches both unprefixed names, and
>> prefixed ones that have the same namespace than the default namespace of
>> the XPath static context. This is not the case: Matching depends on how
>> the "default element/type namespace" of the XPath static context is
>> defined, and then matches either namespace-less elements, or those in
>> the "default element/type namespace", but never both. This context,
>> however, is defined by the XPath itself, not by the document. Thus, it
>> can be set externally and could be set to the diff document's default
>> namespace (if there is one). In that case, XPath 2.0 can be used to
>> evaluate XML Patch selectors.
>
> Indeed, see <http://www.w3.org/TR/xpath20/#node-tests>;, 3rd paragraph.
> (I do note that this is not the only difference between XPath 1.0 and
> XPath 2.0, so the conclusion that then XPath 2.0 can be used to evalu-
> ate XML Patch selectors is not necessarily correct, especially if it
> cannot be assumed that defaults like "Default element/type namespace"
> cannot be assumed to be chosen to maximise compatibility. But that is
> out of scope of the Original Text this item is concerned with.)

yes, you're right that this is not necessarily a correct conclusion. it 
would be really great to figure this out, though, because the 
convenience of being able to use a standard implementation cannot be 
overstated. i am writing 
http://tools.ietf.org/html/draft-wilde-xml-patch-01 which is intended to 
be based on RFC 5261 (which is why am reading it very closely now), and 
it would be great to have an implementation hints section (i am 
currently writing one) that would clearly tell implementers what they 
can and cannot use. it's bad enough that you cannot use a standard XPath 
1.0 implementation; it would be great if at least XPath 2.0 would be 
usable. any insights would be greatly appreciated, i think i have to 
look closer into the XPath subset of the RFC and see whether that 
contains anything where XPath 1.0 and 2.0 differ.

in the interest of readability, 
http://tools.ietf.org/html/draft-wilde-xml-patch-01#appendix-B now has 
an ABNF for the grammar in RFC 5261, where it's only defined in the XSD. 
i have also filed an erratum about the grammar, because it allows 
"id()", which never selects anything:

http://www.rfc-editor.org/errata_search.php?rfc=5261&eid=3458

thanks again and cheers,

dret.

-- 
erik wilde | mailto:dret@berkeley.edu  -  tel:+1-510-2061079 |
            | UC Berkeley  -  School of Information (ISchool) |
            | http://dret.net/netdret http://twitter.com/dret |