Hi, I'm starting a separate thread on this :-)
We currently have the following kinds of serialized formats a) <only used for client-server communication>: various "delta" formats - these require the original CAS be available. b) various forms that can be saved to disk and reloaded. ---------- For (b), there are: - XCAS, XMI (these are xml based) - binary (plain, compressed form 4, form 6) - some compound forms using Java object serialization and encoding type systems as well ---------- The binary forms are "self-identifying" for deserialization, so one piece of deserializer code can "read" the format and pick the right deserializer. Is it correct to assume the request for enhancement from Peter for the CAS Editor is to have that support the various forms (b)? If so, which ones does it not support at the moment? -Marshall
