The Multiple OCP Time Series resource represents a number of Overall Custom Period (OCP) compounded time series (plural) for multiple segments, multiple time periods and (potentially) a large number of measures. The Time Series resource, by contrast, provides data for only one segment, one time period and a limited number of measures - in any one request.
The key to understanding the Multiple OCP Time Series resource is knowing what data can be included in any one request, and how to formulate a query for that data. To this end, please see the documentation for the
multiple-ocp-time-series-query link relation, which contains the full details.
See the annotated representations below for details of how the requested information is contained in XML and JSON representations of the resource.
The Multiple OCP Time Series resource is exposed via XML and JSON representations, which have the following media type names:- > application/vnd.statpro.revolution.api.multiple-ocp-time-series+json
When a response is received from the web service with status 200 (= OK), the fact that the response contains a Multiple OCP Time Series resource representation is indicated by the presence of one of these two response headers:- > Content-Type: application/vnd.statpro.revolution.api.multiple-ocp-time-series+json; charset=utf-8
Content-Type: application/vnd.statpro.revolution.api.multiple-ocp-time-series+xml; charset=utf-8
The Multiple OCP Time Series resource links to the Service resource (and to itself). To do so, its resource representations use link relations:-
self link relation identifies the Multiple OCP Time Series resource link, for the same analysis. Note that, unlike almost all other
self links, the original query data is not contained in the link’s URI. For a new request, the query data must be included in the POSTed entity body.
service link relation identifies the Service resource link.
Looking at the JSON and XML resource representations below, there is seeming redundancy in that a time period’s start and end dates are duplicated in its contained
e attributes (to use XML terminology). The reason for this is that the representations follow the convention used by the Time Series resource in which the time period’s start and end dates are given, and the individual, periodic data points also have explicit start and end dates (as they must do). If the Multiple OCP Time Series resource representations look confusing, it is only because any given time period just has one periodic data point. When considering an
ocp data point, the contents of its
e attributes (‘members’ in JSON) must be considered to be definitive.
Last updated: September 2014