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

Re: [Serial] > in processing instructions (qt-2004Nov0074-01)

From: Joanne Tong <joannet@ca.ibm.com>
Date: Sat, 12 Mar 2005 15:27:19 -0500
To: Bjoern Hoehrmann <derhoermi@gmx.net>, Laurens Holst <lholst@students.cs.uu.nl>
Cc: public-qt-comments@w3.org
Message-ID: <OF08E878AF.5BA4AE3C-ON85256FC2.006D4943-85256FC2.00705C89@ca.ibm.com>
Hi

>This seems to be the only optional serialization error, could
you clarify why serializers are not required to report it?

Thank-you for your response.

The XSL and XML Query Working Groups discussed the response [1] and we 
confirmed that the reason behind the original decision to make this error 
recoverable was to be consistent because there was another recoverable 
error just above the quoted text.  However, the resolution for 
qt-2004Feb0362-17 has removed that recovery option.   This error is now an 
unrecoverable serialization error.  The editorial comment [2] is thus not 
applicable.

I would appreciate if you could check the next public draft of the 
specification when it becomes available, and verify that I've correctly 
applied all the changes, and that they resolve this issue to your 
satisfaction.

Thanks

Joanne

[1]  
http://lists.w3.org/Archives/Public/public-qt-comments/2005Mar/0022.html
[2]  
http://lists.w3.org/Archives/Public/public-qt-comments/2005Mar/0044.html




Bjoern Hoehrmann <derhoermi@gmx.net> 
03/08/05 03:07 PM

To
Joanne Tong/Toronto/IBM@IBMCA
cc
public-qt-comments@w3.org
Subject
Re: [Serial] > in processing instructions (qt-2004Nov0074-01)






* Joanne Tong wrote:
>Thank you for submitting this comment.  The XSL and XML Query Working 
>Groups discussed the comment and have agreed add a serialization error. 
>The new text is:
>
>[...]
>It is a serialization error [err:SE0015] to use the HTML output method 
>when > appears within a processing instruction in the data model instance 

>being serialized. The serializer MAY signal the error, but is not 
REQUIRED 
>to do so. If it does not signal the error, it MAY copy the offending 
>characters into the serialized output, creating HTML which may be invalid 

>or parse in an unexpected way.
>[...]
>
>May I ask you to confirm that this response is acceptable to you?

This seems to be the only optional serialization error, could
you clarify why serializers are not required to report it?
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de
68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 
Received on Saturday, 12 March 2005 20:28:41 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 March 2012 18:14:37 GMT