It's ironic your defending the bias of how this article was posted to slashdot when zune is irrelevant, without realizing the bias of slashdot towards MS being the reason why this article got posted.
Extraction of business rules from legacy (probably COBAL) system.
COBAL, exactly what I was thinking. It reminds me of an article that was on./ about a year ago talking about how California couldn't find anyone to maintain/upgrade their payroll system becuase they couldn't find any COBAL programmers.
I agree 100%. The article makes mention of dimensions and n-cubes, which is already synonymous with star schemas and OLAP cubes in the data warehousing/business intelligence world. To me this causes confusion as to understanding how exactly this Google Fusion works, or even what exactly it does. From looking at the Berkeley paper you linked, I don't see any connection between Dataspaces and OLAP cubes tbh.
Slashdot Mirror
It's ironic your defending the bias of how this article was posted to slashdot when zune is irrelevant, without realizing the bias of slashdot towards MS being the reason why this article got posted.
Phase 1
Extraction of business rules from legacy (probably COBAL) system.
COBAL, exactly what I was thinking. It reminds me of an article that was on ./ about a year ago talking about how California couldn't find anyone to maintain/upgrade their payroll system becuase they couldn't find any COBAL programmers.
I agree 100%. The article makes mention of dimensions and n-cubes, which is already synonymous with star schemas and OLAP cubes in the data warehousing/business intelligence world. To me this causes confusion as to understanding how exactly this Google Fusion works, or even what exactly it does. From looking at the Berkeley paper you linked, I don't see any connection between Dataspaces and OLAP cubes tbh.