The Test Bed has published a new online guide on enabling usage statistics for on-premise RDF, XML, JSON and CSV validators.
The Test Bed’s validators are popular components used to support specifications with validation for RDF, XML, JSON and CSV data. The most popular method for users to deploy a validator is to provide its configuration to the Test Bed team which will set up and manage it on the users’ behalf. This allows validation services to be brought online rapidly and does not burden users with operational concerns.
An alternative to this approach for users wanting more control over their validators is to deploy on-premise on their own infrastructure, either as public services or as internal quality assurance components. For validators accessed publicly, an interesting extension that is now possible is the option to extend them to collect usage statistics, providing insights into how much they are being used, as well as the most popular specifications, options and APIs.
To facilitate the configuration of usage statistics for on-premise validators the Test Bed team has now made available a detailed step-by-step configuration guide, as part of its online guides and tutorials. This new guide walks you through the process of enabling statistics collection for a simple validator and configuring a service that will collect the statistics data for further processing.
If you are running validators on your own infrastructure and collecting such statistics seems like an interesting extension, you are invited to check out the new guide here. It is important to note that even with statistics enabled, validator users remain fully anonymous. The collected data never includes personally identifiable user information, focusing rather on how the validator is used rather than by whom.
If you are new to the Test Bed’s validators but believe they could be useful in support of your specifications, be sure to check the validators’ setup guides (for XML, RDF, JSON and CSV validators). To set up validators on your own infrastructure, benefiting from the extra control and the discussed possibility to collect usage statistics, you can follow the validators’ production installation guide both for setting up a new validator as well as migrating one currently managed by the Test Bed team. Finally, if you are new to the Test Bed overall, you can learn about it through its Joinup space with its value proposition being a good starting point for newcomers. To remain updated of all the latest Test Bed news: