- From: Miguel Garcia <miguel.garcia@fundacionctic.org>
- Date: Tue, 10 Jun 2008 12:36:03 +0200
- To: "Dominique Hazael-Massieux" <dom@w3.org>, "public-mobileok-checker" <public-mobileok-checker@w3.org>
Hi Abel and I are willing to help you updating the checker. We were just waiting until MobileOK Basic Tests 1.0 becomes LC again to start working on the checker. There is no much time to spend on it and we want to avoid working twice. By the way why should all ocurrences of a resource be anotated in moki?. I think the current behavior write into moki only once each resource is still valid we only need to take into account the new object processing rule. But this is just an idea without thinking deeply. Regards, Miguel >>-----Mensaje original----- >>De: public-mobileok-checker-request@w3.org [mailto:public-mobileok- >>checker-request@w3.org] En nombre de Dominique Hazael-Massieux >>Enviado el: martes, 10 de junio de 2008 12:13 >>Para: public-mobileok-checker >>Asunto: Help needed for bug fixes >> >> >>Hi, >> >>I've started to implement some of the changes needed to bring the >>checker in sync with the (to be released) new version of the mobileOK >>Basic spec. >> >>Without going into too much details for now (I can share them later if >>anyone is interested), it appears to be crucial for calculating >>PAGE_SIZE_LIMIT and EXTERNAL_RESOURCES that each image and object >>element in the moki document be annotated with its provenance - at the >>very least, whether it's coming from the primary document vs a >>stylesheet. >> >>Typically, an image should look like >><image> >> <retrieval>...</retrieval> >> <imageInfo type="image/gif"/> >> <instances> >> <source type="markup" line="x1" column="y1"/> >> <source type="markup" line="x2" column="y2"/> >> <source type="stylesheet" url="..." line="x3"/> >> </instances> >></image> >> >>Even if we don't get the level of details of lines, columns and urls >>(which would be ideal), at least knowing the number of times an image is >>called from the markup, and whether it is called from a style sheet >>would probably suffice to solve my problem. >> >>Making such a change is going to take me a lot of time due to my limited >>capabilities in Java; is anyone willing to help me on that one? >> >>Thanks, >> >>Dom >> >>
Received on Tuesday, 10 June 2008 10:36:57 UTC