- From: Jo Rabin <jo@linguafranca.org>
- Date: Thu, 19 Apr 2007 23:35:04 +0100
- To: <public-mobileok-checker@w3.org>
- Message-ID: <00a801c782d2$fa719800$8000a8c0@Linguafrancam2>
Hi My action was to develop the schema for this, and apologies as it has taken me longer than expected. Well, given that you expect things to take longer than expected. It's very much based on the ideas we developed while batting examples back and forth between me and CTIC - and it's also taken into account the requirements we drew up into Dublin.[1] I know there's some stuff missing (e.g. CSS analysis for MEASURES) and Error examples. Hopefully not that much. [1] http://lists.w3.org/Archives/Public/public-mobileok-checker/2007Apr/att-0009 /Intermediate_Document_Format.svg I have really struggled with trying to work the HTTP in RDF stuff in. In the end, taking Nachos words a couple of weeks ago to heart - viz it can't be used as RDF if it is in an XML document, I thought the best thing was to take inspiration from that document, and copy it where possible. I have taken the opportunity to try to reduce the verbosity and to allow for single consistent XPATH expressions to extract items of interest to mobileOK. This is of course a decision that is personal and can be reversed. A couple of other points. a) this is an example doc and not a schema. I'll go about generating a schema and some documentation once there is some feedback and iteration. b) I wonder if it would be a good idea to separate out the http part (and possibly others) into standalone schemas? c) Error codes. We do need a system of allocating codes for errors, warns etc infos. Poss we should look at the validation engines and see what we need to represent before diving too deeply into this. d) I decided to call it moki. Provisionally. Jo
Attachments
- text/xml attachment: moki-example-20070419.xml
Received on Thursday, 19 April 2007 22:35:41 UTC