Comments on four papers on synthetic data in Volume 32 Issue 1 the Statistical Journal of the IAOS
Recent News
Recent Outputs
Upcoming Events
Sorry, there are currently no upcoming Events.
Raab, G. (2016) Statistical Journal of the IAOS, 32, 267 - 269 [SLS]
Other information:
Extract:
One of several explanations of why Homo Sapiens is the only surviving sub-species of the genus Homo is the extended length of our childhood and adolescence. The value of this extended maturation and developing period may be that it allows us to learn and carry out complex tasks. Like Homo Sapiens, methodology for synthetic data has had a long learning period. The idea of using synthetic data for disclosure control was con- ceived more than 20 years ago [1–3], but it was a fur- ther 10 years before the first papers describing how to do it appeared in the literature [4,5]. The subsequent decade was one of rapid development and innovation when the methodology was tested and expanded. The energy and enthusiasm for synthetic data of Reiter and his colleagues was responsible for many major de- velopments; see the monograph by Drechsler [6] for a review. Towards the end of synthetic data’s second decade real applications began to appear [7–9]. Two of the four substantial papers that deal with synthetic data in this issue [10,11] are examples of mature methodol- ogy, while the other two [12,13] deal with disclosure control, the aspect of synthetic data that is at an early stage in its development. My comments here are from the point of view of a practitioner looking for useful and workable ideas in this field. Our project to pro- vide data for the UK Longitudinal Studies (LSs) is re- ferred to in Vilhuber et. al.’s overview of international developments [14]. More details of our methods and our synthpop package for R are available [15–17].
SLS project pageONS LS project pageNILS project page
Available online: Statistical Journal of the IAOS,
Download output document: Full Paper (PDF 65KB)
Output from project: 2013_012 (SLS), 30158 (ONS LS), 079 (NILS)
© 2026 CALLS Hub - Mtc - SMA Login Contact - Output Login
| Cookie | Duration | Description |
|---|---|---|
| cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
| cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
| cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
| cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
| cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
| viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
| Cookie | Duration | Description |
|---|---|---|
| __utma | 2 years | Used to distinguish users and sessions. The cookie is created when the javascript library executes and no existing __utma cookies exists. The cookie is updated every time data is sent to Google Analytics. |
| __utmb | 30 minutes | Used to determine new sessions/visits. The cookie is created when the javascript library executes and no existing __utmb cookies exists. The cookie is updated every time data is sent to Google Analytics. |
| __utmc | Not used in ga.js. Set for interoperability with urchin.js. Historically, this cookie operated in conjunction with the __utmb cookie to determine whether the user was in a new session/visit. | |
| __utmt | 10 minutes | Used to throttle request rate. |
| __utmz | 6 months | Stores the traffic source or campaign that explains how the user reached your site. The cookie is created when the javascript library executes and is updated every time data is sent to Google Analytics. |
| _ga | 2 years | Used to distinguish users. |
| _gat | 1 minute | Used to throttle request rate. |
| _gid | 24 hours | Used to distinguish users. |