|Re: CSV Resource implementation for EMF [message #1804498 is a reply to message #1804482]
||Wed, 27 March 2019 08:40
| Ed Willink
Registered: July 2009
Your goal is presumably to make spreadsheet queries easy ... I don't think you achieve that.
The model has three dimensions of iteration: instances, slots, elements. You align these with spreadsheet lines, columns, ??magic-separation?? which may make visual sense but consider:
I want to query all the names. In your organisation, the query must iterate across the lines and columns to find "name" features.
In a more pragmatic, one line per element, the query locates all the column 2's with a "name" value, then selects all the corresponding column 3's.
With each element on a different line you avoid the complexity that horrible CDATA may be in many different columns, or multi CDATA in a single cell; easier if always a separate column 3 cell per value.
With each element on a different line, you have fixed purposes for each column, and can add meta-columns such as isCDATA. Users can add their own analysis columns.
(Have you checked the Spreadsheet publications of the Epsilon team?)
Powered by FUDForum
. Page generated in 0.02396 seconds