API WG Update.pptxVIP

API WG Update 16th Eurofiling Workshop Wednesday 12 December Herm Fischer API WG - Objectives Goal To standardise the APIs created for XBRL by providing blueprints for them in the form of API signatures Benefits Providing software developers with a familiar point of entry into XBRL Serving as a useful learning tool for developers wishing to incorporate XBRL Encouraging open source implementations of the API signatures Enabling greater consistency across vendor tools and greater interoperability across vendor implementations of XBRL API WG - Status Working Group formed in April 2012 First task was to create survey to canvas input from broad XBRL community. Survey released in September and covered areas including: Background information such as operating jurisdictions, XBRL specifications used etc How XBRL is being used (taxonomy creation, instance creation etc) How the XBRL integration was achieved (used existing XBRL toolkit, built own XBRL capability etc) What problems were encountered What enhancements to current API’s would they like to see API WG - Survey Status Survey is still open and we’d love to hear from you! /news/provide-your-input-take-api-survey Initial results are on the following pages but: They are incomplete and based on a relatively small sample - 61 respondents For key questions only around 50% of respondents provided a response (i.e. others skipped those questions) There were some conflicting results, i.e. the responses to one question did not tally with the responses to another question API WG - Survey Responses Respondents Majority of respondents are XBRL developers, consultants and solution providers. This is followed by XBRL users Smallest group are taxonomy authors and regulators XBRL Integration B2G respondents were more than double those using B2B Respondents using XBRL to normalise data or to produce internal reports is almost half the number of those submitting instance documents to regulators Specifications and Document Persistence S