- From: Stanley A. Klein <sklein@cpcug.org>
- Date: Fri, 29 May 2009 08:21:27 -0400 (EDT)
- To: "Robin Berjon" <robin@berjon.com>
- Cc: "Taki Kamiya" <tkamiya@us.fujitsu.com>, "'FABLET Youenn'" <youenn.fablet@crf.canon.fr>, public-exi@w3.org, fujisawa.jun@canon.co.jp
One feature that might help in many contexts is the capability to encode integers and floats as bit representations rather than their character equivalents usually provided in XML. I didn't notice this feature in the EXI specification, but I think it would be a useful "standard specialized" codec. Is it there and I missed it, or how do you achieve the bit encoding of the integers and floats? Stan Klein On Fri, May 29, 2009 4:05 am, Robin Berjon wrote: > On May 29, 2009, at 02:59 , Taki Kamiya wrote: >> You also indicated that SVG schema is huge. >> (Maybe you can call it even small compared with Docbook schema, I >> suppose. ;-) >> >> You may want to separate the schema used for exchange from the more >> stringent, >> constraining schema used for validation. One simple schema may just >> declare >> element and attribute names so that their names get into the initial >> string >> table. You should be able to calibrate the schema by defining some >> element >> content as repeatable choice of child elements so that the generated >> grammar >> is of minimal size, as necessary. > > If you're willing to transform the document before encoding (in a way > that is unlikely to cause failure) you can also declare that <defs> is > the required first child of the root element, then fold all content > from other <defs> into it, plus all paint servers (linearGradient, > radialGradient, solidColor) as well as filter, mask, clipPath, etc., > and make all of those forbidden elsewhere (instead of able to appear > anywhere). > > You can also normalise the style attribute (removing it completely), > and kill most of the XLink attributes too. > > There's a lot that can be done! As Taki says, relish! > --
Received on Friday, 29 May 2009 12:22:00 UTC