Copyright ©2009 XBRL International Inc., All Rights Reserved.
Circulation of this Recommendation is unrestricted. This document is normative. Recipients are invited to submit comments to formula-feedback@xbrl.org, and to submit notification of any relevant patent rights of which they are aware and provide supporting documentation.
1 Introduction
1.1 Background
1.2 Relationship to other work
1.3 Language independence
1.4 Terminology
1.5 Document conventions (non-normative)
1.6 Namespaces and namespace prefixes
2 Syntax
2.1 Inputs
2.1.1 Input function call
2.2 Outputs
2.2.1 Output tests
A Normative schema
B References
C Intellectual property status (non-normative)
D Acknowledgements (non-normative)
E Document history (non-normative)
F Errata corrections in this document
This specification defines syntax for the inputs and outputs of function registry conformance suite tests.
This specification is intended to support the creation, maintenance, and publication of XBRL function conformance suites.
The official language of XBRL International's own work products is English and the preferred spelling convention is UK English.
This specification is consistent with the definitions of any of the terms defined in specifications that it depends on.
Documentation conventions follow those set out in the XBRL Variables Specification [VARIABLES].
Namespace prefixes [XML NAMES] will be used
for elements and attributes in
the form ns:name where ns is the
namespace prefix and name is the local name.
Throughout this specification, the mappings
from namespace prefixes to actual namespaces is consistent
with
Table
1.
The prefix column in Table 1 is non normative. The namespace URI column is normative.
| Prefix | Namespace URI |
|---|---|
cfcn
|
http://xbrl.org/2008/conformance/function
|
cfcne
|
http://xbrl.org/2008/conformance/function/error
|
xml
|
http://www.w3.org/XML/1998/namespace
|
This specification only provides a textual declaration of syntax constraints when those constraints are not expressed by the normative schema supplied with this specification.
Explanations of elements and attributes are only supplied when explanations are not already provided in other specifications.
Unless explicitly stated otherwise, a reference to a specific element MUST be read as a reference to that element or to any element in its substitution group .
Function conformance suite tests MAY have input files, and input XPath expressions selecting information from the input files to use as function parameter values.
The syntax for the input files is defined in the Conformance Specification [CONFORMANCE].
The syntax for the input function call is provided by the
<cfcn:call>
element.
If provided, the
@file attribute MUST contain the ID of
one of the test case variation's input files.
The content of a
<cfcn:call>
is interpreted as an XPath expression that
is expected to be evaluated using a context that is an empty sequence if there is no
@file attribute and that is the root element of the specified input file otherwise.
The XPath expression will generally call the function being tested.
A function test case variation MUST have exactly one input function call among its inputs.
Function conformance suite tests MAY have error codes as outputs.
They MAY also produce results that are expected to fulfil certain conditions
that can be tested for by executing XPath expressions and requiring the result to be an effective
Boolean value of true. The syntax for error code outputs is defined in the XBRL
Conformance Specification [CONFORMANCE].
The syntax for the output tests is provided by the
<cfcn:test>
element.
The content of a
<cfcn:test>
is interpreted as an XPath expression that
is expected to be evaluated using a context that is the result of evaluating the
XPath expression that provided as an input to the test case variation.
The XPath expression in the
<cfcn:test>
element
MAY contain a reference to the variable $result
that is equal to the result of evaluating the XPath expression
provided as an input to the test case variation.
The result of evaluating the output test XPath expression MUST be an effective
Boolean value of true if the test is to be considered passed.
A test case variation MAY contain more than one output test.
The following is the XML schema provided as part of this specification. This is normative. Non-normative versions (which should be identical to these except for appropriate comments indicating their non-normative status) are also provided as separate files for convenience of users of the specification.
NOTE: (non-normative) Following the schema maintenance policy of XBRL International, it is the intent (but is not guaranteed) that the location of non-normative versions of these schemas on the web will be as follows:
http://www.xbrl.org/2008/ - during the drafting process for
this specification this directory should contain a copy of the
most recent published version of the schema at
http://www.xbrl.org/2008/conformanceFunction.xsd.
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to XBRL International or XBRL organizations, except as required to translate it into languages other than English. Members of XBRL International agree to grant certain licenses under the XBRL International Intellectual Property Policy (www.xbrl.org/legal).
This document and the information contained herein is provided on an "AS IS" basis and XBRL INTERNATIONAL DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
The attention of users of this document is directed to the possibility that compliance with or adoption of XBRL International specifications may require use of an invention covered by patent rights. XBRL International shall not be responsible for identifying patents for which a license may be required by any XBRL International specification, or for conducting legal inquiries into the legal validity or scope of those patents that are brought to its attention. XBRL International specifications are prospective and advisory only. Prospective users are responsible for protecting themselves against liability for infringement of patents. XBRL International takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Members of XBRL International agree to grant certain licenses under the XBRL International Intellectual Property Policy (www.xbrl.org/legal).
This document could not have been written without the contributions of many people including the participants in the FWG.
| Date | Author | Details |
|---|---|---|
| 29 January 2008 | Geoff Shuetrim |
First internal working draft created. |
| 30 January 2008 | Geoff Shuetrim |
Simplified the syntax for the input XPath expressions in function tests by including an explicit function call in the XPath expression rather than generating one XPath expression per input parameter of the function being called. Fixed up various XML Schema errors. |
| 09 April 2008 | Geoff Shuetrim |
Introduced the Fixed up various XML Schema errors. |
This appendix contains a list of the errata that have been incorporated into this document. This represents all those errata corrections that have been approved by the XBRL International FWG up to and including 22 June 2009. Hyperlinks to relevant e-mail threads may only be followed by those who have access to the relevant mailing lists. Access to internal XBRL mailing lists is restricted to members of XBRL International Inc.
No errata have been incorporated into this document.