Change Log for Aug 2015 CTP

Design

  • The XLINK specification is now implemented in a specific class, and XBRL linkbase nodes now leverage Gepsio’s implementation of XLINK. The following classes have been refactored to leverage Gepsio’s internal support for the XLINK specification added in this version:
    • Label
    • LabelLink
  • Improved performance of loading an XBRL fragment’s fact collection by setting the capacity of the collection to the maximum number of nodes beneath the XBRL root node before any facts are created and added to the collection, and then trimming the excess after all facts are created and added to the collection. This strategy prevents .NET from having to re-allocate the fact collection each time it needs to expand, which costs time during the fact collection creation process.
  • The list of facts exposed by an XbrlFragment, formerly of type List<Fact>, is now an object of a class called FactCollection. The FactCollection class allows the fact list to be augmented with some internal dictionaries that can be used to find a fact more quickly than simply iterating through a list and checking each fact.
  • Gepsio’s XML service layer has been implemented behind an interface since the Nov 2014 CTP. These interfaces, which have been internal in previous CTPs, is now public. See this blog post for more information for the motivation and rationale behind this change.

New Classes

  • FactCollection: Replaces the simple List<Fact> with additional public methods to quickly find a fact or list of facts by name or ID. The FactCollection class supports public methods such as GetFactById() and GetFactByName() which allows callers to find facts in the collection quickly and efficiently, thanks to internal disctionaries managed by the FactCollection class.
  • PresentableFactTree: A tree of facts arranged in accordance with the information in a presentation linkbase. See this blog post and this blog post for more information.
  • PresentableFactTreeNode: A node in a tree of facts arranged in accordance with the information in a presentation linkbase. See this blog post and this blog post for more information.

New Properties Available on Previously Existing Classes

Element

  • bool IsAbstract: True if the element is an abstract element; false otherwise.

Fact

  • string Id: The ID of the fact.

Label

  • string Label: The value of the label’s “label” attribute.

New Methods Available on Previously Existing Classes

XbrlFragment

  • GetPresentableFactTree()

LabelLink

  • GetLocator(string href)
  • GetLabelArc(string fromAttributeValue)
  • GetLabel(string labelAttributeValue)

Previously Existing Properties Removed from Previously Existing Classes

Item

  • string ID: The ID value is now populated in the base Fact class, making IDs available to both items and tuples.

Label

  • string ID: The ID value is now populated in the base XlinkNode class and its “Label” property.

Conformance

  • None

Conformance Tests in XBRL-CONF-CR5-2012-01-24 Passed by Gepsio

Identifier Scope [Section 4.3 The Item Element]

  • 301-01-IdScopeValid.xml [301.01 Valid example of id attribute.]
  • 301-03-IdScopePeriodDiff.xml [301.03 Mismatch of periodType attribute and referenced context’s period type.]
  • 301-04-IdScopeContextRefToUnit.xml [301.04 contextRef has IDREF to unit element.]
  • 301-05-IdScopeUnitRefToContext.xml [301.05 unitRef has IDREF to context element.]
  • 301-06-FootnoteScopeValid.xml [301.06 Valid example of footnote link href attribute.]
  • 301-08-FootnoteToContext.xml [301.08 href attribute is referencing to context element.]
  • 301-09-FootnoteToUnit.xml [301.09 href attribute is referencing to unit element.]
  • 301-10-FootnoteFromOutOfScope.xml [301.10 The instance contains two footnote links. The second one contains an arc with a from value that does not have a corresponding loc in the same extended link.]
  • 301-11-FootnoteToOutOfScope.xml [301.11 The instance contains two footnote links. The second one contains an arc with a to value that does not have a corresponding footnote resource in the same extended link.]
  • 301-12-FootnoteLocOutOfScope.xml [301.12 The instance contains a footnote link. In the footnote link there is a loc element that has an href that points to a fact in another instance document.]
  • 301-13-FootnoteLocInScope.xml [301.13 The instance contains a footnote link. In the footnote link there is a loc element that has an href that points to a fact in the instance document using the instance document file name with a fragment identifier.]
  • 301-14-FootnoteFromResource.xml [301.14 The instance contains a footnote link. The arc in the footnote link has a from value that matches a footnote resource. This is not valid for the fact-footnote arc role on the arc. The from must point to a loc which in turns points to a fact in the same instance document.]
  • 301-15-FootnoteToLoc.xml [301.15 The instance contains a footnote link. The arc in the footnote link has a from value that matches a footnote resource. This is not valid for the fact-footnote arc role on the arc. The from must point to a loc which in turns points to a fact in the same instance document.]
  • 301-16-FootnoteWithoutLang.xml [301.16 The xml:lang attribute is missing on the footnote resource.]
  • 301-17-FootnoteCustomArcRole.xml [301.17 The footnote custom arc role can relate two footnotes to each other instead of just fact to footnote. (Only the standard footnote arc role is restricted to being from item or tuple locators.) Maybe this might be used to indicate how some footnote is “footnoting” another footnote.]

