W3C home > Mailing lists > Public > public-mwts@w3.org > October 2009

http://dev.w3.org/2006/waf/widgets-digsig/tests/#automated-testing

From: Kai Hendry <hendry@aplix.co.jp>
Date: Thu, 15 Oct 2009 15:09:12 +0100
Message-ID: <b24851260910150709p14e2ad63w2beb0404357d090d@mail.gmail.com>
To: public-mwts <public-mwts@w3.org>
Cc: Frederick Hirsch <Frederick.Hirsch@nokia.com>, Marcos Caceres <marcosc@opera.com>
I had a quick go categorising tests:
http://dev.w3.org/2006/waf/widgets-digsig/tests/test-suite-unstable.xml

type=syntax syntactic tests
type=signature Signature value verification

http://lists.w3.org/Archives/Public/public-webapps/2009OctDec/0090.html



I was thinking would it be a worthwhile, to test the widget runtime
notices that all the signatures have the same IDREF? I don't see the
MUST for "MUST  use an IDREF value for the ds:Reference  URI
attribute," in
http://dev.w3.org/2006/waf/widgets-digsig/tests/ for whatever reason.


I need to prepare some tests that check for chaining, see:
http://wiki.webvm.net/wrtc/qa/

Reading http://www.w3.org/TR/widgets-digsig/ I understand OCSP and
chaining is entirely optional? So a valid widget runtime that say,
just verifies the SignatureValue is said to be compliant?


Thanks for looking,
Received on Thursday, 15 October 2009 14:09:47 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 15 October 2009 14:09:47 GMT