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 1218 - Serialization uses 6-character error codes
Summary: Serialization uses 6-character error codes
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Serialization 1.0 (show other bugs)
Version: Last Call drafts
Hardware: PC Windows XP
: P2 minor
Target Milestone: ---
Assignee: Scott Boag
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-04-06 20:53 UTC by Michael Kay
Modified: 2005-08-17 14:56 UTC (History)
0 users

See Also:

Attachments

Description Michael Kay 2005-04-06 20:53:58 UTC 
Serialization uses 6-character error codes. For consistency with the other
specs, it should move to 8-character codes.

Michael Kay
Comment 1 Scott Boag 2005-04-28 15:43:30 UTC 
(In reply to comment #0)
> Serialization uses 6-character error codes. For consistency with the other
> specs, it should move to 8-character codes.
> 
> Michael Kay

XSLT and XPath classify their errors based on dynamic, static, or type errors. 
F&O classify their errors based on sections, eg. Arithmetic, datetime,
collation, etc.

Joanne suggested:

0001:  NR - normalization error
0003:  XL - well-formed XML
0004:  PM - parameter error
0005:  RE - invalid result
0006:  SU - not supported
0007:  SU - not supported
0008:  RE - invalid result
0009:  PM - parameter error
0010:  PM - parameter error
0011:  SU - not supported
0012:  RE - invalid result
0013:  SU - not supported
0014:  HL - invalid HTML
0015:  HL - invalid HTML
0016:  PM - parameter error

These seem a tad fine-grained to me.   I think I would fold HL and XL into RE.
Comment 2 Scott Boag 2005-04-28 17:15:58 UTC 
Accept change, with folding HL and XL into RE.