W3C home > Mailing lists > Public > xproc-dev@w3.org > August 2010

XProc test suite

From: temp <temp44@szm.sk>
Date: Mon, 23 Aug 2010 13:28:09 +0200 (CEST)
To: xproc-dev@w3.org
Message-Id: <20100823112809.D4A1329618@mail-mx-3.alinet.sk>
Hello,here
 are some comments about the official XProc test suite i have collected 
during development of my own XProc engine implementation. I would 
greatly appreciate some feedback.1. First, some comments about individual tests:data-002,
 data-006 - expected attribute value 'text/plain; charset="utf-8"' but 
was 'text/plain;charset=UTF-8' - the test should be modified so that it 
accepts both forms, AFAIK both are ok according to respective 
specificationserr-d0006-002 - should throw xd0007 instead, because the sequence appears on a non-sequence output rather than an inputerr-d0020-001 - should be moved into serialization directory, not relevant for engines not supporting serializationerr-primary-001
 - i cannot find a reason for xs0008 in the pipeline of this test, is it
 supposed to be the primary attribute on the p:identity input? isn't 
this attribute allowed by the spec?err-s0007-004
 - why is the difference by sequence an error? according to the spec 
(4.4) "As a convenience to authors, it is not an error if some 
subpipelines declare outputs that can produce sequences and some do 
not."err-s0009-003
 - why is the difference by sequence an error? according to the spec 
(4.6) "As a convenience to authors, it is not an error if an output port
 can produce a sequence in the initial subpipeline but not in the 
recovery subpipeline, or vice versa."err-s0027-001 - in this test, the default namespace is xmlns="http://xproc.org/ns/testsuite", thus it is used in determination of the option name in p:with-option, so {}:select (short form) and {http://xproc.org/ns/testsuite}:select (long form) are not the same option on the step, are they?err-s0039-00*
 - all this steps should be moved into serialization directory, not 
relevant for engines not supporting serializationhttp-request-003, http-request-009, http-request-010 - see comment for data-002 and data-006load-002
 - throws xc0027 when the engine uses a non-validating parser, since 
this test is required, does it mean any xproc engine implementation MUST
 use a validating parser?xslt-006 - should be moved to optional, because it requires xslt 2.02.
 It would be nice if you could provide the dictionary or schema or at 
least an example of the test suite results XML which is used to generate
 a test results page like http://tests.xproc.org/results/calumet/. Also it would be great if you could provide the transformation to generate the page itself from the results.3.
 What would I have to do if I wanted to register my own XProc 
implementation so that I can put up a result page like mentioned above 
to the official test suite page?Thanks in advance for your feedback.Regards
Mio




=== reklama ======================================

http://mail.szm.com - e-mail a priestor na www stranku zadarmo

http://webhosting.szm.com - domény a webhosting za najnižšie ceny

SZM.com používa COMDOM Antispam - www.comdomsoft.com 
Received on Monday, 23 August 2010 14:18:35 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 23 August 2010 14:18:35 GMT