iXBRL Financial Statements Web Service - ROS · XBRL/CheckValidationStatus operation of the iXBRL Financial Statements web service. The element details the current status of the iXBRL

Revenue Online Services iXBRL Financial Statements Web Service Schema Notes

Page 1 of 30

Revenue Online Services

Schema Notes iXBRL Financial Statements Web Service

Last Updated 11/09/12 Document Version 0.1


Page 2 of 30

CONTENTS Contents ...................................................................................................................................................................... 2 0 Document Information .......................................................................................................................................... 4

0.1 Synopsis....................................................................................................................................................... 4 0.2 Change History ............................................................................................................................................. 4

1 Schema Overview................................................................................................................................................. 5 2 Elements .............................................................................................................................................................. 6

2.1 XBRLSubmissionRequest ............................................................................................................................. 6 2.1.1 Element Overview ................................................................................................................................. 6 2.1.2 Child Elements ...................................................................................................................................... 6

2.2 XBRLSubmissionResponse........................................................................................................................... 7 2.2.1 Element Overview ................................................................................................................................. 7 2.2.2 Child Elements ...................................................................................................................................... 7

2.3 CheckXBRLSubmissionRequest.................................................................................................................... 8 2.3.1 Element Overview ................................................................................................................................. 8 2.3.2 Child Elements ...................................................................................................................................... 8

2.4 CheckXBRLSubmissionResponse ................................................................................................................. 9 2.5 XBRLValidationRequest .............................................................................................................................. 10

2.5.1 Element Overview ............................................................................................................................... 10 2.5.2 Child Elements .................................................................................................................................... 10

2.6 XBRLValidationResponse ........................................................................................................................... 11 2.6.1 Element Overview ............................................................................................................................... 11 2.6.2 Child Elements .................................................................................................................................... 11

2.7 CheckXBRLValidationRequest .................................................................................................................... 12 2.7.1 Element Overview ............................................................................................................................... 12 2.7.2 Child Elements .................................................................................................................................... 12

2.8 CheckXBRLValidationResponse.................................................................................................................. 13 3 Complex Types................................................................................................................................................... 14

3.1 Document ................................................................................................................................................... 14 3.1.1 Type Overview..................................................................................................................................... 14 3.1.2 Attributes............................................................................................................................................. 14 3.1.3 Child Elements .................................................................................................................................... 14

3.2 StatusResponseType .................................................................................................................................. 15 3.2.1 Type Overview..................................................................................................................................... 15 3.2.2 Attributes............................................................................................................................................. 15 3.2.3 Child Elements .................................................................................................................................... 15

3.3 ErrorMessage ............................................................................................................................................. 16 3.3.1 Type Overview..................................................................................................................................... 16 3.3.2 Attributes............................................................................................................................................. 16

3.4 ValidationDetail ........................................................................................................................................... 17 3.4.1 Type Overview..................................................................................................................................... 17 3.4.2 Attributes............................................................................................................................................. 17 3.4.3 Child Elements .................................................................................................................................... 17

3.5 ValidationMessage...................................................................................................................................... 18 3.5.1 Type Overview..................................................................................................................................... 18 3.5.2 Attributes............................................................................................................................................. 18

3.6 Reference ................................................................................................................................................... 19 3.6.1 Type Overview..................................................................................................................................... 19 3.6.2 Child Elements .................................................................................................................................... 19

3.7 ReferenceMessage...................................................................................................................................... 20 3.7.1 Type Overview..................................................................................................................................... 20 3.7.2 Attributes............................................................................................................................................. 20

4 Codes................................................................................................................................................................. 21 4.1.1 Status Codes....................................................................................................................................... 21 4.1.2 Error Codes......................................................................................................................................... 21

5 Appendix 1 ......................................................................................................................................................... 22 5.1 Sample Inline XBRLSubmissionRequest ..................................................................................................... 22 5.2 Sample Encoded Inline XBRLSubmissionRequest ....................................................................................... 22 5.3 Sample XBRLSubmissionResponse............................................................................................................ 23 5.4 Sample CheckXBRLSubmissionRequest ..................................................................................................... 23


Page 3 of 30

5.5 Sample CheckXBRLSubmissionResponse .................................................................................................. 23 5.6 Sample Inline XBRLValidationRequest ........................................................................................................ 25 5.7 Sample Encoded Inline XBRLValidationRequest.......................................................................................... 25 5.8 Sample XBRLValidationResponse............................................................................................................... 26 5.9 Sample CheckXBRLValidationRequest........................................................................................................ 26 5.10 Sample CheckXBRLValidationResponse ..................................................................................................... 26

6 Appendix 1 ......................................................................................................................................................... 28


Page 4 of 30

0 DOCUMENT INFORMATION

0.1 Synopsis Notes on the iXBRL Financial Statements web service schema notes.

0.2 Change History Table 1: Change History

Version Number

Section Affected

Change Description Date

0.1 ALL Initial Draft 11/09/12


Page 5 of 30

1 SCHEMA OVERVIEW This document outlines the iXBRL Financial Statements web service schema. This schema defines the structure of messages used to submit or validate iXBRL files using the iXBRL Financial Statements web service on ROS.

This schema does not contain rules pertaining to the validation of the iXBRL Financial Statements themselves, only the requests and responses to the web service.

Full details on the format of iXBRL that will be accepted by revenue can be found at: XXXXX.

The schema comprises of eight different Request and Response messages for the four web service operations. These are:

