1218 2005-04-06 20:53:58 +0000 Serialization uses 6-character error codes 2005-08-17 14:56:01 +0000 1 1 1 Unclassified XPath / XQuery / XSLT Serialization 1.0 Last Call drafts PC Windows XP CLOSED FIXED P2 minor --- 1 mike scott_boag public-qt-comments oldest_to_newest 3813 0 mike 2005-04-06 20:53:58 +0000 Serialization uses 6-character error codes. For consistency with the other specs, it should move to 8-character codes. Michael Kay 3703 1 scott_boag 2005-04-28 15:43:30 +0000 (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. 3707 2 scott_boag 2005-04-28 17:15:58 +0000 Accept change, with folding HL and XL into RE.