Hello Ray,
Thank you for a prompt reply and explanation. I see your point in encouraging use of your licensed component. By the way does it require licensing an ACIS kernel itself and implies any run-time fees/royalties ? Or is it rather a licensing a component with its API that enables just read/write and access to the data structure ? My need is very limited - to only access file contents - either directly (via a parser) or via some API. Royalties would be a blocking condition :-(.
I would appreciate if you could clarify this.
From initial prototyping based on available information, the file structure and entity contents seem to be well structured. The main problem I encountered and anticipate for a parser is that each new version of a format adds contents *inside* the existing record. This makes parser based on older version fail to read new files (as it considers next data part to belong to a further ENTITY subclass while it may belong to extended set of data for a given class). More robust approach would be to add new data as additional data which older-version-tailored parsers would safely ignor.
Roman