Operation Request Element Response Element XBRL/Submit XBRLSubmissionRequest XBRLSubmissionResponse XBRL/CheckSubmissionStatus CheckXBRLSubmissionRequest CheckXBRLSubmissionResponse XBRL/Validate XBRLValidationRequest XBRLValidationResponse XBRL/CheckValidationStatus CheckXBRLValidationRequest CheckXBRLValidationResponse

Details on the different operations and their functionality can be found in the iXBRL Financial Statements web service specification.


Page 6 of 30

2 ELEMENTS

2.1 XBRLSubmissionRequest This element is used to submit an iXBRL file to Revenue using the XBRL/Submit operation of the iXBRL Financial Statements web service. This element wraps an iXBRL file with details relevant to the submission.

2.1.1 Element Overview

2.1.2 Child Elements This element has the following children:

Name Type Required (Y/N) Description / Validation

ReturnDetails rosxbrl:ReturnDetails Y This element and its children contain details about the registration and period for which iXBRL is being filed.

ReturnDetails/AccountType ros:taxtype Y An enumeration indicating the tax type for which the iXBRL is being filed. Currently only Corporation Tax and Income Tax are valid. Sample: “Corporation Tax”

ReturnDetails/RegistrationNumber

ros:string9 Y The customers registration number for the tax against which they are submitting iXBRL. Sample: “1234567T”

ReturnDetails/PeriodStartDate ros:date Y The start date of the tax period for which the submission is being made. In the format DD/MM/YYYY Sample: “31/12/12”

ReturnDetails/PeriodEndDate ros:date Y The end date of the tax period for which the submission is being made. In the Sample: “31/12/13”

Statements rosxbrl:Document Y Contains the iXBRL File. Described further in Section 3.1


Page 7 of 30

2.2 XBRLSubmissionResponse This element is received following a submission of an iXBRL file to Revenue using the XBRL/Submit operation of the iXBRL Financial Statements web service. This element contains either an acknowledgment number if successfully received, or an error if issues were encountered.




Submission Error rosxbrl:ErrorMessage Y Contains submission error details. Described further in Section 3.3.

AcknowledgementNumber ros:string20 Y The acknowledgement number that confirms receipt of the iXBRL file for a tax period. This number should be retained as it will be used to check the status of your submission. Sample: “12345678912345678911”


Page 8 of 30

2.3 CheckXBRLSubmissionRequest This element is used to request the status of a previously submitted iXBRL file to Revenue. It is sent to the XBRL/CheckSubmissionStatus operation of the iXBRL Financial Statements web service.




AcknowledgementNumber ros:string20 Y The acknowledgement number relating to the iXBRL submission for which the status is being checked. Sample: “12345678912345678911”


Page 9 of 30

2.4 CheckXBRLSubmissionResponse This element is received following a submission of a CheckXBRLSubmissionRequest to the XBRL/CheckSubmissionStatus operation of the iXBRL Financial Statements web service.

The element details the current status of the iXBRL file that was submitted and details any validation issues if found.

This element is a complex type of type StatusResponseType. The StatusResponseType type is detailed further in section 0.


Page 10 of 30

2.5 XBRLValidationRequest This element is used to send an iXBRL file to Revenue for validation using the XBRL/Validate operation of the iXBRL Financial Statements web service. This element wraps an iXBRL file with details relevant to the validation.




ReturnDetails rosxbrl:ReturnDetails Y This element and its children contain details about the registration and period for which iXBRL is being filed.

ReturnDetails/AccountType ros:taxtype Y An enumeration indicating the tax type for which the iXBRL will eventually be filed. Currently only Corporation Tax and Income Tax are valid. The value of this element will dictate what business validation rules occur. Sample: “Corporation Tax”

ReturnDetails/PeriodStartDate ros:date Y The start date of the tax period for which the submission is being made. In the format DD/MM/YYYY Sample: “31/12/12”

ReturnDetails/PeriodEndDate ros:date Y The end date of the tax period for which the submission is being made. In the Sample: “31/12/13”

Statements rosxbrl:Document Y Contains the iXBRL File. Described further in Section 3.1


Page 11 of 30

2.6 XBRLValidationResponse This element is received following a submission of an iXBRL file to Revenue for validation using the XBRL/Validate operation of the iXBRL Financial Statements web service. This element contains either an acknowledgment number if successfully received, or an error if issues were encountered.




Validation Error rosxbrl:ErrorMessage Y Contains submission error details. Described further in Section 3.3.

AcknowledgementNumber ros:string20 Y The acknowledgement number that confirms receipt of the iXBRL file for validation. This number should be retained as it will be used to check the status of your validation. Sample: “12345678912345678911”


Page 12 of 30

2.7 CheckXBRLValidationRequest This element is used to request the status of a previously submitted iXBRL file to Revenue for validation only. It is sent to the XBRL/CheckValidationStatus operation of the iXBRL Financial Statements web service.




AcknowledgementNumber ros:string20 Y The acknowledgement number relating to the iXBRL file for validation for which the status is being checked. Sample: “12345678912345678911”


Page 13 of 30

2.8 CheckXBRLValidationResponse This element is received following a submission of a CheckXBRLValidationRequest to the XBRL/CheckValidationStatus operation of the iXBRL Financial Statements web service.

The element details the current status of the iXBRL file that was submitted for validation and details any validation issues if found.

This element is a complex type of type StatusResponseType. The StatusResponseType type is detailed further in section 0.


Page 14 of 30

3 COMPLEX TYPES

3.1 Document This type wraps an iXBRL file in one of two different formats.

3.1.1 Type Overview

3.1.2 Attributes This Type has the following attributes:


fileName xsd:string N This attribute is the name of the iXBRL file being submitted (e.g. ‘accounts2013.html’). The value is not required and if not provided, revenue will assume a common name.

3.1.3 Child Elements This element has the following children. Either an InlineXBRL or EncodedInlineXBRL element may be present in this type, not both.


InlineXBRL xsd:anyType Y This any type element will contain the complete iXBRL file in its xhtml format. To ensure the entire message being submitted to the web service is valid xml, the doctype should be removed from the iXBRL file before being added to this element.

EncodedInlineXBRL xsd:base64Binary

Y The element will contain a Base64 Binary encoded version of the iXBRL file that is to be submitted. This iXBRL file may contain a doctype at the start of the file before encoding.


Page 15 of 30

3.2 StatusResponseType This type is used as the response of calls to check if an iXBRL submission or validation is complete, and details related errors and messages if any.

3.2.1 Type Overview



rqSuccess xsd:boolean Y This attribute indicates whether or not your request to check the status was successful. If the request failed generally a lookupError will be provided in the child elements. Sample: “true”

3.2.3 Child Elements This element has the following children. Either a Lookup Error or Status element may be present in this type, not both. Where the Status is invalid, an unbounded list of ValidationDetail Elements may be present


LookupError rosxbrl:ErrorMessage Y Contains lookup error details. Described further in Section 3.3.

Status xsd:integer Y The element will contain an integer value representing the current status of the iXBRL file. Status codes are detailed in Section 4.1.1. Sample: “1”

ValidationDetail rosxbrl:ValidationDetail

N The ValidationDetail elements are present when the iXBRL status is invalid. More than one can be provided. An element will be present for each validation messages. The ValidationDetail type is further detailed in Section 3.4.


Page 16 of 30

3.3 ErrorMessage This type is an extension of a xsd:String and contains an error message in English. This error generally relates to an error processing your request, not with validation of the iXBRL file itself. A numeric identifier is also provided as an attribute.

Error messages and codes are detailed in section 4.1.2.

3.3.1 Type Overview



ErrorCode xsd:integer N This attribute details the error code number for the listed error message. Error codes are detailed in section 4.1.2.


Page 17 of 30

3.4 ValidationDetail This type is used to describe a validation error or message encountered when trying to validate an iXBRL file.

3.4.1 Type Overview



Severity xsd:string N This attribute indicates the type of message. At the moment only the string ‘Error’ is returned. Sample: “Error”

3.4.3 Child Elements This element has the following children. Either a Lookup Error or Status element may be present in this type, not both. Where the Status is invalid, an unbounded list of ValidationDetail Elements may be present


Code xsd:string Y Contains a unique string identifier for the validation message.

Message rosxbrl:ValidationMessage

Y This element contains a description of the validation message. This type is detailed in Section 3.5.

Reference rosxbrl:Reference N This element contains references to further information about the error. This type is detailed in Section 3.6.


Page 18 of 30

3.5 ValidationMessage This type is used to describe a validation issue encountered when trying to validate an iXBRL file.

This type is an extension of a xsd:String and contains a validation message. A language identifier is also provided as an attribute.

3.5.1 Type Overview



Language ros:language N This attribute indicates the language of the message. Sample: “E”


Page 19 of 30

3.6 Reference This type is used to describe further information for a validation error or message encountered when trying to validate an iXBRL file.

3.6.1 Type Overview

3.6.2 Child Elements This element has the following children. Both are optional


Message rosxbrl:ReferenceMessage

N Contains a string detailing further information on the error or message. This is detailed further in Section 3.7

URL xsd:string N A URL pointing to more information on the error or message


Page 20 of 30

3.7 ReferenceMessage This type is used to describe a further information for an error encountered when trying to validate an iXBRL file.

This type is an extension of a xsd:String and contains a message detailing further information about an error. A language identifier is also provided as an attribute.

3.7.1 Type Overview



Language ros:language N This attribute indicates the language of the message. Sample: “E”


Page 21 of 30

4 CODES Certain elements outlined above return a numeric code. The meanings of these codes are detailed below.

4.1.1 Status Codes The following codes detail the current status of the iXBRL file that is being / has been processed. These are used in the Status element of the StatusResponseType complex type.

Code Status -1 Still Processing 0 Invalid 1 Valid

4.1.2 Error Codes The following codes detail a technical error encountered when calling the iXBRL Financial Statements web service. These are used in the code attribute of the ErrorMessage complex type. These are described in more detail in the iXBRL Financial Statements web service specification.

Code Meaning 101 Please provide a valid acknowledgment number relating to

an XBRL upload you have made. 102 The XBRL service is temporarily unavailable, please try

again later. 103 You cannot currently file XBRL for this period. You may

not have a corresponding period or have already submitted XBRL for this period that is still processing.

104 You have exceeded the polling period for which you can check this acknowledgment number. Please try again later.


Page 22 of 30

5 APPENDIX 1

5.1 Sample Inline XBRLSubmissionRequest