Context Segments and Scenarios [Section 4.4 The Context Element]

  • 302-01-SegmentValid.xml [302.01 Valid segment in a context]
  • 302-02-SegmentNamespaceInvalid.xml [302.02 Invalid segment in a context; contains an element defined in xbrli namespace]
  • 302-03-ScenarioValid.xml [302.03 Valid scenario in a context]
  • 302-04-ScenarioNamespaceInvalid.xml [302.04 Invalid scenario in a context; contains an element defined in xbrli namespace]
  • 302-05-SegmentSubstitutionInvalid.xml [302.05 Invalid segment in a context; contains an element in substitution group of xbrli:item]
  • 302-06-ScenarioSubstitutionInvalid.xml [302.06 Invalid scenario in a context; contains an element in substitution group of xbrli:item]
  • 302-07-SegmentEmptyContent.xml [302.07 Segment in a context contains an element with empty content]
  • 302-08-ScenarioEmptyContent.xml [302.08 Scenario in a context contains an element with empty content]
  • 302-09-PeriodDateTimeValid.xml [302.09 Valid duration context with start date earlier than end date]
  • 302-10-PeriodDateTimeInvalid.xml [302.10 Invalid duration context with start date later than end date]
  • 302-11-DecimalAttributeOnSegmentInconsistent.xbrl [302.11 Two contexts are S-Equal even though a decimal-valued attribute in their segment elements have different lexical representations. The contexts are S-equal, so a calculation inconsistency MUST be signaled.]
  • 302-12-DecimalAttributeOnScenarioInconsistent.xbrl [302.12 Two contexts are S-Equal even though a decimal-valued attribute in their scenario elements have different lexical representations. The contexts are S-equal, so a calculation inconsistency MUST be signaled.]

Period Type Consistency [Section 4.3 The Item Element]

  • 303-01-PeriodInstantValid.xml [303.01 instant context and item defined with PeriodType=”instant”]
  • 303-02-PeriodDurationValid.xml [303.02 duration context and item defined with PeriodType=”duration”]
  • 303-03-PeriodInstantInvalid.xml [303.03 duration context and item defined with PeriodType=”instant”]
  • 303-04-PeriodDurationInvalid.xml [303.04 instant context and item defined with PeriodType=”duration”]
  • 303-05-ForeverElementewithInstancePeriodTypeReportedasForever.xbrl [ForeverConcept with Instant Period Type is not allowed]

