- From: <bugzilla@jessica.w3.org>
- Date: Tue, 08 Mar 2016 15:59:16 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29404 --- Comment #6 from Michael Kay <mike@saxonica.com> --- I think the rule for all the "resource access" functions should be that when the URI is invalid, the processor is allowed to raise an error but is not required to do so. The relevant functions are: doc doc-available collection uri-collection unparsed-text unparsed-text-lines unparsed-text-available json-doc Current handling of invalid URIs is as follows: doc: MAY raise FODC0005 doc-available: MUST raise FODC0005 collection: MUST raise FODC0004 uri-collection: MUST raise FODC0004 unparsed-text: no specific error; treated the same as "no resource found" unparsed-text-lines - same as unparsed-text unparsed-text-available - returns false json-doc - same as unparsed-text I propose to change doc-available to return false, aligning it with unparsed-text-available. I propose to change collection and uri-collection from MUST to MAY, for alignment with doc(). I propose no change for the unparsed-text family of functions; the cost of a change to make them more consistent with doc and collection is greater than the benefit. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 8 March 2016 15:59:19 UTC