<xbrl:XBRLSubmissionRequest xmlns:xbrl="http://www.revenue.ie/schemas/xbrl/"> <xbrl:ReturnDetails> <xbrl:AccountType>Corporation Tax</xbrl:AccountType> <xbrl:RegistrationNumber>1234567T</xbrl:RegistrationNumber> <xbrl:PeriodStartDate>01/11/2011</xbrl:PeriodStartDate> <xbrl:PeriodEndDate>31/10/2012</xbrl:PeriodEndDate> </xbrl:ReturnDetails> <xbrl:Statements> <xbrl:InlineXbrl> <html xmlns='http://www.w3.org/1999/xhtml' xmlns:iso4217='http://www.xbrl.org/2003/iso4217' xmlns:ix='http://www.xbrl.org/2008/inlineXBRL' xmlns:link='http://www.xbrl.org/2003/linkbase' xmlns:xbrli='http://www.xbrl.org/2003/instance' xmlns:xlink='http://www.w3.org/1999/xlink' xmlns:ixt='http://www.xbrl.org/inlineXBRL/transformation/2010-04-20' xmlns:uk-gaap="http://www.xbrl.org/uk/gaap/core/2009-09-01" xmlns:uk-bus="http://www.xbrl.org/uk/cd/business/2009-09-01" xmlns:uk-direp="http://www.xbrl.org/uk/reports/direp/2009-09-01" xmlns:uk-aurep="http://www.xbrl.org/uk/reports/aurep/2009-09-01" xmlns:uk-countries="http://www.xbrl.org/uk/cd/countries/2009-09-01" xmlns:ie-common="http://www.xbrl-ie.org/common/core/DRAFT" xmlns:ie-gaap="http://www.xbrl-ie.org/gaap/core/DRAFT" xmlns:xbrldi='http://xbrl.org/2006/xbrldi'>  </html> </xbrl:InlineXbrl> </xbrl:Statements>

</xbrl:XBRLSubmissionRequest>

5.2 Sample Encoded Inline XBRLSubmissionRequest

<xbrl:XBRLSubmissionRequest xmlns:xbrl="http://www.revenue.ie/schemas/xbrl/"> <xbrl:ReturnDetails> <xbrl:AccountType>Corporation Tax</xbrl:AccountType> <xbrl:RegistrationNumber>9952614C</xbrl:RegistrationNumber> <xbrl:PeriodStartDate>01/11/2011</xbrl:PeriodStartDate> <xbrl:PeriodEndDate>31/10/2012</xbrl:PeriodEndDate> </xbrl:ReturnDetails> <xbrl:Statements fileName="wsB64test"> <xbrl:EncodedInlineXbrl>PGh0bWwgeG1sbnM9J2h0dHA6Ly93d3cudzMub3JnLzE5OTkveGh0bWwnIHhtbG5zOmlzbzQyMTc9J2h0dHA6Ly93d3cueGJybC5vcmcvMjAwMy9pc280MjE3JyB4bWxuczppeD0naHR0cDovL3d3dy54YnJsLm9yZy8yMDA4L2lubGluZVhCUkwnIHhtbG5zOmxpbms9J2h0dHA6Ly93d3cueGJybC5vcmcvMjAwMy9saW5rYmFzZScgeG1sbnM6eGJybGk9J2h0dHA6Ly93d3cueGJybC5vcmcvMjAwMy9pbnN0YW5jZScgeG1sbnM6eGxpbms9J2h0dHA6Ly93d3cudzMub3JnLzE5OTkveGxpbmsnIHhtbG5zOml4dD0naHR0cDovL3d3dy54YnJsLm9yZy9pbmxpbmVYQlJML3RyYW5zZm9ybWF0aW9uLzIwMTAtMDQtMjAnIHhtbG5zOnVrLWdhYXA9Imh0dHA6Ly93d3cueGJybC5vcmcvdWsvZ2FhcC9jb3JlLzIwMDktMDktMDEiIHhtbG5zOnVrLWJ1cz0iaHR0cDovL3d3dy54YnJsLm9yZy91ay9jZC9idXNpbmVzcy8yMDA5LTA5LTAxIiB4bWxuczp1ay1kaXJlcD0iaHR0cDovL3d3dy54YnJsLm9yZy91ay9yZXBvcnRzL2RpcmVwLzIwMDktMDktMDEiIHhtbG5zOnVrLWF1cmVwPSJodHRwOi8vd3d3Lnhicmwub3JnL3VrL3JlcG9ydHMvYXVyZXAvMjAwOS0wOS0wMSIgeG1sbnM6dWstY291bnRyaWVzPSJodHRwOi8vd3d3Lnhicmwub3JnL3VrL2NkL2NvdW50cmllcy8yMDA5LTA5LTAxIiB4bWxuczppZS1jb21tb249Imh0dHA6Ly93d3cueGJybC1pZS5vcmcvY29tbW9uL2NvcmUvRFJBRlQiIHhtbG5zOmllLWdhYXA9Imh0dHA6Ly93d3cueGJybC1pZS5vcmcvZ2FhcC9jb3JlL0RSQUZUIiB4bWxuczp4YnJsZGk9J2h0dHA6Ly94YnJsLm9yZy8yMDA2L3hicmxkaSc+DQoJCQkJPCEtLWlYQlJMIGNvbnRlbnQgY29udGludWVzIC0tPg0KCQkJPC9odG1sPg==</xbrl:EncodedInlineXbrl> </xbrl:Statements>



Page 23 of 30

5.3 Sample XBRLSubmissionResponse

<ns3:XBRLSubmissionResponse xmlns:ns2="http://www.ros.ie/schemas/rostypes/" xmlns:ns3="http://www.revenue.ie/schemas/xbrl/"> <ns3:AcknowledgementNumber>4905858914</ns3:AcknowledgementNumber>

</ns3:XBRLSubmissionResponse>

5.4 Sample CheckXBRLSubmissionRequest

<xbrl:CheckXBRLSubmissionRequest xmlns:xbrl="http://www.revenue.ie/schemas/xbrl/"> <xbrl:AcknowledgementNumber>5376663575</xbrl:AcknowledgementNumber>