Unit of Measure Consistency [Section 4.4 The Context Element]

  • 304-01-monetaryItemTypeUnitsRestrictions.xml [304.01 An element with a monetary item type has an ISO currency code for its units (using the standard ISO namespace prefix).]
  • 304-02-monetaryItemTypeUnitsRestrictions.xml [304.02 An element with a monetary item type has an ISO currency code for its units (using a non-standard ISO namespace prefix).]
  • 304-03-monetaryItemTypeUnitsRestrictions.xml [304.03 An element with a type derived by restriction from the monetary item type has an ISO currency code for its units.]
  • 304-04-monetaryItemTypeUnitsRestrictions.xml [304.04 An element with a type derived by restriction from monetary item type has an ISO currency code for its units (using a non-standard ISO namespace prefix).]
  • 304-05-monetaryItemTypeUnitsRestrictions.xml [304.05 An element with a non-monetary item type has an ISO currency code for its units (using the standard ISO namespace prefix).]
  • 304-06-monetaryItemTypeUnitsRestrictions.xml [304.06 An element with a monetary item type does not have an ISO currency code for its units – the namespace is wrong.]
  • 304-07-monetaryItemTypeUnitsRestrictions.xml [304.07 An element with a monetaryItemType does not have an ISO currency code for its units – the local name is wrong.]
  • 304-08-monetaryItemTypeUnitsRestrictions.xml [304.08 An element with a type derived by restriction from monetaryItemType does not have an ISO currency code for its units – the namespace is wrong.]
  • 304-09-monetaryItemTypeUnitsRestrictions.xml [304.09 An element with a type derived by restriction from monetaryItemType does not have an ISO currency code for its units – the local name is wrong.]
  • 304-10-pureItemTypeUnitsRestrictions.xml [304.10 An item with a pureItemType data type MUST have a unit element and the local part of the measure MUST be “pure” with a namespace prefix that resolves to a namespace of “http://www.xbrl.org/2003/instance&#8221;.]
  • 304-11-pureItemTypeUnitsRestrictions.xml [A measure element with a namespace prefix that resolves to the “http://www.xbrl.org/2003/instance&#8221; namespace MUST have a local part of either “pure” or “shares”. The value ‘impure’ is not a valid measure in the XBRL instance namespace.]
  • 304-12-pureItemTypeUnitsRestrictions.xml [Unlike for monetaryItemType and sharesItemType, there is no constraint (in 4.8.2 or elsewhere) requiring an item with a pureItemType data type to have a particular kind of unit.]
  • 304-12a-pureItemTypeUnitsRestrictions.xml [Same as V-12, but the pure measure has no prefix and the default namespace is undefined.]
  • 304-13-sharesItemTypeUnitsRestrictions.xml [304.13 For facts that are of the sharesItemType, units MUST have A single measure element. The local part of the measure MUST be “shares” and the namespace prefix that MUST resolve to http://www.xbrl.org/2003/instance%5D
  • 304-14-sharesItemTypeUnitsRestrictions.xml [304.14 For facts that are DERIVED BY RESTRICTION from the sharesItemType, units MUST have A single measure element. The local part of the measure MUST be “shares” and the namespace prefix that MUST resolve to http://www.xbrl.org/2003/instance%5D
  • 304-15-pureItemTypeUnitsRestrictions.xml [304.15 For facts that are of shares item type, units MUST have A single measure element. The local part of the measure MUST be “shares” and the namespace prefix that MUST resolve to http://www.xbrl.org/2003/instance. In this case the unit has two measure elements, both of which are pure.]
  • 304-15a-sharesItemTypeUnitsRestrictions.xml [Same as V-15 but in this case the unit has has shares but no prefix and the default namespace is undefined.]
  • 304-16-unitsInSimplestForm.xml [304.16 The units must not have numerator and denominator measures that cancel.]
  • 304-17-sameOrderMeasuresValid.xml [304.17 The units equality test which two units have same order measures.]
  • 304-18-sameOrderDivisionMeasuresValid.xml [304.18 The units equality test which two units have same order divisions.]
  • 304-19-differentOrderMeasuresValid.xml [304.19 The units equality test which two units have different order measures.]
  • 304-20-differentOrderDivisionMeasuresValid.xml [304.20 The units equality test which two units have division elements which their order of child measures are different.]
  • 304-21-measuresInvalid.xml [304.21 it tries to essence-alias equality of two elements with different units : where one is pure-feet and the second is pure-pounds. so the alias essence check is invalid and it should throw an error in xbrl validation]
  • 304-22-divisionMeasuresInvalid.xml [304.22 The test tried to essense-alias equality check of two elements with different units : where one is unit between “pure-inch / pound-feet” and other “pure-feet / pound-inch”. The tests is invalid as it should throw an error during xbrl validation.]
  • 304-23-Calculation-item-does-not-match-unit.xml [Variation of 304-15 where the type of the fact value does not match that of the type of the reported element. Shares type versus Monetary unit]
  • 304-24-valid-ISO-unit-of-measue.xml [Valid ISO unit of measurement example]
  • 304-25-measure-reported-with-prefix-undefined-instance.xbrl [Measure reported with prefix undefined is considered XBRL invalid]
  • 304-26-monetaryItemTypeUnitsRestrictions.xml [Monetary item reported with unit having a denominator.]

Decimal and Precision Mutual Exclusion and prohibition on nil items [Section 4.4 Items]

  • 305-01-DecimalOnlySpecified.xml [305.01 item has only Decimals specified]
  • 305-02-PrecisionOnlySpecified.xml [305.02 item has only Precision specified]
  • 305-03-NoDecimalOrPrecisionSpecified.xml [305.03 item has neither Decimals nor Precision specified]
  • 305-04-BothDecimalAndPrecisionSpecified.xml [305.04 item has both Decimals and Precision specified]
  • 305-05-DecimalSpecifiedOnNilItem.xml [305.05 nil item has Decimals specified]
  • 305-06-PrecisionSpecifiedOnNilItem.xml [305.06 nil item has Precision specified]
  • 305_07_invalid_instance.xbrl [305.07 a genuine inconsistency due to roll up of child values]
  • 305-08-UnitsSpecifiedOnNilItem.xml [305.08 nil items have no decimals or precision, with unitref, but the type specifies fixed values for decimals and precision.]

Required Arc in Definition Linkbase [Section 5.5.6.4.1.5]

  • 306-01-RequiredInstanceValid.xml [306.01 The instance contains two elements in the same context. The presence of one element forces the presence of the other.]
  • 306-02-RequiredInstanceTupleValid.xml [306.02 The instance contains an item and a tuple. The presence of the tuple forces the presence of the item.]
  • 306-03-RequiredInstanceInvalid.xml [306.03 The instance contains an item and a tuple. The presence of the tuple forces the presence of the item.]

Schema References [Section 5 Taxonomies]

  • 307-01-SchemaRefExample.xml [307.01 A schemaRef element MUST hold the URI of a schema. In this case it does.]
  • 307-02-SchemaRefCounterExample.xml [307.01 A schemaRef element MUST hold the URI of a schema. In this case it does not because the second reference to a schema actually points to an XML document that is a label linkbase. ]
  • 307-03-SchemaRefXMLBase.xml [307.03 schemaRef elements MUST hold the URI of Schemas. In this case the requirement is not satisfied because the schema reference has to be resolved using the XML base attribute that ensures the schemaRef URI resolves to the XML document in the base directory. This document, however, is a label linkbase, not a schema. If the XML base attribute value is not used then the schema in the same directory as the instance is discovered and no issues are noticed.]

Duplicate instance roleRef and duplicate arcroleRefs [3.5.2.4.5 and 3.5.2.5.5 duplicate instance roleRef and arcroleRef elements.]

  • 308-01-instance.xml [Instance contains two role references to the same URI, INVALID]
  • 308-02-instance.xml [Instance contains two arcrole references to the same URI, INVALID]

LAX validation tests [Test that LAX validation is performed]

  • 314-lax-validation-01.xml [Segment has an element for which there is no definition, so it is allowed; item has an attribute with no definition, so it is allowed. The definitions are imported to the discovered taxonomy.]
  • 314-lax-validation-02.xml [Segment has an element for which there is no definition, so it is allowed; item has an attribute with no definition, so it is allowed. The definitions are found by schemaLocation from the instance document.]
  • 314-lax-validation-03.xml [Same as v-01 but segment has an element defined as integer with string contents]
Advertisements