[mmox] Requirements for new xxSD specification

[Catherine Pfeffer <[e-mail]>]

Infinity wrote:
> so my response would be:
>        1.a. can we look at the effect before making this change? my
> suspicion is that message sizes will be much more affected by turning
> on compressed content encoding than with the change from one DTD to
> another.

Of course. Whatever we come up with, it must meet the following requirements
:
1 - be easy to validate with a schema or DTD
2 - be easy to parse and transform  with XSLT and XPath
3 - have low "angle bracket tax" price to pay
(and that should be expressed as a precise "bloat ratio" relative to the
binary serialization for the same set of data)
4 - be future-proof, i.e. allow for things that have been identified as
missing, like lack of alternative sizes for integers and floats, and lack of
unsigned.

I also have a detail question/concern about the current LLSD serialization.
What is the intention on how to serialize big amounts of data, like an
avatar mesh or a PNG picture? Are they supposed to go into a big
<binary>...</binary> blob? Because, if that is true, the binary data encoded
so will have to be base64-encoded inside of the <binary> tags, and that's a
point that might make the whole XML serialization almost unusable, because
the angle bracket tax would probably become unacceptable in typical data
exchanges.

-- 
Cathy