</xbrl:CheckXBRLSubmissionRequest>

5.5 Sample CheckXBRLSubmissionResponse <ns3:CheckXBRLSubmissionResponse rqSuccess="true" xmlns:ns2="http://www.ros.ie/schemas/rostypes/" xmlns:ns3="http://www.revenue.ie/schemas/xbrl/"> <ns3:Status>0</ns3:Status> <ns3:ValidationDetail Severity="Error"> <ns3:Code>#NumericItemMustUseContextRefAndUnitRefAttribute </ns3:Code> <ns3:Message Language="E">Error in "http://www.xbrl.org/uk/gaap/core/2009-09-01#IntangibleFixedAssetsCostOrValuation (13200000)." The numeric item must use context reference and unit reference attribute. </ns3:Message> <ns3:Reference> <ns3:Message Language="E">For more information, please see the XBRL 2.1 recommendation. http://www.xbrl.org/uk/gaap/core/2009-09-01#IntangibleFixedAssetsCostOrValuation (13200000) </ns3:Message> <ns3:URL>http://www.xbrl.org/Specification/XBRL-RECOMMENDATION-2003-12-31+Corrected-Errata-2008-07-02.htm#_4.6.2http://www.xbrl.org/uk/gaap/core/2009-09-01#IntangibleFixedAssetsCostOrValuation (13200000)</ns3:URL> </ns3:Reference> </ns3:ValidationDetail> <ns3:ValidationDetail Severity="Error"> <ns3:Code>#UnitRefAttributeMustOccurInNumericItem </ns3:Code> <ns3:Message Language="E">Error in "http://www.xbrl.org/uk/gaap/core/2009-09-01#IntangibleFixedAssetsCostOrValuation (13200000)." Numeric items MUST include a "unitRef" attribute referencing a unit element in the same XBRL instance. In the XML Schema for XBRL instances, item is defined as an abstract element. This means that it will never appear in its own right in an XBRL instance. Therefore, all elements representing single facts or business measurements defined in an XBRL taxonomy document and reported in an XBRL instance MUST be either (a) members of the substitution group item; or, (b) members of a substitution group originally based on item. XBRL taxonomies include taxonomy schemas that contain such element definitions. item elements might need to be referenced from elsewhere (such as from a footnote) therefore taxonomy authors SHOULD NOT prohibit the id attribute inherited from the base XBRL item type.</ns3:Message> <ns3:Reference> <ns3:Message Language="E">For more information, please see section 4.6 of the XBRL 2.1 recommendation.http://www.xbrl.org/uk/gaap/core/2009-09-01#IntangibleFixedAssetsCostOrValuation (13200000)</ns3:Message> <ns3:URL>http://www.xbrl.org/Specification/XBRL-RECOMMENDATION-2003-12-31+Corrected-Errata-2008-07-02.htm#_4.6.2http://www.xbrl.org/uk/gaap/core/2009-09-01#IntangibleFixedAssetsCostOrValuation (13200000)</ns3:URL> </ns3:Reference> </ns3:ValidationDetail>


Page 24 of 30

</ns3:CheckXBRLSubmissionResponse>


Page 25 of 30

5.6 Sample Inline XBRLValidationRequest

<rosxbrl:XBRLValidationRequest xmlns:rosxbrl="http://www.revenue.ie/schemas/xbrl/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <rosxbrl:ReturnDetails> <rosxbrl:AccountType>Corporation Tax</rosxbrl:AccountType> <rosxbrl:PeriodStartDate>01/11/2011</rosxbrl:PeriodStartDate> <rosxbrl:PeriodEndDate>31/10/2012</rosxbrl:PeriodEndDate> </rosxbrl:ReturnDetails> <rosxbrl:Statements> <rosxbrl:InlineXbrl> <html xmlns='http://www.w3.org/1999/xhtml' xmlns:iso4217='http://www.xbrl.org/2003/iso4217' xmlns:ix='http://www.xbrl.org/2008/inlineXBRL' xmlns:link='http://www.xbrl.org/2003/linkbase' xmlns:xbrli='http://www.xbrl.org/2003/instance' xmlns:xlink='http://www.w3.org/1999/xlink' xmlns:ixt='http://www.xbrl.org/inlineXBRL/transformation/2010-04-20' xmlns:uk-gaap="http://www.xbrl.org/uk/gaap/core/2009-09-01" xmlns:uk-bus="http://www.xbrl.org/uk/cd/business/2009-09-01" xmlns:uk-direp="http://www.xbrl.org/uk/reports/direp/2009-09-01" xmlns:uk-aurep="http://www.xbrl.org/uk/reports/aurep/2009-09-01" xmlns:uk-countries="http://www.xbrl.org/uk/cd/countries/2009-09-01" xmlns:ie-common="http://www.xbrl-ie.org/common/core/DRAFT" xmlns:ie-gaap="http://www.xbrl-ie.org/gaap/core/DRAFT" xmlns:xbrldi='http://xbrl.org/2006/xbrldi'>  </html> </rosxbrl:InlineXbrl> </rosxbrl:Statements> </rosxbrl:XBRLValidationRequest>

5.7 Sample Encoded Inline XBRLValidationRequest

