W3C home > Mailing lists > Public > xml-encryption@w3.org > September 2002

Re: Erratum to XML 1.0 spec to allow xml:lang=""

From: Martin Duerst <duerst@w3.org>
Date: Mon, 23 Sep 2002 17:54:52 +0900
Message-Id: <>
To: reagle@w3.org, Paul Grosso <pgrosso@arbortext.com>
Cc: w3c-i18n-ig@w3.org, XML Encryption <xml-encryption@w3.org>

[Reduced cross-posting]

At 10:25 02/09/20 -0400, Joseph Reagle wrote:

>The new text on the xml:lang is below (I didn't provide an actual formal
>reference to that document, but a link to the erratum.... (?) )
>    http://www.w3.org/Encryption/2001/Drafts/xmlenc-core/
>    $Revision: 1.242 $ on $Date: 2002/09/20 14:22:46 $ GMT by
>    ...
>    where Bongo's href is subsequently interpreted as
>    "http://example.org/example.xml". If this is not the correct URI,
>    Bongo should have been serialized with its own xml:base attribute. The
>    recommendation that xmlns="" be emitted to divorce the default
>    namespace of the fragment from the context into which it is being
>    inserted can not be made for the attributes xml:base, and xml:space.

What does it mean to say 'the recommendation that xmlns="" be emitted
cannot be made for xml:base and xml:space' ?  Better change to 'the
recommendation to use an empty attribute value ...'

>    (Error 41 of the XML 1.0 Second Edition Specification Errata clarifies
>    that an empty string value of the attribute xml:lang is considered as
>    if, "there is no language information available, just as if xml:lang
>    had not been specified".)
>    The interpretation of an empty value for these attributes

which attributes? all four? xml:base/space? xml:lang?

>is undefined
>    or maintains the contextual value.

'or maintains the contextual value' would be rather misleading
for xml:lang; an empty value explicitly breaks context (read inheritance).

>Consequently, applications SHOULD
>    ensure (1) fragments that are to be encrypted are not dependent on XML
>    attributes, or (2) if they are dependent and the resulting document is
>    intended to be valid [XML], the fragment's definition permits the
>    presence of the attributes and that they have non-empty values.

'and that they have non-empty values': this took me quite a while to
parse correctly. Maybe better ', and permits that these attributes
have non-empty values'.

Regards,   Martin.
Received on Monday, 23 September 2002 05:52:25 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:32:04 UTC