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

Bjoern Hoehrmann <derhoermi@gmx.net> Tue, 05 February 2013 11:17 UTC

Return-Path: <derhoermi@gmx.net>
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 23FB921F8716 for <simple@ietfa.amsl.com>; Tue, 5 Feb 2013 03:17:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.932
X-Spam-Level:
X-Spam-Status: No, score=-3.932 tagged_above=-999 required=5 tests=[AWL=-1.333, BAYES_00=-2.599]
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 odjW+p8s51Ox for <simple@ietfa.amsl.com>; Tue, 5 Feb 2013 03:17:04 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) by ietfa.amsl.com (Postfix) with ESMTP id 03D1921F86F0 for <simple@ietf.org>; Tue, 5 Feb 2013 03:17:03 -0800 (PST)
Received: from mailout-de.gmx.net ([10.1.76.1]) by mrigmx.server.lan (mrigmx002) with ESMTP (Nemesis) id 0M8ntS-1UEkGQ3P3c-00CCqR for <simple@ietf.org>; Tue, 05 Feb 2013 12:17:02 +0100
Received: (qmail invoked by alias); 05 Feb 2013 11:17:02 -0000
Received: from p5B062596.dip.t-dialin.net (EHLO netb.Speedport_W_700V) [91.6.37.150] by mail.gmx.net (mp001) with SMTP; 05 Feb 2013 12:17:02 +0100
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX19pHBcSZYJpvIz+NVXeGCPZpeUw72MvqVJ5XDDfru iAUfA6IPwWe5Nz
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: RFC Errata System <rfc-editor@rfc-editor.org>
Date: Tue, 05 Feb 2013 12:16:58 +0100
Message-ID: <t4q1h81mvm2vt7vn5posa7bl5t217gliod@hive.bjoern.hoehrmann.de>
References: <20130205102514.EC98AB1E002@rfc-editor.org>
In-Reply-To: <20130205102514.EC98AB1E002@rfc-editor.org>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 0
Cc: dret@berkeley.edu, jari.urpalainen@nokia.com, simple@ietf.org, hisham.khartabil@gmail.com
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 11:17:05 -0000

* RFC Errata System wrote:
>Original Text
>-------------
>In XPath 2.0, a "bar" selector
>not only matches an unqualified <bar> element, but also matches a
>qualified <bar> element that is in scope of a default namespace
>declaration.  In contrast, in this specification, a selector without
>a prefix only matches one element, and it may match an element with
>or without a prefix but only if the namespace it's qualified with (or
>none) is an exact match.

>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.)
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/