<rosxbrl:XBRLValidationRequest xmlns:rosxbrl="http://www.revenue.ie/schemas/xbrl/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <rosxbrl:ReturnDetails> <rosxbrl:AccountType>Corporation Tax</rosxbrl:AccountType> <rosxbrl:PeriodStartDate>01/11/2011</rosxbrl:PeriodStartDate> <rosxbrl:PeriodEndDate>31/10/2012</rosxbrl:PeriodEndDate> </rosxbrl:ReturnDetails> <rosxbrl:Statements> <rosxbrl:Statements fileName="wsB64test"> <rosxbrl:EncodedInlineXbrl>PGh0bWwgeG1sbnM9J2h0dHA6Ly93d3cudzMub3JnLzE5OTkveGh0bWwnIHhtbG5zOmlzbzQyMTc9J2h0dHA6Ly93d3cueGJybC5vcmcvMjAwMy9pc280MjE3JyB4bWxuczppeD0naHR0cDovL3d3dy54YnJsLm9yZy8yMDA4L2lubGluZVhCUkwnIHhtbG5zOmxpbms9J2h0dHA6Ly93d3cueGJybC5vcmcvMjAwMy9saW5rYmFzZScgeG1sbnM6eGJybGk9J2h0dHA6Ly93d3cueGJybC5vcmcvMjAwMy9pbnN0YW5jZScgeG1sbnM6eGxpbms9J2h0dHA6Ly93d3cudzMub3JnLzE5OTkveGxpbmsnIHhtbG5zOml4dD0naHR0cDovL3d3dy54YnJsLm9yZy9pbmxpbmVYQlJML3RyYW5zZm9ybWF0aW9uLzIwMTAtMDQtMjAnIHhtbG5zOnVrLWdhYXA9Imh0dHA6Ly93d3cueGJybC5vcmcvdWsvZ2FhcC9jb3JlLzIwMDktMDktMDEiIHhtbG5zOnVrLWJ1cz0iaHR0cDovL3d3dy54YnJsLm9yZy91ay9jZC9idXNpbmVzcy8yMDA5LTA5LTAxIiB4bWxuczp1ay1kaXJlcD0iaHR0cDovL3d3dy54YnJsLm9yZy91ay9yZXBvcnRzL2RpcmVwLzIwMDktMDktMDEiIHhtbG5zOnVrLWF1cmVwPSJodHRwOi8vd3d3Lnhicmwub3JnL3VrL3JlcG9ydHMvYXVyZXAvMjAwOS0wOS0wMSIgeG1sbnM6dWstY291bnRyaWVzPSJodHRwOi8vd3d3Lnhicmwub3JnL3VrL2NkL2NvdW50cmllcy8yMDA5LTA5LTAxIiB4bWxuczppZS1jb21tb249Imh0dHA6Ly93d3cueGJybC1pZS5vcmcvY29tbW9uL2NvcmUvRFJBRlQiIHhtbG5zOmllLWdhYXA9Imh0dHA6Ly93d3cueGJybC1pZS5vcmcvZ2FhcC9jb3JlL0RSQUZUIiB4bWxuczp4YnJsZGk9J2h0dHA6Ly94YnJsLm9yZy8yMDA2L3hicmxkaSc+DQoJCQkJPCEtLWlYQlJMIGNvbnRlbnQgY29udGludWVzIC0tPg0KCQkJPC9odG1sPg==</rosxbrl:EncodedInlineXbrl> </rosxbrl:Statements>

</rosxbrl:XBRLValidationRequest>


Page 26 of 30

<xbrl:XBRLSubmissionRequest xmlns:xbrl="http://www.revenue.ie/schemas/xbrl/"> <xbrl:ReturnDetails> <xbrl:AccountType>Corporation Tax</xbrl:AccountType> <xbrl:RegistrationNumber>9952614C</xbrl:RegistrationNumber> <xbrl:PeriodStartDate>01/11/2011</xbrl:PeriodStartDate> <xbrl:PeriodEndDate>31/10/2012</xbrl:PeriodEndDate> </xbrl:ReturnDetails> <xbrl:Statements fileName="wsB64test"> <xbrl:EncodedInlineXbrl>PGh0bWwgeG1sbnM9J2h0dHA6Ly93d3cudzMub3JnLzE5OTkveGh0bWwnIHhtbG5zOmlzbzQyMTc9J2h0dHA6Ly93d3cueGJybC5vcmcvMjAwMy9pc280MjE3JyB4bWxuczppeD0naHR0cDovL3d3dy54YnJsLm9yZy8yMDA4L2lubGluZVhCUkwnIHhtbG5zOmxpbms9J2h0dHA6Ly93d3cueGJybC5vcmcvMjAwMy9saW5rYmFzZScgeG1sbnM6eGJybGk9J2h0dHA6Ly93d3cueGJybC5vcmcvMjAwMy9pbnN0YW5jZScgeG1sbnM6eGxpbms9J2h0dHA6Ly93d3cudzMub3JnLzE5OTkveGxpbmsnIHhtbG5zOml4dD0naHR0cDovL3d3dy54YnJsLm9yZy9pbmxpbmVYQlJML3RyYW5zZm9ybWF0aW9uLzIwMTAtMDQtMjAnIHhtbG5zOnVrLWdhYXA9Imh0dHA6Ly93d3cueGJybC5vcmcvdWsvZ2FhcC9jb3JlLzIwMDktMDktMDEiIHhtbG5zOnVrLWJ1cz0iaHR0cDovL3d3dy54YnJsLm9yZy91ay9jZC9idXNpbmVzcy8yMDA5LTA5LTAxIiB4bWxuczp1ay1kaXJlcD0iaHR0cDovL3d3dy54YnJsLm9yZy91ay9yZXBvcnRzL2RpcmVwLzIwMDktMDktMDEiIHhtbG5zOnVrLWF1cmVwPSJodHRwOi8vd3d3Lnhicmwub3JnL3VrL3JlcG9ydHMvYXVyZXAvMjAwOS0wOS0wMSIgeG1sbnM6dWstY291bnRyaWVzPSJodHRwOi8vd3d3Lnhicmwub3JnL3VrL2NkL2NvdW50cmllcy8yMDA5LTA5LTAxIiB4bWxuczppZS1jb21tb249Imh0dHA6Ly93d3cueGJybC1pZS5vcmcvY29tbW9uL2NvcmUvRFJBRlQiIHhtbG5zOmllLWdhYXA9Imh0dHA6Ly93d3cueGJybC1pZS5vcmcvZ2FhcC9jb3JlL0RSQUZUIiB4bWxuczp4YnJsZGk9J2h0dHA6Ly94YnJsLm9yZy8yMDA2L3hicmxkaSc+DQoJCQkJPCEtLWlYQlJMIGNvbnRlbnQgY29udGludWVzIC0tPg0KCQkJPC9odG1sPg==</xbrl:EncodedInlineXbrl> </xbrl:Statements>


