W3C home > Mailing lists > Public > public-qt-comments@w3.org > March 2004

Re: [F&O] Protocol language information

From: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Wed, 10 Mar 2004 15:08:46 +0100
To: "Ashok Malhotra" <ashokma@microsoft.com>
Cc: <public-qt-comments@w3.org>
Message-ID: <40531b6a.1444106655@smtp.bjoern.hoehrmann.de>

* Ashok Malhotra wrote:
>Thank you for your message
>http://lists.w3.org/Archives/Public/public-qt-comments/2004Feb/0147.html
>We discussed this at the joint meeting of the XML Query WG and the XSL
>WG last week.  The joint WGs 
>decided that no change was needed in the wording.  Applications are free
>to use, or not use, such protocol
>language information as they see fit.

I am not satisfied with this response. The current text only considers
the xml:lang attribute and specifically says the function returns false
if (ancestor-or-self::*/@xml:lang)[last()] returns an empty sequence,
this implies that implementations must not use such protocol information
which contradicts your decision and would thus require change. It would
also be necessary to discuss what fn:lang returns if there is no
xml:lang attribute and the protocol information specifies multiple
languages (which would be possible using the HTTP Content-Language
header) and what the specification considers protocol language
information.

I am not too concerned about how fn:lang works (though I worry about
complexity if protocol information is considered and inconsistency with
e.g. the :lang() pseudo-class in CSS if it is not considered...), but
the specification should say whether implementations MUST NOT/MAY/
SHOULD/MUST consider it.
Received on Wednesday, 10 March 2004 09:09:06 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 07:13:56 UTC