W3C home > Mailing lists > Public > xml-dist-app@w3.org > April 2000

Fwd: LOPT: serialization algorithm suggestions

From: Constantine Plotnikov <cap@mail.novosoft.ru>
Date: Fri, 14 Apr 2000 16:17:04 +0700
Message-ID: <38F6E210.370C1E4B@mail.novosoft.ru>
To: MOREAU Jean-Jacques <moreau@crf.canon.fr>
CC: Dan Connolly <connolly@w3.org>, Henrik Frystyk Nielsen <frystyk@microsoft.com>, David Burdett <david.burdett@commerceone.com>, "'Eric Prud'hommeaux'" <eric@w3.org>, Ken MacLeod <ken@bitsko.slc.ut.us>, xml-dist-app@w3.org
Hi!

1. Could you please reconsider serialization algorithm?
As for as I understand from your site the SOAP is starting 
point for LOPT development.

We had some problems with implementing soap protocol in java.
The algorithm require two passes for serialization and 
deserialization.

The basic idea I suggest is the same as in java and XMI 1.1
serialization algorithm.

When object is serialized, it is assgined id and it is written
as:
<Type id="id0" >
  // contents
</Type>

Later (in the body of the the element or or ), when reference is 
encountered, empty element with href is used.

<List t="i0">
  <Type id="i1" >
    <value>
      <Element id="i2">
        <parent>
          <Type href="i1"/>
        </parent>
      <Element id="i2">
    </value>
  </Type>
  <Type id="id0"/>
</List>

It allow single pass serialization/desirailaization and references 
to parent. I do not suggest to use exactly this representation
for protocol. For example XMI 1.1 like optimization for representation 
of values may be used. I just want to make (de)serialization simple and 
single pass.

2. Could you please include standard collection types in LOPT namespace.
I think there should be:
Map
List
Bag

There may be other like Array.

Constantine
Received on Friday, 14 April 2000 05:16:37 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:56 GMT