Sounds good. If this can get done in a few days, I guess we can hold up the release. Otherwise, I'd like to go ahead with the release, and pick this improvement up on the next one.
Cheers. -Marshall On 7/16/2016 6:55 AM, Peter Klügl wrote: > Hi, > > > yes, it's (b). Right now, the CAS Editor only supports XMI and XCAS I > far as I remember. No binary format is supported. > > > I am thinking about some utils class for CAS serialization in > uimaj-core. The read method should be somewhat generic (detecting the > format), the write method takes the format as argument. > > > This utils class can then be utilized in the CAS Editor (and also by > others) to read and write the CAS files (with the format it was read). > > > Best, > > Peter > > > Am 15.07.2016 um 20:35 schrieb Marshall Schor: >> 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 >> >
