- From: <bugzilla@jessica.w3.org>
- Date: Tue, 31 Mar 2015 02:00:25 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20734 --- Comment #5 from Abel Braaksma <abel.braaksma@xs4all.nl> --- Sorry, it looks like my comment was about the file attribute, not the uri, as you said in comment#0, my bad. Looking more closely at it, I decided to do a quick search. In QT3 I find that both practices are used, for instance some examples with uri attribute relative are: fn-doc-24 through to fn-doc-37 UseCaseJSON origami environment fn-doc-available-4 and 4 Some others use an absolute URI. However, doing the same search on XT3, it's even worse. Total of 107 with a uri attribute and *all* of them have a relative uri (despite what is said in the XSD), including very old tests, see the document and collection tests for instance. This may not be relevant for the tests if the test itself does not use the URI for resource location, merely the file reference, but I agree it appears an erroneous, if not at least confusing, practice. I am not sure if we should attempt to fix these 107 items. I think they kind of behave equal to the 662 items *without* a URI, in that only the file location is known. I could, to remove the confusion, remove all these uri attributes, as they seem to have no relevance to the tests. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 31 March 2015 02:00:28 UTC