Copyright ©2011 XBRL International Inc., All Rights Reserved.
Circulation of this Candidate Recommendation is unrestricted. This document is normative. Other documents may supersede this document. 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
1.7 XPath usage
2 Syntax
2.1 Tuple production
2.2 Location rules
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
1 Namespaces and namespace prefixes
1 Producing a tuple with three fact items by variables-scope relationships
2 Location rules
The tuples specification provides the means to produce XBRL output instances containing tuples with nested tuples and items.
This specification is a member of a suite of similar specifications that define specific types of criteria that can be used to produce output tuples constructed by multiple related formula evaluations [FORMULA].
This specification depends upon the XBRL Specification [XBRL 2.1], and the XBRL Variables Specification [VARIABLES]. In the event of any conflicts between this specification and the specifications upon which it depends, this specification does not prevail.
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 |
---|---|
tuple
|
http://xbrl.org/2010/formula/tuple
|
xbrltuplee
|
http://xbrl.org/2008/filter/variable/instance/error
|
eg
|
http://example.com/
|
fn
|
http://www.w3.org/2005/xpath-functions
|
link
|
http://www.xbrl.org/2003/linkbase
|
xbrli
|
http://www.xbrl.org/2003/instance
|
xfi
|
http://www.xbrl.org/2008/function/instance
|
xbrldi
|
http://xbrl.org/2006/xbrldi
|
xbrldt
|
http://xbrl.org/2005/xbrldt
|
xl
|
http://www.xbrl.org/2003/XLink
|
xlink
|
http://www.w3.org/1999/xlink
|
xs
|
http://www.w3.org/2001/XMLSchema
|
xsi
|
http://www.w3.org/2001/XMLSchema-instance
|
gen
|
http://xbrl.org/2008/generic
|
variable
|
http://xbrl.org/2008/variable
|
iso4217
|
http://www.xbrl.org/2003/iso4217
|
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.
A tuple is declared by a
<tuple:tuple>
element. This is an equivalent to the
formula
intended to produce output tuples (whereas the formula element produces
output items).
The syntax for the
<tuple:tuple>
element
is defined by the normative schema supplied with this specification.
Tuples are produced in the output instance by a tuple:tuple
element with
a source aspect specifying a concept that is a tuple. (The tuple:tuple
element
is otherwise the same as the formula:formula
element.)
The tuple element has all the behavior, semantics, and error conditions of the formula element (other than that of producing a value for an item).
Facts (items and tuples) are produced in the output instance within a containing element
by a tuple:tuple
element with
a location rule specifying a location aspect that is a containing tuple.
In order to access the source tuple, which is in the output instance, a
variables-scope relationship
from the source tuple to the contents producing formula is required.
(The tuple:tuple
element producing an item fact inside a tuple
is otherwise the same as the formula:formula
element.)
This example shows use of variable-scope relationships to provide an output location of the produced tuple, to be used as the location aspect for dependent nested items. This (variable-scope) approach is the preferred one, because the tuple which is to be the parent of the nested children is unambiguously specified by the variable-scope relationship |
A location rule is an aspect rule that addresses the
location aspect
and that is expressed by the
<tuple:location>
element.
The syntax for the
<tuple:location>
element
is defined by the normative schema supplied with this specification.
A location rule provides specific rules for constructing the fact in the location (as child) of a tuple in the output instance.
The location rule has no child elements, its RAV is its SAV.
If the source contains a QName that is the result
@name
on a variable-scope relationship
from a
<tuple:tuple>
element, then the output fact is produced as a child of that tuple.
(Otherwise the fact is produced as root fact as usual.)
SAV | Location rule | Output location |
---|---|---|
t | RAV is the SAV | Output fact item for this formula has location (as child) of the tuple of variable $t. Tuple t is located in an output instance, $t being the result name on a variable-scope relationship. |
When there is no location rule element, the default location aspect rule applies:
the formula source
is not considered, and the output fact is produced as a child element of the
output XBRL instance's
<xbrli:xbrl>
element.
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/2010/formula/tuple.xsd.
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/2010/formula-tuple.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 Formula Working Group.
Date | Author | Details |
---|---|---|
13 December 2010 | Herm Fischer |
First internal working draft created, drawing extensively on wiki page discussions in 2008 and early 2009, discussions with Fujitsu team at Bank of Japan hosted meeting in early 2009, and initial UBmatrix implementation. |
12 November 2011 | Herm Fischer |
Removed references to producing tuples by means of an instance-variable relationship because multi-instances processing has evolved since this was proposed, and no longer specifies a processing model that would allow a referenced instance to be partially constructed (to have a tuple) and in an extendible state (where items could be added). Now an instance may be fully produced before it is referencable for consumption, which would preclude using an instance containing a tuple to add items into that instance (after it was produced). The only way to produce a tuple is now by variable-scope relationships. |
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 Formula Working Group up to and including 30 November 2011. 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.