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 3197 - [XSLT] missing error code for section 16.2
Summary: [XSLT] missing error code for section 16.2
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XSLT 2.0 (show other bugs)
Version: Candidate Recommendation
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Michael Kay
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-04 14:28 UTC by Joanne Tong
Modified: 2006-07-02 03:12 UTC (History)
0 users

See Also:


Attachments

Description Joanne Tong 2006-05-04 14:28:38 UTC
The 2nd paragraph in section 16.2 (Reading Text Files) reads:

"The $href argument must be a string in the form of a URI. The URI must contain no fragment identifier, and must identify a resource that can be read as text. If the URI is a relative URI, then it is resolved relative to the base URI from the static context."

What is the error code if the URI contains a fragment identifier? 

This section of the spec contains the following 3 error codes which I believe do not apply:

[ERR XTDE1170] It is a non-recoverable dynamic error if a URI cannot be used to retrieve a resource containing text.
[ERR XTDE1190] It is a non-recoverable dynamic error if a resource contains octets that cannot be decoded into Unicode characters ...
[ERR XTDE1200] It is a non-recoverable dynamic error if the second argument of the unparsed-text function is omitted and the processor cannot infer the encoding ..
Comment 1 Michael Kay 2006-05-12 19:43:10 UTC
I have included this condition within the definition of error XTDE1170, since they seem closely related.
Comment 2 Michael Kay 2006-07-02 03:12:17 UTC
I am marking this closed; the agreed text appears in the June draft.