Abstract: Embodiments are directed to providing a plurality of data provisioning tiers for datasets and to throttling access to dataset data based on the dataset's data provisioning tiers. In an embodiment, a computer system receives an input that specifies a maximum number of queries that a user is allowed to perform on a given dataset over a specified period of time. The computer system generates data provisioning tiers for the dataset based on the received input. Each data provisioning tier indicates a maximum number of queries that the user is allowed to perform on a given dataset over a specified period of time. The computer system also applies the generated data provisioning tiers to the dataset so that the user is limited to the maximum number of queries specified in the data provisioning tier.

Abstract: Semantic categorization of data includes submitting obtained data values to a data enhancement service which has a semantic criterion for incoming data. A response from the service indicates whether the submitted data values meet the criterion, and is used to assign a likelihood that the values belong to a semantic category matching the criterion. Other semantic categorization operations do not necessarily use a data enhancement service. Some are based on which device was used to collect the data values, on a subject heading in which data was published, and/or on syntactic patterns. A semantic taxonomy shows semantic categorizations for one or more datasets and connections between datasets, possibly filtered per user request. Different versions of the taxonomy are stored for respective different users. Similarity between the data values can be assessed using semantic categorization. Taxonomies can be federated to allow exploration and understanding across multiple repositories.

Abstract: Systems and methods for providing and utilizing a query formulation service are described herein. In accordance with certain embodiments, an application is configured to obtain data from a target data source by interacting with a data service that makes data from a plurality of data sources available, each data source supporting a different method of query formulation. To obtain data from the target data source, the application requests a query formulation user interface (UI) associated with the target data source from a query formulation service and embeds the requested query formulation UI when it is received from the query formulation service. A user of the application then interacts with the embedded query formulation UI to formulate a query that is suitable for obtaining data from the target data source and the application sends the query to the data service for execution against the target data source.

Abstract: Verifying a translation middleware piece. A first request is provided to a front end user service using a protocol appropriate for the front end user service, including a translation middleware piece. The translation middleware piece translates requests provided to the front end service to requests for back-end data stores. A first response to the first request to the front end user service is received. A second request is provided to a back-end data store. The second request to the back-end data store is in a format appropriate for the back-end data store and includes elements that should return the same results as the first request to the front end user service. A second response to the second request to the back-end data store is received. Based on the responses, a functional state is determined for at least one of the, front end, the back-end, or the translation middleware piece.

Abstract: Brokering requests between a user and a content provider. Methods include receiving, at the middleware system, a request for data from a user that is formatted in a first request format and requests data from a content provider. The request is translated to a second request format that is compatible with the content provider and sent to the content provider. A response is received from the content provider that includes hierarchically-structured content. The hierarchically-structured content is converted into tabular content by performing first queries on the hierarchically-structured content to identify repeating nodes, and mapping the repeating nodes to rows in the tabular format, and by performing second queries on the hierarchically-structured content to identify individual columns in the tabular format.

Abstract: Embodiments are directed to providing a plurality of data provisioning tiers for datasets and to throttling access to dataset data based on the dataset's data provisioning tiers. In an embodiment, a computer system receives an input that specifies a maximum number of queries that a user is allowed to perform on a given dataset over a specified period of time. The computer system generates data provisioning tiers for the dataset based on the received input. Each data provisioning tier indicates a maximum number of queries that the user is allowed to perform on a given dataset over a specified period of time. The computer system also applies the generated data provisioning tiers to the dataset so that the user is limited to the maximum number of queries specified in the data provisioning tier.

Abstract: Various aspects for providing a runtime for dataset transformation are disclosed. In one aspect, data consumption requests are received. The requested data is retrieved from a web service in an arbitrary form, and subsequently transformed into a standardized result from the arbitrary form. In another aspect, a user interface is displayed to a content provider, and an input identifying a transform function selected by the content provider is received via the user interface. A transform assembly is then generated based on the input, which facilitates retrieving data from a web service in an arbitrary form, and transforming the data into a standardized result by calling the selected transform function. In yet another aspect, third party code is associated with a transform assembly. An execution of the third party code is then managed such that at least one aspect of the transform assembly is operated according to the execution.

Abstract: Various aspects for scaling an availability of information are disclosed. In one aspect, a response performance associated with responding to data consumption requests is monitored. A characterization of the response performance is ascertained, and a scaling of resources is facilitated based on the characterization. In another aspect, a data consumption status indicative of data consumed is ascertained. Here, a scalability interface is provided, which displays aspects of the status, and receives an input from a content provider. An allocation of resources is then modified in response to the input. In yet another aspect, a response performance associated with responding to data consumption requests is monitored. An application programming interface (API) call is generated based on a characterization of the response performance, and transmitted to a content provider. An API response is then received from the content provider indicating whether a scaling of resources for hosting the data was performed.

Abstract: Aspects are disclosed for providing information as a service via web services. Access to at least one application programming interface (API) database is facilitated and requests for a requested API are parsed. Here, such API requests facilitate a processing of data provided by at least one content provider. In an aspect, each request includes a key associated with a developer of the requested API and a unique identifier associated with a user of the requested API. A usage of the requested API is then tracked based on the key and/or unique identifier.

Abstract: Data is published by publishers to an information service configured to receive data sets and allow consumers to consume the data sets via queries. Structural information of the data sets (e.g., column information) is presented to the publishers to select which information of the data sets can be a search parameter and which information can be returned in query results. Query interfaces are automatically created based on the selections by the publisher, and the back end databases are optimized for such query interfaces, e.g., creation of indexes based on the search parameters or query results selected by the publisher. A query aggregator can automatically combine a given query interface with other query interfaces to form more complicated (but still permitted) queries based on the intersection of permissions for the given query interface and the other query interfaces.

Abstract: Methods, systems, and computer-readable media are disclosed to generate an interface for a web service and to query the web service. A particular method includes generating a user interface associated with a web service. The user interface includes one or more input parameter options associated with the web service. The user interface is generated based on a service specification and one or more series specifications associated with the service specification. User input is received via the user interface, where the user input includes a selection of at least one of the one or more input parameter options. A query of the web service is generated based on the received user input, where the query reflects at least one selected input parameter option. The method includes invoking the generated query with respect to the web service to receive results and automatically adding the received results to the user interface.