- From: Abel Rionda <abel.rionda@fundacionctic.org>
- Date: Tue, 7 Aug 2007 14:21:01 +0200
- To: <public-mobileok-checker@w3.org>
- Message-ID: <09700B613C4DD84FA9F2FEA521882819024BD0AE@ayalga.fundacionctic.org>
Hi, In the first part of this mail there is summary of current status of CSS in XML implementation and the second part there are some questions about Regular expressions approach in order to make a comparison between both approaches. Please, feel free to add any comments or other issues to make the comparison more accurate. Current Status of CSS: CSS in XML This is the general stylesheet structure present in moki so far: <stylesheets> <stylesheet type="embedded"> <URI></URI> <CSSValidity valid="false"> /*CSS grammar errors*/ </CSSValidity> <styles> /*CSS in XML */ </styles> </stylesheet> <stylesheet type="external"> <URI></URI> <retrieval>...</retrieval> <CSSValidity valid="true"/> <styles> /*CSS in XML */ </styles> </stylesheet> </stylesheets> Current values of type attributte: Embedded This type is used for CSS stuff enclosed inside style tags elements in primary document. External This type is used for linked CSS (through link tag or xml pre-processing instruction) and imported CSS (with some recent changes made by Laura). Moki styles Block tag We are using SAC for making a writer of CSS and build a representation of CSS in XML. So far we have not a full serialization of CSS but an equivalent representation. For example: So far we have <selector>a:visited</selector> instead of <selector value="a" pseudo="visited"/> Possible changes or things pending to do: TOBEDISCUSSED Full Serialization Jo had said that it would be desirable having a full serialization. We think that is not very difficult to do, but do we really need this level of serialization to fulfil our tests? TODO Serialization of Inline Style This can be done adding a new stylesheet tag to moki (of type inline) with all the style attributes present in main document. TODO Line Number Adding a line number property to each serialized CSS property (This can be done during serialization). TODO: Deal with short hand properties (eg font into font-size, font-family....) TODO: Parsing out the values defined in properties into usable values Comparison between CSS in XML and Regular Expressions It would be very desirable if you can complete these issues in order to make a comparison. * Structure of moki We are not sure how is the final moki structure in this way. Can you include a sketch of stylesheets information moki? * Structure of Tests Currently we have two CSS tests (Measures and StyleSheetSupport) running made in a pure XSLT way based on CSS serialization How would be a skeleton of any of CSS test with Regular Expressions? * Line number How is reported the line number with this approach?
Received on Tuesday, 7 August 2007 12:21:27 UTC