[MOBY-dev] Binary data streaming

[Dmitry Repchevsky]

Hello,

> About FastInfoSet it compress XML schema in binary data, is this correct? 
It's better to say that it compress (transform) entire XML infoset. 
(while XOP is extract binary infoset and then again assemble then into one)

> So the idea can be to compress the XML using this system to reduce the 
> bandwidth used, correct? 
Yes it is.

> But I cannot see the relation with xml include. 
It's easy - XInclude can not handle not textual data - only XML/plain-text
To use "disabled" XInclude to pass a reference into a custom parser is 
not better than using XLink...

On the other hand it is possible to use XInclude to include fastinfoset 
encoded XML automatically.
Another advantage would be to reference not to "some" resource, but to 
the entire "ontology" object that can be included into the place where 
it should be...
This way you don't even need to change a message itself: you pass your 
image by "value" (with XOP/MTOM attachment) or by XInclude reference 
where it is encoded by fastinfoset.
The final XML is the same! Parser just assembles such a message...

Dmitry

Sergio Ramirez Ramirez wrote:
> About FastInfoSet it compress XML schema in binary data, is this correct?
>
> So the idea can be to compress the XML using this system to reduce the 
> bandwidth used, correct?
>
> But I cannot see the relation with xml include.
>
> Dmitry Repchevsky wrote:
>>
>>> I mean that if you want  "to have control over how to treat the 
>>> referenced data" Xinclude allows this possibility, but at the same 
>>> time offers the possibility of handle them automatically.
>> I am afraid the only way to make it work is to have it always 
>> switched off...
>>
>> By the way, what is your opinion about FastInfoset???
>> Could it be used with XInclude?
>>
>> I mean that it compresses data very well (it transforms XML schema 
>> into ASN.1 and use BER encoding
>> If I have some ontology class with binary data (base64binary) and 
>> send this "Moby Object" as an XML, but using FastInfoset... for the 
>> traffic if would be virtually the same as it was "plain" binary stream.
>>
>> I mean that we can have say "BinaryImage" ontology object that is 
>> using "binary" primitive type.
>> Then instead of making an url into "http://mysite.com/image.jpg"
>> we make a reference into "http://mysite.com/image.xml"
>>
>> The latter could be included and processed automatically by XInclude, 
>> but if we enable FastInfoset for it - it will be sent as a binary 
>> data over a network...
>>
>> Just a few thoughts...
>>
>> Best wishes,
>>
>> Dmitry
>> _______________________________________________
>> MOBY-dev mailing list
>> MOBY-dev at lists.open-bio.org
>> http://lists.open-bio.org/mailman/listinfo/moby-dev
>>
>