Situation november / december 2012 - DRAFT Emile Bartolé CEN/WS XBRL: Improving transparency in financial and business reporting CWA2 Situation 1CWA2.

Situation november / december 2012 - DRAFTEmile Bartolé

CEN/WS XBRL: Improving transparency in financial and business reporting

CWA2 Situation

1 CWA2

Objectives of CWA2Dual objective of CWA2: standardize

The way of submitting instances, a container with standardizedEncryptionDigital signatureCompression…

The way of transmitting the usual metadata that determine the context of an xbrl reporting instance

the sender of the documentcontact detailsdate and time of submission…

Page 2 CWA2

Workflow

1. Submission container

2. Feedback container

Submission container

Declarer Regulator

Feedback container

Declarer Regulator

Container structure

Compression / packaging: zip

Signature: XAdES-EPES

Encryption: XML Encryption

Page 4

Signature

Encryption

Zip

File-1 … File-n

Container structure

No standard naming convention applies to the files (neither to the container nor to the XBRL instances in the container)

Multiple compression packages per security envelope (encryption, signature) are allowed (e.g. for a consolidated reporting for several entities of a group that requires cross-verification)

Page 5

Signature

Encryption

Zip

File-1 … File-n

Zip

File-1 … File-n

Zip

File-1 …File-n

…

Submission containerMultiple XBRL instance documents packed with one xml header file

Header is the only file with a naming convention: “header.xml”; it is located on top-level of the compression package

Header lists xbrl instances contained in the container

Instances should always have extension .xbrl

Use of folders is optional; in case they are used, all references (in header to XBRL instances; in XBRL instances to taxonomy files) must respect them.

Folder names used here (“Instances”, “Taxonomy”) are given as examples

Taxonomy files are optional (they are normally unnecessary and would only be used in case taxonomy extensions by the reporter became allowed in Europe)

Authorities may define “their” naming convention (files, folders)

Page 6

Package & Compress (zip)

Signature (XADES-EPES)

header.xml

Instances instance1.xbrl instance2.xbrl … instancen.xbrl

Taxonomy taxonomy-file1.xml | .xsd taxonomy-file2.xml | .xsd … taxonomy-filen.xml | .xsd

Encryption (XML Encryption)

Feedback container

One XML feedback file per XBRL instance in the original submission container

Feedback files will be generated systematically, even if no errors at validation time occurred (also positive acknowledge)

The XML schema for the feedback files will contain a hash code for the original file guaranteeing non-repudiation of the submitted XBRL instances

The feedback file will have the same name as the original instance it refers to (but with extension .xml instead of the original .xbrl)

Folder name used here (“Feedback”) is given as an example

Package & Compress (zip)

Signature (XADES-EPES)

Feedback instance1.xml instance2.xml … instancen.xml

Encryption (XML Encryption)

Page 7

Industry standard .zip compressionhttp://www.pkware.com/documents/casestudies/APPNOTE.TXTMinimum 2.0 versionNo maximum defined by standard, but potentially defined by receiving authority

Page 8 CWA2

Compression

Compliant with European Directive 1999/93/ECBuilt on XML digital signature (W3C).The most flexible signature supported by the directive Allows the addition of one (or more) compression package(s) to a containerMust contain the signer’s digital X.503 v3 certificate.Long terms validation is not needed, as signature will be validated in a limited time-frame.Produces an XML output

Page 9 CWA2

Signature: XADES-EPES

XAdES (XML Advanced Electronic Signature) is build on XML digital signature (w3c).

XAdES-BES: XAdES – Basic Electronic Signature. Satisfies the legal requirements for electronic signature, as defined in the European Directive on Electronic Signatures, providing basic authentication and integrity protection XAdES-EPES: XAdES – Explicit Policy-based Electronic Signature. Extends XAdES-BES , incorporating a signed attribute indicating the signature policy that shall be used to validate the electronic signature.

Page 10 CWA2

Signature selected: XAdES-EPES

Standard W3C XML compression http://www.w3.org/TR/xmlenc-core/

Page 11 CWA2

W3C XML encryption

Header approaches

Decisions of the F2F end october in Madrid:Header will be a separate XML instanceNo integration with XBRL (no extension of or integration with any XBRL taxonomy)One header for multiple XBRL instancesSupport of initial & subsequent update submissions (corrections)

Direct import of the core business vocabulary into the draft header taxonomy

Header Orientations

Types of header fields

CWA2Page 13

Type of field Way of dealing with it

Related to filing instance reports Integrated into the header XML schema

Transport related Not in the scope of the header taxonomy, this should be part of the submission / transport system used

Data related Not in the scope of the header taxonomy, this should be part of the data taxonomy

Initial & update submissionsSupport of initial & subsequent update submissions (corrections)

Flag in header toggles between initial and update containers

“An authority allowing the sending of update containers is required to provide the necessary mechanisms to ensure that in spite of the possibility of the failure of content-related validations on the update container itself, the combination of the latest initial container with all subsequent update containers guarantees the full respect of all content-related validations as defined in the taxonomies and an adequate error handling.”

Container (initial)

File 1 …File n

Container (update)

File 1 …File n

Container (update)

File 1 …File n

Container (initial)

File 1 …File n

t

Container (update)

File 1 …File n

Thanks for your attention

Page 15

Comments or questions?

[email protected]

CWA2