5.8 Sample XBRLValidationResponse

<ns3:XBRLValidationResponse xmlns:ns2="http://www.ros.ie/schemas/rostypes/" xmlns:ns3="http://www.revenue.ie/schemas/xbrl/"> <ns3:AcknowledgementNumber>5758282998</ns3:AcknowledgementNumber>

</ns3:XBRLValidationResponse>

5.9 Sample CheckXBRLValidationRequest

<xbrl:CheckXBRLValidationRequest xmlns:xbrl="http://www.revenue.ie/schemas/xbrl/"> <xbrl:AcknowledgementNumber>5514260226</xbrl:AcknowledgementNumber>

</xbrl:CheckXBRLValidationRequest>

5.10 Sample CheckXBRLValidationResponse

<ns3:CheckXBRLValidationResponse rqSuccess="true" xmlns:ns2="http://www.ros.ie/schemas/rostypes/" xmlns:ns3="http://www.revenue.ie/schemas/xbrl/"> <ns3:Status>0</ns3:Status> <ns3:ValidationDetail Severity="Error"> <ns3:Code>Entity Identifier Scheme</ns3:Code> <ns3:Message Language="E">Context entity identifier scheme (http://www.companieshouse.gov.uk/) is not supported.</ns3:Message> <ns3:Reference> <ns3:Message Language="E"/> </ns3:Reference> </ns3:ValidationDetail> <ns3:ValidationDetail Severity="Error">


Page 27 of 30

<ns3:Code>Accounting Period</ns3:Code> <ns3:Message Language="E">Period End Date (uk-bus:EndDateForPeriodCoveredByReport) is 2009-05-31 must be 2011-12-31 or later</ns3:Message> <ns3:Reference> <ns3:Message Language="E"/> </ns3:Reference> </ns3:ValidationDetail> </ns3:CheckXBRLValidationResponse>


Page 28 of 30

6 APPENDIX 1 Any further Information

<html

xmlns='http://www.w3.org/1999/xhtml'

xmlns:iso4217='http://www.xbrl.org/2003/iso4217'

xmlns:ix='http://www.xbrl.org/2008/inlineXBRL'

xmlns:link='http://www.xbrl.org/2003/linkbase'

xmlns:xbrli='http://www.xbrl.org/2003/instance'

xmlns:xlink='http://www.w3.org/1999/xlink'

xmlns:ixt='http://www.xbrl.org/inlineXBRL/transformation/2010-04-20'

xmlns:uk-gaap="http://www.xbrl.org/uk/gaap/core/2009-09-01"

xmlns:uk-bus="http://www.xbrl.org/uk/cd/business/2009-09-01"

xmlns:uk-direp="http://www.xbrl.org/uk/reports/direp/2009-09-01"

xmlns:uk-aurep="http://www.xbrl.org/uk/reports/aurep/2009-09-01"

xmlns:uk-countries="http://www.xbrl.org/uk/cd/countries/2009-09-01"

xmlns:ie-common="http://www.xbrl-ie.org/common/core/DRAFT"

xmlns:ie-gaap="http://www.xbrl-ie.org/gaap/core/DRAFT"

xmlns:xbrldi='http://xbrl.org/2006/xbrldi'>



</html>

<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <XBRLValidationResponse Language="E" xmlns:ns2="http://www.revenue.ie/schemas/common/revenue-types-v1" xmlns="http://www.revenue.ie/schemas/xbrl/request"> <Mode>online-submit</Mode> <FormType>754</FormType> <Prn>5996484131</Prn> <Status>0</Status> <Detail Severity="Error"> <Code>#ElementWithPeriodTypeDurationMustContainForeverOrValidSeqOfStartDateAndEndDate</Code> <Message Language="E">Error in "http://www.xbrl.org/uk/gaap/core/2009-09-01#ControllingPartyUltimateControllingParty (true)." For an item element with periodType="duration," the period MUST contain a "forever" element or a set of "startDate" and "endDate" elements.</Message> <Reference> <Message Language="E">For more information, please see section 4.7.2 of the XBRL 2.1 recommendation.http://www.xbrl.org/uk/gaap/core/2009-09-01#ControllingPartyUltimateControllingParty (true)</Message> <URL>http://www.xbrl.org/Specification/XBRL-RECOMMENDATION-2003-12-31+Corrected-Errata-2008-07-02.htm#_4.7.2http://www.xbrl.org/uk/gaap/core/2009-09-01#ControllingPartyUltimateControllingParty (true)</URL> </Reference> </Detail> <Detail Severity="Error"> <Code>#ExplicitMemberNotExplicitDimensionError</Code>


Page 29 of 30

<Message Language="E">Dimensions Validation Error: In the context "http://www.xbrl.org/2003/instance#context ()[ID: FY2008_Motor_vehicles1]" (segment), the reported element "uk-gaap_BusinessSegment13" refers to "http://xbrl.org/2006/xbrldi#explicitMember (uk-gaap_BusinessSegment13)" which is not an explicit dimension. The content of the dimension attribute of an xbrldi:explicitMember element MUST be the QName of an explicit dimension element defined in a schema within the DTS of the instance document.</Message> <Reference> <Message Language="E">For more information, please see section 3.1.4.5.2 of the Dimensions 1.0 recommendation. http://www.xbrl.org/2003/instance#context ()[ID: FY2008_Motor_vehicles1],segment,http://xbrl.org/2006/xbrldi#explicitMember (uk-gaap_BusinessSegment13),uk-gaap_BusinessSegment13</Message> <URL>http://www.xbrl.org/Specification/XDT-REC-2006-09-18.htm#_3.1.4http://www.xbrl.org/2003/instance#context ()[ID: FY2008_Motor_vehicles1],segment,http://xbrl.org/2006/xbrldi#explicitMember (uk-gaap_BusinessSegment13),uk-gaap_BusinessSegment13</URL> </Reference> </Detail> <Detail Severity="Error"> <Code>#ExplicitMemberUndefinedQNameError</Code> <Message Language="E">Dimensions Validation Error: In the context "http://www.xbrl.org/2003/instance#context ()[ID: FY2008_Plant_and_machinery1]" (segment), the QName value "uk-gaap_AllTangibleFixedAssetsDefault" of the explicit dimension "&http://www.xbrl.org/uk/gaap/core/2009-09-01#TangibleFixedAssetClassesDimension[ID: uk-gaap_TangibleFixedAssetClassesDimension]" is not an element defined in the taxonomy schema. The content of the xbrldi:explicitMember element must be a QName whose global element definition can be found in the taxonomy schema referenced by the namespace of the QName. </Message> <Reference> <Message Language="E">For more information, please see section 3.1.4.5.3 of the Dimensions 1.0 recommendation. http://www.xbrl.org/2003/instance#context ()[ID: FY2008_Plant_and_machinery1],segment,&http://www.xbrl.org/uk/gaap/core/2009-09-01#TangibleFixedAssetClassesDimension[ID: uk-gaap_TangibleFixedAssetClassesDimension],uk-gaap_AllTangibleFixedAssetsDefault</Message> <URL>http://www.xbrl.org/Specification/XDT-REC-2006-09-18.htm#_3.1.4http://www.xbrl.org/2003/instance#context ()[ID: FY2008_Plant_and_machinery1],segment,&http://www.xbrl.org/uk/gaap/core/2009-09-01#TangibleFixedAssetClassesDimension[ID: uk-gaap_TangibleFixedAssetClassesDimension],uk-gaap_AllTangibleFixedAssetsDefault</URL> </Reference> </Detail> <Detail Severity="Error"> <Code>#ExplicitMemberUndefinedQNameError</Code> <Message Language="E">Dimensions Validation Error: In the context "http://www.xbrl.org/2003/instance#context ()[ID: FY2008_Motor_vehicles1]" (segment), the QName value "uk-gaap_BusinessSegment13" of the explicit dimension "http://xbrl.org/2006/xbrldi#explicitMember (uk-gaap_BusinessSegment13)" is not an element defined in the taxonomy schema. The content of the xbrldi:explicitMember element must be a QName whose global element definition can be found in the taxonomy schema referenced by the namespace of the QName. </Message> <Reference> <Message Language="E">For more information, please see section 3.1.4.5.3 of the Dimensions 1.0 recommendation. http://www.xbrl.org/2003/instance#context ()[ID: FY2008_Motor_vehicles1],segment,http://xbrl.org/2006/xbrldi#explicitMember (uk-gaap_BusinessSegment13),uk-gaap_BusinessSegment13</Message> <URL>http://www.xbrl.org/Specification/XDT-REC-2006-09-18.htm#_3.1.4http://www.xbrl.org/2003/instance#context ()[ID: FY2008_Motor_vehicles1],segment,http://xbrl.org/2006/xbrldi#explicitMember (uk-gaap_BusinessSegment13),uk-gaap_BusinessSegment13</URL> </Reference> </Detail> <Detail Severity="Error"> <Code>#SchemaValidationError</Code>


Page 30 of 30

<Message Language="E">There has been a schema validation error in "stream://2" on line number 2, column number 4309. Error message: cvc-datatype-valid.1.2.1: 'falsex' is not a valid value for 'boolean'.</Message> <Reference> <Message Language="E"/> <URL/> </Reference> </Detail> <Detail Severity="Error"> <Code>#SchemaValidationError</Code> <Message Language="E">There has been a schema validation error in "stream://2" on line number 2, column number 4309. Error message: cvc-complex-type.2.2: Element 'uk-bus:EntityDormant' must have no element [children], and the value must be valid.</Message> <Reference> <Message Language="E"/> <URL/> </Reference> </Detail> </XBRLValidationResponse>

Documents

iXBRL Financial Statements Web Service - ROS · XBRL/CheckValidationStatus operation of the iXBRL Financial Statements web service. The element details the current status of the iXBRL