Spec for model/cube

Fiscal Data Package has a mapping object. This is very very handy for building a logical model out of the physical data sources when appropriate. This logical model can in turn be used to automate visualisations and data loaders, for example.

Actually, there is nothing particularly “Fiscal” about this mapping: it is simply an OLAP cube implementation with measures and dimensions. I think we could extract out the generic pattern and expose it as a spec for declaring a model/cube mapping for any tabular data package.

[rufuspollock]

WONTFIX. I’m going to close as wontfix for now and we can re-open if there is interest / need.

[ericbusboom]

Ah, Good question. I half-thought “user” was the wrong word when I wrote that … I should have said Creator and Wrangler, as described in this analysis model. So, it’s the people who are creating the dataset and the data dictionary, not the people who are defining what “weight” means.

I ask because I want to distinguish between a canonical representation of something on the descriptor, and an ideal user experience for “end users” who might generate a descriptor via a series of actions.

Yes, Absolutely. The definition of what “weight” is could be ( probably should be ) JSON.

I’ve updated one of my older specifications into a proposal for a semantic datatype category taxonomy. This is basically the system I’ve linked to previously, used in Ambry.