I like Cube - it's extremely useful for deriving interesting information once you have the "events" that they're talking about (something similar to what I have

I like Cube - it's extremely useful for deriving interesting information once you have the "events" that they're talking about (something similar to what I have here). What I'm trying to do here with SLOPE is something much more basic though. One could certainly represent time as a JSON object, but as I mentioned near the end of the post, it could even be represented as a single string: > start;length;offset1,offset2...;period;end With any of the semicolon delimited portions removed in order. So instead of using a typical timestamp in YYYY-MM-DDTHH:MM:SSTZ, you use a SLOPE string instead. It makes it much more easy to compute across all situations irrespective of the platform being used.