HTTP Datasets for Research in Service-Oriented Computing
<p>We present three HTTP datasets for experimenting on various aspects of service-oriented computing.</p> <p>The datasets were generated by creating random traffic targeting the services offered by <a href="https://developers.google.com/tasks">Google Tasks</a>, <a href="https://api.slack.com/methods">Slack</a> and <a href="https://developer.twitter.com/en/docs/tweets/post-and-engage/overview">Twitter</a>. In order to form transactions, various operations to create, read, update and delete (CRUD) service-specific resources were created and the respective responses were recorded, simulating service interactions by users through applications. The resources the operations interacted with are lists (Google Tasks), messages (Slack) and tweets (Twitter). </p> <p>The input generation used fuzzing techniques. In particular, <a href="https://jmeter.apache.org/">Apache JMeter</a> was used as it has the functionality to fuzz RESTful services (randomly generate various types of API calls by providing different inputs) and recording interactions in a suitable textual format for further processing. The fuzzing was guided by a light-weight semantic service model provided as <a href="https://github.com/OAI/OpenAPI-Specification">Swagger</a> (recently renamed as OpenAPI) spec. </p> <p>The datasets reflect the richness of modern Web APIs for experiments and are in the XML format. </p>
ShareScore
16/100
Overall dataset sharing score
Score breakdown
These five areas show where the dataset supports — or may limit — practical reuse.
- Stewardship
- 8
- Harmonization
- 4
- Access
- 0
- Reuse readiness
- 0
- Engagement
- 4