Re: [widgets] Interface published
2009/11/30 Robin Berjon ro...@berjon.com: widget.getItem(name) Revolutionary? Well, if you're in business selling keyboards and RSI relief, maybe. I thought it might save on DOM pollution. I have been playing with a debugger and the global vars passed between the Web runtime and debugger are outrageously bloated. There isn't a standard mapping from XML to JSON, but there have been experiments mapping the Infoset to JSON. Good luck using that here! Loads of PHP developers write something like: ? $s = simplexml_load_file(rawurlencode(config.xml)); echo json_encode($s); ? Though it looks pretty darn ugly. We could expose more things, but no one asked for them. If people ask for them, we can expose them in 1.1. It's not complicated. Well it is complicated when you think you have to wait until all the people upgrade to the next version in order to expose something new. Though, I can't think of a Debian package that relies on the debian/control file for anything during runtime. Please consider my comments as resolved.
Re: [widgets] Interface published
Some comments: http://dabase.com/blog/Widget_mapping_quirks/ Do I need to send them inline? I do prefer the Web since I can keep it better upto date. Kind regards,
Re: Implementation of the widget signing spec
Please try your signed widgets on http://test.webvm.net/ Example signed widget: http://static.webvm.net/example.wgt Example root CA: http://bondisdk.limofoundation.org/qa/keys/example.pub http://bondisdk.limofoundation.org/qa/keys/example.p12 with keystore password 'secret'
Re: Widget DigSign: Example of a distributor signature document is buggy
Hopefully further (correct) examples are here: http://dev.w3.org/2006/waf/widgets-digsig/tests/ http://dev.w3.org/2006/waf/widgets-digsig/tests/test-suite-unstable.xml Review is very welcome,
Re: [widgets] Draft Agenda for 2 July 2009 Voice Conference
2009/7/1 Arthur Barstow art.bars...@nokia.com: b. Dig Sig testing - call for inputs for testable assertion list Yesterday I was dabbling with openssl and xmlsec1: http://www.aleksey.com/pipermail/xmlsec/2009/008686.html Still trying to come up with a helloworld example where I (the author) sign with a private key and verify the widget using a self-signed certificate. I'll get onto all the chaining distributor stuff once I can figure out the basics I hope. I'll try join the call. Kind regards,
Re: [widgets] dig sig RelaxNG schema
Woops. The validator error messages go away when the ... are removed from the DigestValues. http://www.w3.org/TR/widgets-digsig/#example Attached is a signature1.xml template which validates to http://www.w3.org/2007/xmlsec/Drafts/xmldsig-rngschema/ with rnv for me at least. :) ?xml version=1.0 encoding=UTF-8? Signature xmlns=http://www.w3.org/2000/09/xmldsig#; Id=DistributorASignature SignedInfo CanonicalizationMethod Algorithm=http://www.w3.org/2006/12/xml-c14n11/ SignatureMethod Algorithm=http://www.w3.org/2001/04/xmldsig-more#rsa-sha256/ Reference URI=config.xml DigestMethod Algorithm=http://www.w3.org/2001/04/xmlenc#sha256/ DigestValue/DigestValue /Reference Reference URI=index.html DigestMethod Algorithm=http://www.w3.org/2001/04/xmlenc#sha256/ DigestValue/DigestValue /Reference Reference URI=icon.png DigestMethod Algorithm=http://www.w3.org/2001/04/xmlenc#sha256/ DigestValue/DigestValue /Reference Reference URI=#prop DigestMethod Algorithm=http://www.w3.org/2001/04/xmlenc#sha256/ DigestValue/DigestValue /Reference /SignedInfo SignatureValue/SignatureValue KeyInfo X509Data X509Certificate/X509Certificate /X509Data /KeyInfo Object Id=prop SignatureProperties xmlns:dsp=http://www.w3.org/2009/xmldsig-properties; SignatureProperty Id=profile Target=#DistributorASignature dsp:Profile URI=http://www.w3.org/ns/widgets-digsig#profile/ /SignatureProperty SignatureProperty Id=role Target=#DistributorASignature dsp:Role URI=http://www.w3.org/ns/widgets-digsig#role-distributor/ /SignatureProperty SignatureProperty Id=identifier Target=#DistributorASignature dsp:Identifier07425f59c544b9cebff04ab367e8854a/dsp:Identifier /SignatureProperty /SignatureProperties /Object /Signature
[widgets] dig sig RelaxNG schema
Using http://bondi.omtp.org/1.0/security/xmldsig-core-schema.rnc and
rnv [1] I've been trying to validate the example:
http://www.w3.org/TR/widgets-digsig/#example
Firstly does widgets-digsig have it's own grammar.rnc? I have not been
able to find one.
Using xmldsig-core-schema.rnc I ran into a couple of problems. Firstly
I had to alter:
Object.ANY = (element * {Object.ANY}|attribute * {text}|text)*
To accept the new elements introduced by
http://www.w3.org/TR/xmldsig-properties/
Also the xmldsig-core-schema.rnc seems sensitive to element order. So
I made a change to the rnc to get the example signature1.xml to
validate:
-Signature.attlist, SignedInfo, SignatureValue, KeyInfo?, Object*
+Signature.attlist, SignedInfo, Object*, SignatureValue, KeyInfo?
Or perhaps the order of the example is incorrect?
Be great to see more fully worked examples. An author-signature.xml
example would be good.
Kind regards,
[1] http://www.davidashen.net/rnv.html
http://dev.w3.org/2006/waf/widgets/#the-widget-element height and width default values
Suggestion for http://dev.w3.org/2006/waf/widgets/#the-widget-element When the value is missing or invalid, the widget user agent will assume the value 300. And perhaps reference http://dev.w3.org/2006/waf/widgets/#step-3-set-the-configuration-defaults Was wondering how you came up with 150x300 as the default size for a widget. How does that work for scalability and what not? Perhaps pixel definitions are scalable in reality nowadays by UAs and that's just an indicator of dimensions, 1:2? This might be addressed in R16 http://www.w3.org/TR/widgets-reqs/#visual but I don't quite understand it. Is there an example? Thanks guys,
Widget testing
Hey guys, I have an action to tell you what I've been upto WRT widgets http://www.w3.org/2008/11/04-mwts-minutes.html#action02 I've started working one day a week on widget testing. My own git repo is here: http://git.webvm.net/?p=wgtqa and it will move to a W3C CVS soon. I've come across a couple of issues which I've mailed Marcos already about. Though I'll paste them in here just in case: Subject: http://dev.w3.org/2006/waf/widgets/#the-license Having a optional URI or href whatever for the license would be good. Seems to be some inconsistency between src, uri, url, href btw that you can easily pick up in the relaxng scheme. http://dev.w3.org/2006/waf/widgets/#the-author xml:lang is not needed and it's not in your relaxng schema besides. Subject: http://dev.w3.org/2006/waf/widgets/#the-widget0 Bit confused by its:dir on widget, name, description, author etc. The RelaxNG compact schema uses the bdo element and so does HTML5 so can't we just rock with that? http://git.webvm.net/?p=wgtqa;a=blob;f=widget.rnc I've also written a little widget validation tool, which uses my updated (probably wrong) schema (widget.rnc). Try foo.wgt out like so: curl -F [EMAIL PROTECTED] http://wgt.webvm.net/ If you have any comments or you'd like to help us out over at http://www.w3.org/2005/MWI/Tests/ then please get in touch. I'm also on IRC as 'hendry'. Enjoy the weekend,
