Re: Fwd: Possible Errata for SMIL2.0, SMIL Animation, and SVG 1.1 - attributeName and "default namespace"

Glenn's analysis and proposal look correct to me. It seems to me that is 
needed is a clarification within the SMIL2 errata.

Jon


At 04:44 PM 12/2/2002 +0100, Chris Lilley wrote:
>Content-Type: text/plain; charset=ISO-8859-15
>X-MIME-Autoconverted: from 8bit to quoted-printable by 
>inner-relay-1.corp.adobe.com id gB2FjRKX026247
>
>This is a forwarded message
>From: Glenn A. Adams <glenn@xfsi.com>
>To: www-smil@w3.org, www-svg@w3.org
>Date: Sunday, December 1, 2002, 8:58:54 PM
>Subject: Possible Errata for SMIL2.0, SMIL Animation, and SVG 1.1 - 
>attributeName and "default namespace"
>
>===8<==============Original message text===============
>
>
>There appears to be a problem with the use of the term “default namespace” 
>in SMIL 2.0 Animation Modules [1], Section 3.4.1. In particular, in the 
>third paragraph under the heading ”The target attribute”, there appears 
>the following language:
>
>
>
>“if no CSS match is made (or CSS does not apply) the default namespace for 
>the target element will be matched”
>
>
>
>Also, in the fourth paragraph there appears:
>
>
>
>“If a target attribute is defined in an XML Namespace other than the 
>default namespace for the target element”
>
>
>
>The same problematic use of “default namespace” appears in SMIL Animation 
>[2], Section 3.1.
>
>
>
>Slightly different, but nevertheless problematic language appears in SVG 
>1.1 [3], Section 3.1, under the definition of the “XML” value for the 
>attributeType attribute:
>
>
>
>“This specifies that the value of "attributeName" is the name of an XML 
>attribute defined in the default XML namespace for the target element. 
>Note that if the value for attributeName has an XMLNS prefix, the 
>implementation must use the associated namespace as defined in the scope 
>of the animation element.”
>
>
>
>The problem with the above language is that it implies that unqualified 
>attributes are defined in the default namespace for a target element; 
>however, according to XMLNAMES [4], Section 5.{2,3}, attributes are not 
>defined in the default namespace; rather, they are defined either in the 
>global attribute partition (if qualified) or in a per-element-type 
>partition (if unqualified).  The relevant language from XMLNAMES is:
>
>
>
>Section 5.2, 1st paragraph, last sentence:
>
>
>
>“Note that default namespaces do not apply directly to attributes.”
>
>
>
>Section 5.3, paragraph before last example:
>
>
>
>“However, each of the following is legal, the second because the default 
>namespace does not apply to attribute names”
>
>
>
>Annex A.2, definition of per-element-type partitions:
>
>
>
>“Each type in the All Element Types Partition has an associated namespace 
>in which appear the names of the unqualified attributes that are provided 
>for that element. This is a traditional namespace because the appearance 
>of duplicate attribute names on an element is forbidden by XML 1.0. The 
>combination of the attribute name with the element's type and namespace 
>name uniquely identifies each unqualified attribute.”
>
>
>
>Annex A.2, last paragraph:
>
>
>
>“In XML documents conforming to this specification, the names of all 
>qualified (prefixed) attributes are assigned to the global attribute 
>partition, and the names of all unqualified attributes are assigned to the 
>appropriate per-element-type partition.”
>
>
>
>I would imagine that the intended meaning of the SMIL and SVG text quoted 
>above is something like:
>
>
>
>If the qname value of the attributeName attribute does not contain a 
>prefix (i.e., is a local name), then the named attribute is considered to 
>be a member of the per-element-type partition namespace of the 
>targetElement, and, as such, is associated with the XML namespace of the 
>target element [which is not necessarily associated with the namespace 
>value of the currently in-scope xmlns attribute, i.e., the default [XML] 
>namespace].
>
>
>
>The problem with the current text, is that it appears to read just the 
>opposite of the above; namely, that an unqualified attribute name in 
>attributeName is associated with the namespace value of the currently 
>in-scope xmlns attribute. Or, at least, this is how I read the current text.
>
>
>
>Regards,
>
>Glenn Adams
>
>
>
>[1] http://www.w3.org/TR/smil20/animation.html
>
>[2] http://www.w3.org/TR/smil-animation/
>
>[3] http://www.w3.org/TR/SVG11/animate.html#TargetAttributes
>
>[4] http://www.w3.org/TR/REC-xml-names/
>
>
>
>
>
>===8<===========End of original message text===========
>
>Yes, this is a problem.
>
>In other words, animating x could be read as animating svg:x
>and thus, having no effect on  the x attribute.
>
>--
>Best regards,
>  Chris                            mailto:chris@w3.orgReturn-Path: 
> <www-svg-request@w3.org>
>Received: from frink.w3.org (frink.w3.org [18.29.1.71])
>         by tux.w3.org (8.9.3/8.9.3) with ESMTP id PAA30356;
>         Sun, 1 Dec 2002 15:01:38 -0500
>Received: (from lists@localhost)
>         by frink.w3.org (8.11.6+Sun/8.11.6) id gB1JrSX10469;
>         Sun, 1 Dec 2002 14:53:28 -0500 (EST)
>Resent-Date: Sun, 1 Dec 2002 14:53:28 -0500 (EST)
>Resent-Message-Id: <200212011953.gB1JrSX10469@frink.w3.org>
>Received: from tux.w3.org (tux.w3.org [18.29.0.27])
>         by frink.w3.org (8.11.6+Sun/8.11.6) with ESMTP id gB1JrPA10418
>         for <www-svg@frink.w3.org>; Sun, 1 Dec 2002 14:53:25 -0500 (EST)
>Received: from wiggum.w3.org (wiggum.w3.org [18.29.0.213])
>         by tux.w3.org (8.9.3/8.9.3) with ESMTP id OAA29132;
>         Sun, 1 Dec 2002 14:53:24 -0500
>Received: by wiggum.w3.org (Postfix, from userid 65534)
>         id 89E812280B; Sun,  1 Dec 2002 14:53:24 -0500 (EST)
>Received: from tux.w3.org (tux.w3.org [18.29.0.27])
>         by frink.w3.org (8.11.6+Sun/8.11.6) with ESMTP id gB1JqaA10255
>         for <www-svg@frink.w3.org>; Sun, 1 Dec 2002 14:52:36 -0500 (EST)
>Received: from longxuyen.xfsi.com (smtp.xfsi.com [199.232.38.141])
>         by tux.w3.org (8.9.3/8.9.3) with ESMTP id OAA29003;
>         Sun, 1 Dec 2002 14:52:31 -0500
>content-class: urn:content-classes:message
>MIME-Version: 1.0
>Date: Sun, 1 Dec 2002 14:58:54 -0500
>X-Security: MIME headers sanitized on smtp-relay-1
>         See http://www.impsec.org/email-tools/procmail-security.html
>         for details. $Revision: 1.129 $Date: 2001-04-14 20:20:43-07
>Content-Type: multipart/alternative;
>         boundary="----_=_NextPart_001_01C29974.13924876"
>Message-ID: <7249D02C4D2DFD4D80F2E040E8CAF37C01973A@longxuyen.xfsi.com>
>x-mimeole: Produced By Microsoft Exchange V6.0.5762.3
>X-MS-Has-Attach:
>X-MS-TNEF-Correlator:
>Thread-Topic: Possible Errata for SMIL2.0, SMIL Animation, and SVG 1.1 - 
>attributeName and "default namespace"
>Thread-Index: AcKZdBON9hKE/ICoQZ67JzZA+4SzYA==
>From: "Glenn A. Adams" <glenn@xfsi.com>
>To: www-smil@w3.org, www-svg@w3.org
>X-caa-id: e5cd1307cb2835a43fe92825d309707cbc352b87
>Subject: Possible Errata for SMIL2.0, SMIL Animation, and SVG 1.1 - 
>attributeName and "default namespace"
>Resent-From: www-svg@w3.org
>X-Mailing-List: <www-svg@w3.org> archive/latest/3010
>X-Loop: www-svg@w3.org
>Sender: www-svg-request@w3.org
>Resent-Sender: www-svg-request@w3.org
>Precedence: list
>List-Id: <www-svg.w3.org>
>List-Help: <http://www.w3.org/Mail/>
>List-Unsubscribe: <mailto:www-svg-request@w3.org?subject=unsubscribe>
>Status:
>
>
>
>There appears to be a problem with the use of the term “default 
>namespace” in SMIL 2.0 Animation Modules [1], Section 3.4.1. In 
>particular, in the third paragraph under the heading ”The target 
>attribute”, there appears the following language:
>
>
>
>“if no CSS match is made (or CSS does not apply) the default namespace 
>for the target element will be matched”
>
>
>
>Also, in the fourth paragraph there appears:
>
>
>
>“If a target attribute is defined in an XML Namespace other than the 
>default namespace for the target element”
>
>
>
>The same problematic use of “default namespace” appears in SMIL 
>Animation [2], Section 3.1.
>
>
>
>Slightly different, but nevertheless problematic language appears in SVG 
>1.1 [3], Section 3.1, under the definition of the “XML” value for the 
>attributeType attribute:
>
>
>
>“This specifies that the value of "attributeName" is the name of an XML 
>attribute defined in the default XML namespace for the target element. 
>Note that if the value for attributeName has an XMLNS prefix, the 
>implementation must use the associated namespace as defined in the scope 
>of the animation element.”
>
>
>
>The problem with the above language is that it implies that unqualified 
>attributes are defined in the default namespace for a target element; 
>however, according to XMLNAMES [4], Section 5.{2,3}, attributes are not 
>defined in the default namespace; rather, they are defined either in the 
>global attribute partition (if qualified) or in a per-element-type 
>partition (if unqualified). Â The relevant language from XMLNAMES is:
>
>
>
>Section 5.2, 1st paragraph, last sentence:
>
>
>
>“Note that default namespaces do not apply directly to attributes.”
>
>
>
>Section 5.3, paragraph before last example:
>
>
>
>“However, each of the following is legal, the second because the default 
>namespace does not apply to attribute names”
>
>
>
>Annex A.2, definition of per-element-type partitions:
>
>
>
>“Each type in the All Element Types Partition has an associated 
>namespace in which appear the names of the unqualified attributes that are 
>provided for that element. This is a traditional namespace because the 
>appearance of duplicate attribute names on an element is forbidden by XML 
>1.0. The combination of the attribute name with the element's type and 
>namespace name uniquely identifies each unqualified attribute.”
>
>
>
>Annex A.2, last paragraph:
>
>
>
>“In XML documents conforming to this specification, the names of all 
>qualified (prefixed) attributes are assigned to the global attribute 
>partition, and the names of all unqualified attributes are assigned to the 
>appropriate per-element-type partition.”
>
>
>
>I would imagine that the intended meaning of the SMIL and SVG text quoted 
>above is something like:
>
>
>
>If the qname value of the attributeName attribute does not contain a 
>prefix (i.e., is a local name), then the named attribute is considered to 
>be a member of the per-element-type partition namespace of the 
>targetElement, and, as such, is associated with the XML namespace of the 
>target element [which is not necessarily associated with the namespace 
>value of the currently in-scope xmlns attribute, i.e., the default [XML] 
>namespace].
>
>
>
>The problem with the current text, is that it appears to read just the 
>opposite of the above; namely, that an unqualified attribute name in 
>attributeName is associated with the namespace value of the currently 
>in-scope xmlns attribute. Or, at least, this is how I read the current text.
>
>
>
>Regards,
>
>Glenn Adams
>
>
>
>[1] 
><http://www.w3.org/TR/smil20/animation.html>http://www.w3.org/TR/smil20/animation.html
>
>[2] http://www.w3.org/TR/smil-animation/
>
>[3] 
><http://www.w3.org/TR/SVG11/animate.html#TargetAttributes>http://www.w3.org/TR/SVG11/animate.html#TargetAttributes
>
>[4] http://www.w3.org/TR/REC-xml-names/
>
>