1 / 51

XBRL Specifications

Eurofiling - XIII European Banking Supervisors XBRL Workshop 24th - 25th November 2010 Commission de Surveillance du Secteur Financier Luxembourg . XBRL Specifications. Active Technical Areas. XSB Strategic Initiatives . Abstract Modeling is starting now.

misha
Download Presentation

XBRL Specifications

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Eurofiling - XIII European Banking Supervisors XBRL Workshop 24th - 25th November 2010 Commission de Surveillance du Secteur Financier Luxembourg XBRL Specifications

  2. Active Technical Areas

  3. XSB Strategic Initiatives Abstract Modeling is starting now

  4. XSB Strategic Initiatives - Journey so far Identifying the Goals Analyzing the Market Feedback Identifying the Initiatives

  5. Strategic Initiatives Overview

  6. Starting now: Abstract Modelling • XBRL • framework for modelling various domains • a meta-model, not a model • taxonomy models a domain • UML • framework for modelling software infrastructures • XII’s relationship to XBRL is as OMG’s to UML • OMG Meta-Object Facility (MOF) models UML • XSB wishes the same for XBRL

  7. OMG’s Meta-Object Facility (MOF)

  8. XBRL Equivalent

  9. Abstract Modeling Initiative - Goals • Primary model captures XBRL semantics: • Core spec and Dimensions are mandatory • Model should be void of syntactic details • Should be portable across technologies, like SQL and OOP • Secondary model binds primary model to XML • This bridges the gap from model to current spec

  10. Abstract Modeling - Out of Scope • Domain (taxonomy) modelling not an objective • Parallel modelling efforts will be considered with BPB involvement • Formulas, Versioning, Rendering • XSB will consider

  11. Initiative plan • Focused group to delivery over 6-8 weeks • Easier to get short commitments • Deliverable is of high value to the community, so sooner the better • Abstract model is a prerequisite to several other initiatives

  12. 6- to 8-week Working Group • Format will be: • 2 face-to-face meetings over a 4-6 week period • 1st meeting scheduled for Boston on Jan 11-13 • Conference calls daily, or every other day, in between the face-to-face meetings • Dedicated project manager to drive the process • Preparations and materials will be assigned prior to face-to-face meetings • Face-to-face meetings will be divided into 90-120 minute segments, with firm deliverables defined

  13. Working Group Topics • Use cases • What processes is XBRL intended to work in? • Modelling the core specification • Facts, units, periods, entities, labels, heirarchy, etc. • Modelling the dimensions specification • Primary item, domain, dimension, member, etc. • Binding the models to the current XML syntax • How to bridge the gap from abstract model to the current XML specs

  14. Working Group Review Process • Review process will have to be open and as inclusive as possible: • Review period will have to demonstrate community coverage • Broad outreach (webcasts, conferences, etc.) will be a necessity • Specific, targeted outreach will also need to be conducted where necessary

  15. 6 areas for volunteer resources

  16. Volunteerism weak in EU

  17. Volunteer now!!! – Call to Action • volunteers@xbrl.org • http://www.surveymonkey.com/s/2010Initiatives

  18. Base Spec Updates

  19. Bugzilla issues

  20. Calculation arcs precision issue • Items reported in precision 0 always invalid • Items reported in decimals with value 0 • Infers precision 0 • Technically always invalid • Changing to infer decimals • Known financial reporting is in decimals • Eliminates issues with 0-valued items, edge cases • Test suite has been updated

  21. Section 5.2.5.2 paragraph #6 The total of a binding calculation is defined to be the sum of the rounded values of the contributing numeric items in the binding, each multiplied by the value of the weight attribute on the item's associated calculationArc. This multiplication takes place after any necessary rounding is performed. The rounded value of a numeric item is the result of rounding the value of the numeric item to its precision decimals or inferred precision decimals (see Section 4.6.6 and ). A binding calculation is defined to be consistent if the rounded value of the summation item is equal to the total rounded to the  precision decimals or inferred precision decimals of the summation item. (If any item of the calculation has a precision attribute value 0 then the binding calculation is deemed to be inconsistent.)

  22. Formula Updates

  23. Formula CR-extension modules

  24. Formula topics of 2010/11/23 • 1. CEBS member formula issues • 2. Dimensional aspects of fallback values • 3. Debugging capabilities • 3. Rendering of new FINREP and COREP • 4. Rendering ideas and formulae editoring

  25. Versioning Updates

  26. Versioning status - modules status CR PWD

  27. Versioning module overview

  28. Inputs and outputs in versioning

  29. Inputs and outputs in versioning

  30. Base module covers DTS, roles, namespaces

  31. Concept modules

  32. Change of concept name

  33. Relationship and Aspects Models

  34. Change to the dimensional representation of a set of concepts • Unchanged from business perspective • Concept and dimensions aspects changed • A, B, C and X are primary items • D is a dimension • d1, d2 and d3 are domain members • Version 1 Version 2 • A <==> X ( D = d1 ) • B <==> X ( D = d2 ) • C <==> X ( D = d3 )

  35. Dimensions are instance aspects

  36. Instance aspects change events <verdim:aspectModelChange> <verdim:fromAspects> <verdim:concepthref="../dts1.xsd#A"/> </verdim:fromAspects> <verdim:toAspects> <verdim:concepthref="../dts2.xsd#X"/> <verdim:explicitDimensionhref="../dts1.xsd#D"> <verdim:memberhref="../dts1.xsd#d1"/> </verdim:explicitDimension> </verdim:toAspects> </verdim:aspectModelChange>

  37. Location aspect (GL to FR) • Predicate expression (Xpath 2) • Identifies fact by relative location <gl:entryDetail> <gl:amount>500</gl:amount> <gl:xbrlInfo> <gl:summaryReportingElement>Cash</gl:summaryReportingElement> </gl:xbrlInfo> </gl:entryDetail> <verdim:concepthref=“…gl.xsd#amount"/> <verdim:location> ../gl:xbrlinfo/gl:summaryReportingElementeq ‘Cash’ </verdim:location> <fr:cash>500</fr:cash> <verdim:concept href=“…fr.xsd#cash"/>

  38. Location aspect modeling <verdim:aspectModelChange> <verdim:fromAspects> • <verdim:concepthref=“…gl.xsd#amount"/> • <verdim:location> • ../gl:xbrlinfo/gl:summaryReportingElementeq ‘Cash’ • </verdim:location> • </verdim:fromAspects> • <verdim:toAspects> <verdim:concepthref="../fr.xsd#cash"/> </verdim:toAspects> </verdim:aspectModelChange>

  39. Beginning balance aspects <xbrli:xbrl> <gl:accountingEntries> <gl:entryHeader> <gl:qualifierEntry …>balance-brought-forward</ …> <gl:entryDetail> <gl:account> <gl:accountMainID…>5100</ …> <gl:accountMainDescription …>Supplies</ …> <gl:accountType …>account</ …> </gl:account> <gl:amount…>242678.26</ …> <gl:debitCreditCode …">D</ …> <gl:xbrlInfo> <gl:xbrlInclude …>beginning_balance</…> </gl:xbrlInfo> </gl:entryDetail> … </ gl:entryHeader> <gl:entryHeader> <gl:qualifierEntry …>standard</ …> <gl:entryDetail> … </gl:entryDetail> … </ gl:entryHeader> </ gl:accountingEntries> </ xbrli:xbrl> <verdim:concepthref=“…gl.xsd#amount"/> <verdim:location> ../../gl:qualifierEntryeq’balance-brought-forward’ and ../gl:account/gl:accountMainIDeq ‘5100’ and ../gl:xbrlinfo/gl:xbrlIncludeeq ‘beginning_balance’ </verdim:location>

  40. Rendering status • Inline XBRL - REC • embeds XBRL fragments into an HTML document • Requirements for linkbase – Drafting • Linkbase spec – Modularized & new specs

  41. Rendering Updates inline XBRL Requirements Linkbase Future

  42. Rendering linkbase update • Separation of Specification • Improve understanding and extendsibility • New Models • Inheritance mechanism • Injection model • New Specifications • Identification and Ordering • Context Grouping • Generic Preferred Label • Manifest

  43. New Rendering Architecture #1 Public Taxonomy author Data preparer Taxonomy 2.1 spec dimensions Extension Taxonomy Extended table of contents Identification and ordering Taxonomy Instance / Inline XBRL User specific Rendering Structure Detailed rendering structure Less information here Put as much as information here

  44. New Rendering Architecture #2 Public Taxonomy author Report from Taxonomy information Taxonomy 2.1 spec dimensions Ex: Manual Guidelines etc… Create report Identification and ordering Taxonomy Detailed rendering structure

  45. Injection Model • Current spec provides document model to rendering modeling: • document layered model. • Uses linkbase mechanism to represent entire reporting document model. • Additional model introduced: • Injection model. • Uses existing rendering format (such as XHTML ) then inject rendering definition into the format.

  46. Document Layered Model Component Legend XLink arc Container XLink resource Document relationships relationships Document Containers Components

  47. Injection Model Tables, lists, paragraphs are injected into exiting format (XHTML as such) image Legend Rendering Components XHTML etc..

  48. Generic Preferred Label • Heavy use of definition link by XBRL Dimensions, same mechanism such as preferred label in presentation link solves rendering issues. • Generic preferred label is a new mechanism to ‘preferredLabel’ attribute on definition/calculation/generic arcs.

  49. Rendering linkbase specs • Specification are separated into: • Semantics • Semantic modeling definition regarding the specifications • Structure • One basic model to represent reporting document structure • Axes • Set of axis definitions which could be used to rendering component • Components • Set of component definitions that could be used in the report structure • Values • Set of value definitions that could be used to represent cell pattern. • Rules • Set of rule definitions that could be used from any part of rendering information. • Identification and Ordering (Table of Contents) • Mechanism to identify statements (build table of contents explicitly) • Context Grouping • Mechanism to create group of contexts • Generic Preferred Label • Mechanism to specify preferred label into linkbases other than presentation linkbase. • Manifest • Mechanism to package XBRL doucments

  50. Rendering modeling

More Related