1829 – clarify whether URI escaping is affected by the normalization-form

This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 1829 - clarify whether URI escaping is affected by the normalization-form

Summary: clarify whether URI escaping is affected by the normalization-form

Status:	CLOSED FIXED

Alias:	None

Product:	XPath / XQuery / XSLT
Classification:	Unclassified
Component:	Serialization 1.0 (show other bugs)
Version:	Last Call drafts
Hardware:	All All

Importance:	P2 normal
Target Milestone:	---
Assignee:	Joanne Tong
QA Contact:	Mailing list for public feedback on specs from XSL and XML Query WGs

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2005-08-02 18:02 UTC by Joanne Tong
Modified:	2005-09-29 08:36 UTC (History)
CC List:	1 user (show)

See Also:

Attachments

Description Joanne Tong 2005-08-02 18:02:05 UTC

Original comment raised by Bjoern Hoehrmann 
[http://lists.w3.org/Archives/Public/public-qt-comments/2005Aug/0002.html]

It's not clear to me
that normalization-form has no impact on resource identifier escaping
... For example, with 

  escape-uri-attributes = no
  normalization-form = NFC

input such as

  <a href='Bjo&#x308;rn' ...

would yield in

  <a href='Bj&#xf6;rn' ...

With 

  escape-uri-attributes = yes
  normalization-form = NFC

however it would yield in, as I understand it,

  <a href='Bjo%CC%88rn' ...

which is not in NFC even though that has been requested. Also note that
RFC 3987 requires the result to be NFC-normalized under some circum-
stances, so I think this needs to be clarified in the draft.

Comment 1 Michael Kay 2005-09-29 08:36:34 UTC

Thanks for the comment. RFC 3987 appears to expect that the characters that
are escaped will be NFC-normalized (although there is room for
interpretation about the circumstances in which normalization takes place).
It therefore doesn't seem appropriate to take the serialization parameter
normalization-form into account, given that this can request values other
than NFC. Instead, we propose to change the rules for the
escape-uri-attributes parameter so that the value "yes" causes the following
two steps:

(a) normalize to NFC
(b) apply the escape-html-uri() function

If users want a different outcome then they can set escape-uri-attributes to
"no", and invoke the required processing themselves from within the
stylesheet.

In the expectation that you will accept this resolution, we are marking the
issue fixed and closed. If there is any problem with this, please re-open it.

Michael Kay
for the XSL and XQuery Working Groups