90309: xfi:fact-explicit-dimension-value

  1. The XBRL Standard
  2. XBRL Specifications
  3. Registries
  4. Functions Registry 1.0
  5. Functions Registry
  6. xfi:fact-explicit-dimension-value
  7. 90309: xfi:fact-explicit-dimension-value

Documentation

Owners

Name Affiliation Email Start End
Herm Fischer UBMatrix / Mark V Systems fischer@markv.com 06-02-2008 at 12:55:00

References

function definition

Test Case Variations

V-01 Location dimension for Mount Kilimanjaro

Documentation

Inputs

Outputs

  • Result test: $result instance of xs:QName? and count( $result ) eq 1 and $result eq QName('http://xbrl.org/formula/conformance/example','t:Tanzania')

V-01a Location default dimension for Vinson Massif

Documentation

Mt Vinson uses the Antarctica default dimension, so although it is not physically reported in the context, it is virtually reported due to the default for the dimension.

Inputs

Outputs

  • Result test: $result instance of xs:QName? and count( $result ) eq 1 and $result eq QName('http://xbrl.org/formula/conformance/example','t:Antarctica')

V-02 Location dimension for Peak concept Aurora Borealis (whose context lacks the location dimension)

Documentation

Inputs

Outputs

  • Result test: $result instance of xs:QName? and count( $result ) eq 1 and $result eq QName('http://xbrl.org/formula/conformance/example','t:Antarctica')

V-03 Location dimension for AtmosphericPhenomenon concept with open hypercube 'leaks' global dimension-default value

Documentation

Location dimension for AtmosphericPhenomenon concept Aurora Borealis (whose hypercube lacks the location dimension): The AtmosphereicPhenomenon primary item has an open hypercube. (It isn't supposed to have a location dimension, but as this variation was originally written, because the hypercube is open, and the location dimension-default is global, that causes the location dimension to be valid and the default value applies to facts of this primary item despite it being 'unwanted'. That is 'fixed' in variation V-03a.)

Inputs

Outputs

  • Result test: $result instance of xs:QName? and count( $result ) eq 1 and $result eq QName('http://xbrl.org/formula/conformance/example','t:Antarctica')

V-03a Location dimension for AtmosphericPhenomenon, closed hypercube, no value for absent dimension

Documentation

Demonstrates that the default value is reported even when it is not dimensionally valid for the primary item. Same as V-03 but regardless that the Atmospheric Phenomenon primary item now has a closed hypercube (by a higher priority arc which overrides with closed=true) so that the location dimension is not dimensionally valid or expected, despite being a global default. However this test case assures that the unwanted default dimension value is reported for facts of this primary item.

Inputs

Outputs

  • Result test: $result instance of xs:QName? and count( $result ) eq 1 and $result eq QName('http://xbrl.org/formula/conformance/example','t:Antarctica')

V-04 Error of concept argument which is not a dimension

Documentation

Inputs

Outputs

  • Error code: xfie:invalidExplicitDimensionQName

V-05 Error of non-XBRL element argument as dimension argument

Documentation

Inputs

Outputs

  • Error code: xfie:invalidExplicitDimensionQName

V-06 Raises an error for an attribute declaration argument

Documentation

Tests that error is detected when the concept name argument declares an attribute.

Inputs

Outputs

  • Error code: xfie:invalidExplicitDimensionQName

V-07 Raises an error for an xbrli namespace'ed argument

Documentation

Tests that error is detected when the concept qname is xbrli:item

Inputs

Outputs

  • Error code: xfie:invalidExplicitDimensionQName

V-08 Dimension can be located in either segment or scenario, for this variation appears in the segment, to test that function is looking in only desired location for value.

Documentation

Inputs

Outputs

  • Result test: $result instance of xs:QName? and count( $result ) eq 1 and $result eq QName('http://xbrl.org/formula/conformance/example','t:ExplDim1Mbr1')

V-09 Dimension can be located in either segment or scenario but for this variation appears in the scenario instead of segment, to test that function is looking in only desired location for value.

Documentation

Inputs

Outputs

  • Result test: $result instance of xs:QName? and count( $result ) eq 1 and $result eq QName('http://xbrl.org/formula/conformance/example','t:ExplDim1Mbr1')

Revisions

Name On Details
Herm Fischer 06-02-2008 at 12:55:00 Created the test case.
Herm Fischer 16-03-2008 at 08:30:00 Added variations for bi-locational dimension with value in desired and opposite locations.
Herm Fischer 22-05-2008 at 08:30:00 Added variation v-01a for default dimension value.
Herm Fischer 01-09-2008 at 00:00:00 Made the function segment/scenario agnostic, renamed without segment/scenario in name.
Herm Fischer 16-11-2008 at 00:00:00 Changed V-03 to empty result.
Herm Fischer 28-12-2010 at 00:00:00 Updated preceding change, to correspond with 2009 base spec WG resolving applicability of dimension defaults to primary items (bug 343). In V-03 the primary item has an open hypercube, so the location dimension is allowed, and has a default value, which is applied to V-03's primary item (despite being silly for the example). A new variation is added, V-03a, closing that hypercube, so the unwanted location dimension is not allowed and does not show up as a default member value. Thanks to IHR for identifying this issue and helping.
Herm Fischer 01-03-2011 at 16:00:00 Changed v-03a to report the default value even when a closed hypercube does not allow it. Accompanies function change to clarify that dimension default values are reported for a dimension without respect to such a default value's validity for a given primary item.