Compliance report with the XBRL Conformance suite

Date executed: 2008-08-03T17:27:11.627+0200

Section 4.3 The Item Element
Id: V-1 Description: 301.01 Valid example of id attribute.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/301-01-IdScopeValid.xml
Id: V-2 Description: 301.02 ID is referenced out side of xbrl element. This test is out of scope of Conformance testing. But this is kept in the conformance suite since it is still useful test. Decided by Spec WG.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.DTSDiscoveryException Document is not a Taxonomy, Linkbase or XBRL Instance
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/301-02-IdScopeOutOfScope.xml
Id: V-3 Description: 301.03 Mismatch of periodType attribute and referenced context's period type.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Period type on context of fact {http://example.com/xbrl/taxonomy}fixedAssets at file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/301-03-IdScopePeriodDiff.xml/xbrli:xbrl[1]/example:fixedAssets[1] is (Duration) does not match periof type on item declaration (Instant)
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/301-03-IdScopePeriodDiff.xml
Id: V-4 Description: 301.04 contextRef has IDREF to unit element.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLRuntimeException Context not found for fact
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/301-04-IdScopeContextRefToUnit.xml
Id: V-5 Description: 301.05 unitRef has IDREF to context element.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLRuntimeException Unit not found for fact
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/301-05-IdScopeUnitRefToContext.xml
Id: V-6 Description: 301.06 Valid example of footnote link href attribute.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/301-06-FootnoteScopeValid.xml
Id: V-7 Description: 301.07 href attribute is referencing out side of xbrl element. This test is out of scope of Conformance testing. But this is kept in the conformance suite since it is still useful test. Decided by Spec WG.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.DTSDiscoveryException Document is not a Taxonomy, Linkbase or XBRL Instance
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/301-07-FootnoteOutOfScope.xml
Id: V-8 Description: 301.08 href attribute is referencing to context element.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLRuntimeException Relationship file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/301-08-FootnoteToContext.xml#element(/1/4/3) the element in the from part of the arc cannot be obtained
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/301-08-FootnoteToContext.xml
Id: V-9 Description: 301.09 href attribute is referencing to unit element.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLRuntimeException Relationship file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/301-09-FootnoteToUnit.xml#element(/1/4/3) the element in the from part of the arc cannot be obtained
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/301-09-FootnoteToUnit.xml
Id: V-10 Description: 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.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLRuntimeException Relationship does not have any element in the from part of the arc file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/301-10-FootnoteFromOutOfScope.xml#element(/1/5/3)
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/301-10-FootnoteFromOutOfScope.xml
Id: V-11 Description: 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.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLRuntimeException Relationship does not have any element in the to part of the arc
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/301-11-FootnoteToOutOfScope.xml
Id: V-12 Description: 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.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.DTSDiscoveryException Illegal attempt to include an instance document in the DTS from another object in the DTS
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/301-12-FootnoteLocOutOfScope.xml
Id: V-13 Description: 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.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/301-13-FootnoteLocInScope.xml
Id: V-14 Description: 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.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException footnoteArc points from an invalid element
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/301-14-FootnoteFromResource.xml
Id: V-15 Description: 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.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException footnoteArc points to an invalid element
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/301-15-FootnoteToLoc.xml
Id: V-16 Description: 301.16 The xml:lang attribute is missing on the footnote resource.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException footnote does not have xml:lang attribute
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/301-16-FootnoteWithoutLang.xml
Section 4.4 The Context Element
Id: V-01 Description: 302.01 Valid segment in a context
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/302-01-SegmentValid.xml
Id: V-02 Description: 302.02 Invalid segment in a context; contains an element defined in xbrli namespace
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException The segment contains elements in the {http://www.xbrl.org/2003/instance} namespace
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/302-02-SegmentNamespaceInvalid.xml
Id: V-03 Description: 302.03 Valid scenario in a context
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/302-03-ScenarioValid.xml
Id: V-04 Description: 302.04 Invalid scenario in a context; contains an element defined in xbrli namespace
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException The scenario contains elements in the {http://www.xbrl.org/2003/instance} namespace
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/302-04-ScenarioNamespaceInvalid.xml
Id: V-05 Description: 302.05 Invalid segment in a context; contains an element in substitution group of xbrli:item
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException The segment contains elements in the {http://www.xbrl.org/2003/instance} item or tuple substitution group
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/302-05-SegmentSubstitutionInvalid.xml
Id: V-06 Description: 302.06 Invalid scenario in a context; contains an element in substitution group of xbrli:item
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException The scenario contains elements in the {http://www.xbrl.org/2003/instance} item or tuple substitution group
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/302-06-ScenarioSubstitutionInvalid.xml
Id: V-07 Description: 302.07 Segment in a context contains an element with empty content
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/302-07-SegmentEmptyContent.xml
Id: V-08 Description: 302.08 Scenario in a context contains an element with empty content
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/302-08-ScenarioEmptyContent.xml
Id: V-09 Description: 302.09 Valid duration context with start date earlier than end date
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/302-09-PeriodDateTimeValid.xml
Id: V-10 Description: 302.10 Invalid duration context with start date later than end date
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Date end is earlier than date start in context
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/302-10-PeriodDateTimeInvalid.xml
Id: V-11 Description: 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.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Calculation mismatch {http://xbrl.example.com}a=1000.0 p(4) is not equal to: (1.0)x({http://xbrl.example.com}b=2000.0 p(4))
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/302-11-DecimalAttributeOnSegmentInconsistent.xbrl
Id: V-12 Description: 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.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Calculation mismatch {http://xbrl.example.com}a=1000.0 p(4) is not equal to: (1.0)x({http://xbrl.example.com}b=2000.0 p(4))
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/302-12-DecimalAttributeOnScenarioInconsistent.xbrl
Section 4.3 The Item Element
Id: V-01 Description: 303.01 instant context and item defined with PeriodType="instant"
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/303-01-PeriodInstantValid.xml
Id: V-02 Description: 303.02 duration context and item defined with PeriodType="duration"
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/303-02-PeriodDurationValid.xml
Id: V-03 Description: 303.03 duration context and item defined with PeriodType="instant"
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Period type on context of fact {http://mycompany.com/xbrl/taxonomy}changeInRetainedEarnings at file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/303-03-PeriodInstantInvalid.xml/xbrli:xbrl[1]/s:changeInRetainedEarnings[1] is (Instant) does not match periof type on item declaration (Duration)
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/303-03-PeriodInstantInvalid.xml
Id: V-04 Description: 303.04 instant context and item defined with PeriodType="duration"
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Period type on context of fact {http://mycompany.com/xbrl/taxonomy}fixedAssets at file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/303-04-PeriodDurationInvalid.xml/xbrli:xbrl[1]/s:fixedAssets[1] is (Duration) does not match periof type on item declaration (Instant)
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/303-04-PeriodDurationInvalid.xml
Id: V-05 Description: ForeverConcept with Instant Period Type is not allowed
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Period type on context of fact {http://www.example.com/new}Forever at file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/303-05-ForeverElementewithInstancePeriodTypeReportedasForever.xbrl/xbrli:xbrl[1]/new:Forever[1] is (Duration) does not match periof type on item declaration (Instant)
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/303-05-ForeverElementewithInstancePeriodTypeReportedasForever.xbrl
Section 4.4 The Context Element
Id: V-01 Description: 304.01 An element with a monetary item type has an ISO currency code for its units (using the standard ISO namespace prefix).
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/304-01-monetaryItemTypeUnitsRestrictions.xml
Id: V-02 Description: 304.02 An element with a monetary item type has an ISO currency code for its units (using a non-standard ISO namespace prefix).
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/304-02-monetaryItemTypeUnitsRestrictions.xml
Id: V-03 Description: 304.03 An element with a type derived by restriction from the monetary item type has an ISO currency code for its units.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/304-03-monetaryItemTypeUnitsRestrictions.xml
Id: V-04 Description: 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).
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/304-04-monetaryItemTypeUnitsRestrictions.xml
Id: V-05 Description: 304.05 An element with a non-monetary item type has an ISO currency code for its units (using the standard ISO namespace prefix).
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/304-05-monetaryItemTypeUnitsRestrictions.xml
Id: V-06 Description: 304.06 An element with a monetary item type does not have an ISO currency code for its units - the namespace is wrong.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Valicating fact {http://www.someCompany.com}assets unit error is: Namespace is not http://www.xbrl.org/2003/iso4217 on monetaryItemType fact
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/304-06-monetaryItemTypeUnitsRestrictions.xml
Id: V-07 Description: 304.07 An element with a monetaryItemType does not have an ISO currency code for its units - the local name is wrong.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Valicating fact {http://www.someCompany.com}assets unit error is: Local part is not iso4217 on monetary unit
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/304-07-monetaryItemTypeUnitsRestrictions.xml
Id: V-08 Description: 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.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Valicating fact {http://www.someCompany.com}assets unit error is: Namespace is not http://www.xbrl.org/2003/iso4217 on monetaryItemType fact
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/304-08-monetaryItemTypeUnitsRestrictions.xml
Id: V-09 Description: 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.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Valicating fact {http://www.someCompany.com}assets unit error is: Local part is not iso4217 on monetary unit
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/304-09-monetaryItemTypeUnitsRestrictions.xml
Id: V-10 Description: 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".
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/304-10-pureItemTypeUnitsRestrictions.xml
Id: V-11 Description: A measure element with a namespace prefix that resolves to the "http://www.xbrl.org/2003/instance" namespace MUST have a local part of either "pure" or "shares". The value 'impure' is not a valid measure in the XBRL instance namespace.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Unit declaration in the {http://www.xbrl.org/2003/instance} namespace MUST be "pure" or "shares".
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/304-11-pureItemTypeUnitsRestrictions.xml
Id: V-12 Description: 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.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/304-12-pureItemTypeUnitsRestrictions.xml
Id: V-13 Description: 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
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/304-13-sharesItemTypeUnitsRestrictions.xml
Id: V-14 Description: 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
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/304-14-sharesItemTypeUnitsRestrictions.xml
Id: V-15 Description: 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.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Local part is not shares on shares unit
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/304-15-pureItemTypeUnitsRestrictions.xml
Id: V-16 Description: 304.16 The units must not have numerator and denominator measures that cancel.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Units are not in the most simplified form
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/304-16-unitsInSimplestForm.xml
Id: V-17 Description: 304.17 The units equality test which two units have same order measures.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/304-17-sameOrderMeasuresValid.xml
Id: V-18 Description: 304.18 The units equality test which two units have same order divisions.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/304-18-sameOrderDivisionMeasuresValid.xml
Id: V-19 Description: 304.19 The units equality test which two units have different order measures.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/304-19-differentOrderMeasuresValid.xml
Id: V-20 Description: 304.20 The units equality test which two units have division elements which their order of child measures are different.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/304-20-differentOrderDivisionMeasuresValid.xml
Id: V-21 Description: 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
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Two facts in an essence-alias relationship that are c-equal and p-equal are not u-equal file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/304-21-measuresInvalid.xml#element(/1/2) and file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/304-21-measuresInvalid.xml#element(/1/3)
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/304-21-measuresInvalid.xml
Id: V-22 Description: 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.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Two facts in an essence-alias relationship that are c-equal and p-equal are not u-equal file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/304-22-divisionMeasuresInvalid.xml#element(/1/2) and file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/304-22-divisionMeasuresInvalid.xml#element(/1/3)
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/304-22-divisionMeasuresInvalid.xml
Id: V-23 Description: 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
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Namespace is not http://www.xbrl.org/2003/instance on sharesItemType fact
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/304-23-Calculation-item-does-not-match-unit.xml
Id: V-24 Description: Valid ISO unit of measurement example
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/304-24-valid-ISO-unit-of-measue.xml
Id: V-25 Description: Measure reported with prefix undefined is considered XBRL invalid
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Unit declaration in the {http://www.xbrl.org/2003/instance} namespace MUST be "pure" or "shares".
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/304-25-measure-reported-with-prefix-undefined-instance.xbrl
Section 4.4 Items
Id: V-01 Description: 305.01 item has only Decimals specified
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/305-01-DecimalOnlySpecified.xml
Id: V-02 Description: 305.02 item has only Precision specified
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/305-02-PrecisionOnlySpecified.xml
Id: V-03 Description: 305.03 item has neither Decimals nor Precision specified
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLRuntimeException The fact does not have neither @decimals or @precision attribute
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/305-03-NoDecimalOrPrecisionSpecified.xml
Id: V-04 Description: 305.04 item has both Decimals and Precision specified
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Numeric item has decimals and precision attributes. Only one is allowed
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/305-04-BothDecimalAndPrecisionSpecified.xml
Id: V-05 Description: 305.05 nil item has Decimals specified
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Nilled facts MUST not have decimals or precision attributes
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/305-05-DecimalSpecifiedOnNilItem.xml
Id: V-06 Description: 305.06 nil item has Precision specified
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Nilled facts MUST not have decimals or precision attributes
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/305-06-PrecisionSpecifiedOnNilItem.xml
Id: V-07 Description: 305.07 a genuine inconsistency due to roll up of child values
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Calculation mismatch {http://www.example.com/decimals}TotalPropertyPlantEquipment=4001.0 p(4) is not equal to: (1.0)x({http://www.example.com/decimals}ComputerEquipment=25.0 p(2)) + (1.0)x({http://www.example.com/decimals}Land=25.0 p(2)) + (1.0)x({http://www.example.com/decimals}Other=25.0 p(2)) + (1.0)x({http://www.example.com/decimals}FurnitureFixtures=25.0 p(2)) + (1.0)x({http://www.example.com/decimals}Buildings=3900.0 p(4))
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/305_07_invalid_instance.xbrl
Section 5.5.6.4.1.5
Id: V-1 Description: 306.01 The instance contains two elements in the same context. The presence of one element forces the presence of the other.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/306-01-RequiredInstanceValid.xml
Id: V-2 Description: 306.02 The instance contains an item and a tuple. The presence of the tuple forces the presence of the item.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/306-02-RequiredInstanceTupleValid.xml
Id: V-3 Description: 306.03 The instance contains an item and a tuple. The presence of the tuple forces the presence of the item.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException requires-element, source element found but target element not found
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/306-03-RequiredInstanceInvalid.xml
Section 5 Taxonomies
Id: V-1 Description: 307.01 A schemaRef element MUST hold the URI of a schema. In this case it does.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/307-01-SchemaRefExample.xml
Id: V-2 Description: 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.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.DTSDiscoveryException schemaRef MUST point to schemas
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/307-02-SchemaRefCounterExample.xml
Id: V-3 Description: 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.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.DTSDiscoveryException schemaRef MUST point to schemas
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/307-03-SchemaRefXMLBase.xml
Relevant sections for calculation binding rules 5_2_5_2 and 4_6_6
Id: V-00 Description: 320.00 - Valid
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/320-00-BindCalculationInferPrecision-instance.xbrl
Id: V-01 Description: 320.01 - Valid
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Calculation mismatch {http://www.example.com/calcinferprecisiontestcase}A=1500.0 p(2) is not equal to: (1.0)x({http://www.example.com/calcinferprecisiontestcase}C=582.3000000000001 p(4)) + (1.0)x({http://www.example.com/calcinferprecisiontestcase}B=985.0 p(3))
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/320-01-BindCalculationInferPrecision-instance.xbrl
Id: V-02 Description: 320.02 - InValid
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Calculation mismatch {http://www.example.com/calcinferprecisiontestcase}A=1530.0 p(3) is not equal to: (1.0)x({http://www.example.com/calcinferprecisiontestcase}B=985.0 p(3)) + (1.0)x({http://www.example.com/calcinferprecisiontestcase}C=582.3000000000001 p(4))
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/320-02-BindCalculationInferPrecision-instance.xbrl
Id: V-03 Description: 320.03 - Valid
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/320-03-nestedtupleBindCalculationInferPrecision-instance.xbrl
Id: V-04 Description: 320.04 - Valid
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/320-04-BindCalculationInferPrecision-instance.xbrl
Id: V-05 Description: 320.05 - Valid
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/320-05-BindCalculationInferPrecision-instance.xbrl
Id: V-07 Description: 320.07 - inValid
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/320-07-BindCalculationInferPrecision-instance.xbrl
Id: V-09 Description: 320.09 - Valid
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/320-09-BindCalculationInferPrecision-instance.xbrl
Id: V-10 Description: 320.10 - Valid - precision stated as 15
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/320-10-BindCalculationInferPrecision-instance.xbrl
Id: V-11 Description: 320.11 - inValid - inconsistent
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Calculation mismatch {http://www.example.com/calcinferprecisiontestcase}A=1.001 p(INF) is not equal to: (1.0)x({http://www.example.com/calcinferprecisiontestcase}C=1.001 p(INF)) + (1.0)x({http://www.example.com/calcinferprecisiontestcase}B=1.0 p(INF))
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/320-11-BindCalculationInferPrecision-instance.xbrl
Id: V-12 Description: 320.12 - Valid - Consistent - precision attribute stated as 15
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/320-12-BindCalculationInferPrecision-instance.xbrl
Id: V-13 Description: 320.13 - Valid - Consistent
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/320-13-BindCalculationInferPrecision-instance.xbrl
Id: V-14 Description: 320.14 - Valid - Consistent
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/320-14-BindCalculationInferPrecision-instance.xbrl
Id: V-15 Description: 320.15 - Valid - COnsistent - Decimal attribute zero
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/320-15-BindCalculationInferPrecision-instance.xbrl
Id: V-16 Description: 320.16 - InValid - Inconsistency contributing items 3200, summation value is 3201
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Calculation mismatch {http://www.example.com/calcinferprecisiontestcase}A=4001.0 p(4) is not equal to: (1.0)x({http://www.example.com/calcinferprecisiontestcase}B=4000.0 p(4)) + (1.0)x({http://www.example.com/calcinferprecisiontestcase}C=0.0 p(0))
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/320-16-BindCalculationInferPrecision-instance.xbrl
Id: V-17 Description: 320.17 - InValid - Inconsistent roll up - weights stated as 1.0
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Calculation mismatch {http://www.example.com/calcinferprecisiontestcase}A=1.0 p(1) is not equal to: (1.0)x({http://www.example.com/calcinferprecisiontestcase}B=1.0 p(1)) + (1.0)x({http://www.example.com/calcinferprecisiontestcase}C=1.0 p(1))
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/320-17-BindCalculationInferPrecision-instance.xbrl
Id: V-18 Description: 320.18 - InValid - 2.04 effective value generates inconsistent roll up - weight is defined as 1.01
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Calculation mismatch {http://www.example.com/calcinferprecisiontestcase}A=2.02 p(3) is not equal to: (1.01)x({http://www.example.com/calcinferprecisiontestcase}B=1.01 p(3)) + (1.01)x({http://www.example.com/calcinferprecisiontestcase}C=1.01 p(3))
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/320-18-BindCalculationInferPrecision-instance.xbrl
Id: V-19 Description: 320.19 - InValid - effective value 1.02 generates inconsistent roll up - weight is defined as 1.01
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Calculation mismatch {http://www.example.com/calcinferprecisiontestcase}A=1.02 p(3) is not equal to: (1.01)x({http://www.example.com/calcinferprecisiontestcase}B=1.0 p(3))
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/320-19-BindCalculationInferPrecision-instance.xbrl
Id: V-20 Description: 320.20 - Valid - Consistent Weight is applied to the value after the decimal or precision is applied to the lexical value reported in the instance Arc weights are defined with the value 1.01 Test ensures the sequence that we apply these rules of inferred precision and weight attribute Summation ns:A weight: 1.01 ns:A lexical value: 1.01 ns:A decimal: 2 Contributing items ns:B weight: 1.01 ns:B lexical value: 1 ns:B decimal: 0 Valid Summation: 1.01 = 1.01
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/320-20-BindCalculationInferPrecision-instance.xbrl
Id: V-21 Description: 320.21 - Duplicate Facts reported and thus calculation will not bind per 5.2.5.2 A calculation represented by a “summation-item” relationship binds for a summation item S if and only if: 1. S has at least one contributing item. 2. S is not a duplicate item (as defined in section 4.10), and 3. None of the contributing items are duplicates. 4. S is not nil-valued (i.e. it does not have an xsi:nil attribute with value true). Test ensures that we do not bind the calculation due to a duplicated fact and do not infer precision.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/320-21-BindCalculationInferPrecision-instance.xbrl
Id: V-22 Description: 320.22 - Duplicate Facts reported and thus calculation will not bind per 5.2.5.2 A calculation represented by a “summation-item” relationship binds for a summation item S if and only if: 1. S has at least one contributing item. 2. S is not a duplicate item (as defined in section 4.10), and 3. None of the contributing items are duplicates. 4. S is not nil-valued (i.e. it does not have an xsi:nil attribute with value true). Test ensures that we Do NOT bind the calculation and do not infer precision. If it did bind then there would be an inconsistency.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/320-22-BindCalculationInferPrecision-instance.xbrl
Id: V-23 Description: 320-24 - Valid - Consistent Inferred precision and Weight Attribute test Summation ns:A weight: 1.01 ns:A lexical value: -3.03 ns:A decimal: 4 Contributing items ns:B weight: 1.01 ns:B lexical value: -1.01 ns:B decimal: 4 ns:C weight: 1.01 ns:C lexical value: 1.99 ns:C decimal: 4 Effective summation of contributing items: -3.0300 + -1.0100 + -1.9900 =-3.0300 Valid Summation: -3.0300 = -3.03
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/320-23-BindCalculationInferPrecision-instance.xbrl
Id: V-24 Description: 320-24 - Valid - Consistent Inferred precision and Weight Attribute test in corrcet sequence ns:A weight: 1.99 ns:A lexical value: 14.99 ns:A decimal: 4 Computed value: 14.9900 ns:B weight: 1 ns:B lexical value: 10 ns:B decimal: 4 Computed value: 10.0000 ns:Parent lexical value: 39.8301 ns:Parent decimal: 4 Computed value: 39.8301 Effective summation of contributing items: 29.8301 + 10.0000 = 39.8301 Valid Summation: 39.8301
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/320-24-BindCalculationInferPrecision-instance.xbrl
Id: V-25 Description: 320-25 - Invalid Test: Verifies that IsNill facts do not bind to calculations per 5.2.5.2 A calculation represented by a “summation-item” relationship binds for a summation item S if and only if: 1. S has at least one contributing item. 2. S is not a duplicate item (as defined in section 4.10), and 3. None of the contributing items are duplicates. 4. S is not nil-valued (i.e. it does not have an xsi:nil attribute with value true).
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Calculation mismatch {http://www.example.com/calcinferprecisiontestcase}A=2.0 p(1) is not equal to: (1.0)x({http://www.example.com/calcinferprecisiontestcase}B=1.0 p(1))
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/320-25-BindCalculationInferPrecision-instance.xbrl
Test the implementation of converting the xlink:href from the represented character string into the right URL for file names and the content of ID attributes
Id: V-00 Description: 321-01 the instance document refers to a taxonomy that contains item definitions using Spanish characters. The item definitions are references from the linkbases. The instance should be considered valid but inconsistent according to the relationships in the calculation linkbase
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Calculation mismatch {http://www.reportingstandard.com/conformance/internatialization}Espaa1=100.0 p(3) is not equal to: (1.0)x({http://www.reportingstandard.com/conformance/internatialization}la_=10.0 p(2)) + (1.0)x({http://www.reportingstandard.com/conformance/internatialization}=40.0 p(2)) + (1.0)x({http://www.reportingstandard.com/conformance/internatialization}la_=20.0 p(2)) + (1.0)x({http://www.reportingstandard.com/conformance/internatialization}la_=1.0 p(1)) + (1.0)x({http://www.reportingstandard.com/conformance/internatialization}la_=30.0 p(2))
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/321-01-internationalization-instance-invalid.xml
Id: V-01 Description: 321-01 the instance document refers to a taxonomy that contains item definitions using Spanish characters. The item definitions are references from the linkbases. The instance should be considered valid and consistent according to the relationships in the calculation linkbase
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/321-01-internationalization-instance-valid.xml
Test equvalent relationships processing
Id: V-01 Description: t:P1 is a summation of t:P2 and t:P3. The contributing items have a calculation inconsistency. Following tests will use relationship equivalence to prohibit (or not be successful at prohibiting) P3 so the sum is clean (or inconsistent if unsuccessful at prohibiting), and thus the test case determines if equivalency matches the spec (by prohibition successfulness in subsequent tests).
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Calculation mismatch {http://xbrl.org/conformance/example}P1=111.0 p(3) is not equal to: (1.0)x({http://xbrl.org/conformance/example}P3=999.0 p(3)) + (1.0)x({http://xbrl.org/conformance/example}P2=111.0 p(3))
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/331-equivalentRelationships-instance-01.xml
Id: V-02 Description: Same as V-01 but t:P3 calculation arc is with an arc prohibited with nothing tricky, thus avoiding the calculation inconsistency. The prohibiting arc has the same arcrole, from, to, order, weight, t: attributes and use=prohibited.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/331-equivalentRelationships-instance-02.xml
Id: V-03 Description: Same as V-02 but prohibiting arc has different weight causing nonequivalency and thus the prohibit is ineffective and calculation is inconsistent.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Calculation mismatch {http://xbrl.org/conformance/example}P1=111.0 p(3) is not equal to: (1.0)x({http://xbrl.org/conformance/example}P3=999.0 p(3)) + (1.0)x({http://xbrl.org/conformance/example}P2=111.0 p(3))
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/331-equivalentRelationships-instance-03.xml
Id: V-04 Description: Same as V-02 but prohibiting arc has has an xmlns not on the original arc, which is exempt. Also the xmlns provides different lexical prefixes for the home-made attributes on the arc.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/331-equivalentRelationships-instance-04.xml
Id: V-05 Description: Same as V-02 but prohibiting arc has has an xlink:title not on the original arc, which is exempt.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/331-equivalentRelationships-instance-05.xml
Id: V-06 Description: Same as V-02 but prohibiting arc has has an default attribute matching the default value (the original arc has the default valued attribute missing). Because the arc allows this attribute with an any wildcard attribute definition, it is not considered an explicit attribute use in the schema declared attributes, and thus it the validator has no way of knowing this default attribute might be put into the PSVI by the validator, and is simply absent on the original arc in the PSVI. Thus the equivalency test fails here.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Calculation mismatch {http://xbrl.org/conformance/example}P1=111.0 p(3) is not equal to: (1.0)x({http://xbrl.org/conformance/example}P2=111.0 p(3)) + (1.0)x({http://xbrl.org/conformance/example}P3=999.0 p(3))
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/331-equivalentRelationships-instance-06.xml
Id: V-07 Description: Same as V-02 but prohibiting arc has has an defaulted attribute whose value does not match the default value (of the original arc, where the default valued attribute was missing, and per V-06 didn't enter the post-schema-validation infoset of attributes of the original arc).
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Calculation mismatch {http://xbrl.org/conformance/example}P1=111.0 p(3) is not equal to: (1.0)x({http://xbrl.org/conformance/example}P3=999.0 p(3)) + (1.0)x({http://xbrl.org/conformance/example}P2=111.0 p(3))
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/331-equivalentRelationships-instance-07.xml
Id: V-08 Description: Same as V-02 but prohibiting arc has an fixed attribute of the correct fixed value (the original arc has the fixed valued attribute missing). Per testing by several vendors, the fixed is determined to behave like default, and thus this attribute is not present on the original arc and causes nonequivalence.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Calculation mismatch {http://xbrl.org/conformance/example}P1=111.0 p(3) is not equal to: (1.0)x({http://xbrl.org/conformance/example}P3=999.0 p(3)) + (1.0)x({http://xbrl.org/conformance/example}P2=111.0 p(3))
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/331-equivalentRelationships-instance-08.xml
Id: V-09 Description: Same as V-02 but prohibiting arc has the stringAttr differently valued.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Calculation mismatch {http://xbrl.org/conformance/example}P1=111.0 p(3) is not equal to: (1.0)x({http://xbrl.org/conformance/example}P3=999.0 p(3)) + (1.0)x({http://xbrl.org/conformance/example}P2=111.0 p(3))
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/331-equivalentRelationships-instance-09.xml
Id: V-10 Description: Same as V-02 but prohibiting arc has the decimalAttr lexically different but same value.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/331-equivalentRelationships-instance-10.xml
Id: V-11 Description: Same as V-02 but prohibiting arc has the doubleAttr lexically different and scaled differently but same value.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/331-equivalentRelationships-instance-11.xml
Id: V-12 Description: Same as V-02 but prohibiting arc has the doubleAttr lexically different and scaled differently to produce a different value.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Calculation mismatch {http://xbrl.org/conformance/example}P1=111.0 p(3) is not equal to: (1.0)x({http://xbrl.org/conformance/example}P3=999.0 p(3)) + (1.0)x({http://xbrl.org/conformance/example}P2=111.0 p(3))
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/331-equivalentRelationships-instance-12.xml
Id: V-13 Description: Same as V-02 but prohibiting arc has the boolAttr lexically different but same value (e.g., 1 == true, 0 == false).
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/331-equivalentRelationships-instance-13.xml
Test s-equal processing
Id: V-01 Description: t:P1 is a summation of t:P2 and t:P3. The contributing items have identical contextRef and thus there is no calculation inconsistency. The context has a scenario contrived to show nesting, attributes, and elements for s-equality testing purposes in subsequent variations.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/330-s-equal-instance-01.xml
Id: V-02 Description: t:P1 is a summation of t:P2 and t:P3. t:P2's context is missing the scenario of the summation item and other contributing item, thus causing calculation inconsistency.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Calculation mismatch {http://xbrl.org/conformance/example}P1=300003.0 p(6) is not equal to: (1.0)x({http://xbrl.org/conformance/example}P3=200002.0 p(6))
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/330-s-equal-instance-02.xml
Id: V-03 Description: t:P1 is a summation of t:P2 and t:P3. t:P2's context has a different t:strVal within its context scenario, thus causing calculation inconsistency.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Calculation mismatch {http://xbrl.org/conformance/example}P1=300003.0 p(6) is not equal to: (1.0)x({http://xbrl.org/conformance/example}P3=200002.0 p(6))
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/330-s-equal-instance-03.xml
Id: V-04 Description: t:P1 is a summation of t:P2 and t:P3. t:P2's context has a ordering of t:strVal and t:decVal within its context scenario, thus causing calculation inconsistency.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Calculation mismatch {http://xbrl.org/conformance/example}P1=300003.0 p(6) is not equal to: (1.0)x({http://xbrl.org/conformance/example}P3=200002.0 p(6))
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/330-s-equal-instance-04.xml
Id: V-05 Description: t:P1 is a summation of t:P2 and t:P3. t:P2's context has a different parenting of t:strVal within its context scenario, thus causing calculation inconsistency.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Calculation mismatch {http://xbrl.org/conformance/example}P1=300003.0 p(6) is not equal to: (1.0)x({http://xbrl.org/conformance/example}P3=200002.0 p(6))
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/330-s-equal-instance-05.xml
Id: V-06 Description: t:P1 is a summation of t:P2 and t:P3. t:P2's context has a different attribute a1 on nested element t:scenarioVal within its context scenario, thus causing calculation inconsistency.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Calculation mismatch {http://xbrl.org/conformance/example}P1=300003.0 p(6) is not equal to: (1.0)x({http://xbrl.org/conformance/example}P3=200002.0 p(6))
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/330-s-equal-instance-06.xml
Id: V-08 Description: t:P1 is a summation of t:P2 and t:P3. t:P2's context has the same scenario, but attributes on element dv2-v02 have been re-ordered, but it is still s-equal to the context of t:P1 and t:P3, so the calculation is valid. (Only the id attribute on the context differs, for the moment, id attributes have been removed from subelements.)
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/330-s-equal-instance-08.xml
Id: V-12 Description: t:P1 is a summation of t:P2 and t:P3. t:P2's context has the same scenario, but doubles and booleans test lexical representations by scaling, though values are the same.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/330-s-equal-instance-12.xml
Id: V-13 Description: t:P1 is a summation of t:P2 and t:P3. t:P2's context has the same scenario, but numbers test lexical signing representations, + optional on positive, and +0 equal to -0.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/330-s-equal-instance-13.xml
Id: V-14 Description: t:P1 is a summation of t:P2 and t:P3. t:P2's context has the same scenario, but doubles and test lexical non-number representations, INF.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/330-s-equal-instance-14.xml
Id: V-15 Description: t:P1 is a summation of t:P2 and t:P3. t:P2's context has the same scenario, but doubles and test lexical non-number representations, INF. Attribute a3 differs, to check that + infinity and - infinity are detected as unequal.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Calculation mismatch {http://xbrl.org/conformance/example}P1=300003.0 p(6) is not equal to: (1.0)x({http://xbrl.org/conformance/example}P3=200002.0 p(6))
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/330-s-equal-instance-15.xml
Id: V-16 Description: t:P1 is a summation of t:P2 and t:P3. t:P2's context has the same scenario, but attributes a3 in both contexts are NaN which is always unequal to all values including itself.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Calculation mismatch {http://xbrl.org/conformance/example}P1=300003.0 p(6) is not equal to: (1.0)x({http://xbrl.org/conformance/example}P3=200002.0 p(6))
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/330-s-equal-instance-16.xml
Id: V-17 Description: t:P1 is a summation of t:P2 and t:P3. t:P2's context has the same scenario, but booleans test lexical representations, 0 or 1 for false or true.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/330-s-equal-instance-17.xml
Section 4.4 Items
Id: V-01 Description: Test variation 391-01 using a base lexical representation of .0000 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-01-InferPrecisionFromDecimals.xml
Id: V-02 Description: Test variation 391-02 using a base lexical representation of 0.0000 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-02-InferPrecisionFromDecimals.xml
Id: V-03 Description: Test variation 391-03 using a base lexical representation of 0. for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-03-InferPrecisionFromDecimals.xml
Id: V-04 Description: Test variation 391-04 using a base lexical representation of 0000. for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-04-InferPrecisionFromDecimals.xml
Id: V-05 Description: Test variation 391-05 using a base lexical representation of 0 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-05-InferPrecisionFromDecimals.xml
Id: V-06 Description: Test variation 391-06 using a base lexical representation of 0000 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-06-InferPrecisionFromDecimals.xml
Id: V-07 Description: Test variation 391-07 using a base lexical representation of .001234 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-07-InferPrecisionFromDecimals.xml
Id: V-08 Description: Test variation 391-08 using a base lexical representation of 0.001234 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-08-InferPrecisionFromDecimals.xml
Id: V-09 Description: Test variation 391-09 using a base lexical representation of 0000.001234 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-09-InferPrecisionFromDecimals.xml
Id: V-10 Description: Test variation 391-10 using a base lexical representation of .00123400 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-10-InferPrecisionFromDecimals.xml
Id: V-11 Description: Test variation 391-11 using a base lexical representation of 0.00123400 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-11-InferPrecisionFromDecimals.xml
Id: V-12 Description: Test variation 391-12 using a base lexical representation of 0000.00123400 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-12-InferPrecisionFromDecimals.xml
Id: V-13 Description: Test variation 391-13 using a base lexical representation of .1234 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-13-InferPrecisionFromDecimals.xml
Id: V-14 Description: Test variation 391-14 using a base lexical representation of 0.1234 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-14-InferPrecisionFromDecimals.xml
Id: V-15 Description: Test variation 391-15 using a base lexical representation of 0000.1234 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-15-InferPrecisionFromDecimals.xml
Id: V-16 Description: Test variation 391-16 using a base lexical representation of .123400 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-16-InferPrecisionFromDecimals.xml
Id: V-17 Description: Test variation 391-17 using a base lexical representation of 0.123400 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-17-InferPrecisionFromDecimals.xml
Id: V-18 Description: Test variation 391-18 using a base lexical representation of 0000.123400 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-18-InferPrecisionFromDecimals.xml
Id: V-19 Description: Test variation 391-19 using a base lexical representation of 1234 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-19-InferPrecisionFromDecimals.xml
Id: V-20 Description: Test variation 391-20 using a base lexical representation of 001234 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-20-InferPrecisionFromDecimals.xml
Id: V-21 Description: Test variation 391-21 using a base lexical representation of 001234. for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-21-InferPrecisionFromDecimals.xml
Id: V-22 Description: Test variation 391-22 using a base lexical representation of 1234. for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-22-InferPrecisionFromDecimals.xml
Id: V-23 Description: Test variation 391-23 using a base lexical representation of 1234.0000 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-23-InferPrecisionFromDecimals.xml
Id: V-24 Description: Test variation 391-24 using a base lexical representation of 001234.0000 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-24-InferPrecisionFromDecimals.xml
Id: V-25 Description: Test variation 391-25 using a base lexical representation of 123400 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-25-InferPrecisionFromDecimals.xml
Id: V-26 Description: Test variation 391-26 using a base lexical representation of 00123400 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-26-InferPrecisionFromDecimals.xml
Id: V-27 Description: Test variation 391-27 using a base lexical representation of 123400. for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-27-InferPrecisionFromDecimals.xml
Id: V-28 Description: Test variation 391-28 using a base lexical representation of 00123400. for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-28-InferPrecisionFromDecimals.xml
Id: V-29 Description: Test variation 391-29 using a base lexical representation of 123400.0000 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-29-InferPrecisionFromDecimals.xml
Id: V-30 Description: Test variation 391-30 using a base lexical representation of 00123400.0000 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-30-InferPrecisionFromDecimals.xml
Id: V-31 Description: Test variation 391-31 using a base lexical representation of 1234.001234 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-31-InferPrecisionFromDecimals.xml
Id: V-32 Description: Test variation 391-32 using a base lexical representation of 001234.001234 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-32-InferPrecisionFromDecimals.xml
Id: V-33 Description: Test variation 391-33 using a base lexical representation of 123400.001234 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-33-InferPrecisionFromDecimals.xml
Id: V-34 Description: Test variation 391-34 using a base lexical representation of 00123400.001234 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-34-InferPrecisionFromDecimals.xml
Id: V-35 Description: Test variation 391-35 using a base lexical representation of 1234.00123400 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-35-InferPrecisionFromDecimals.xml
Id: V-36 Description: Test variation 391-36 using a base lexical representation of 001234.00123400 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-36-InferPrecisionFromDecimals.xml
Id: V-37 Description: Test variation 391-37 using a base lexical representation of 123400.00123400 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-37-InferPrecisionFromDecimals.xml
Id: V-38 Description: Test variation 391-38 using a base lexical representation of 00123400.00123400 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-38-InferPrecisionFromDecimals.xml
Id: V-39 Description: Test variation 391-39 using a base lexical representation of .001204 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-39-InferPrecisionFromDecimals.xml
Id: V-40 Description: Test variation 391-40 using a base lexical representation of 0.001204 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-40-InferPrecisionFromDecimals.xml
Id: V-41 Description: Test variation 391-41 using a base lexical representation of 0000.001204 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-41-InferPrecisionFromDecimals.xml
Id: V-42 Description: Test variation 391-42 using a base lexical representation of .00120400 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-42-InferPrecisionFromDecimals.xml
Id: V-43 Description: Test variation 391-43 using a base lexical representation of 0.00120400 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-43-InferPrecisionFromDecimals.xml
Id: V-44 Description: Test variation 391-44 using a base lexical representation of 0000.00120400 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-44-InferPrecisionFromDecimals.xml
Id: V-45 Description: Test variation 391-45 using a base lexical representation of .1204 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-45-InferPrecisionFromDecimals.xml
Id: V-46 Description: Test variation 391-46 using a base lexical representation of 0.1204 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-46-InferPrecisionFromDecimals.xml
Id: V-47 Description: Test variation 391-47 using a base lexical representation of 0000.1204 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-47-InferPrecisionFromDecimals.xml
Id: V-48 Description: Test variation 391-48 using a base lexical representation of .120400 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-48-InferPrecisionFromDecimals.xml
Id: V-49 Description: Test variation 391-49 using a base lexical representation of 0.120400 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-49-InferPrecisionFromDecimals.xml
Id: V-50 Description: Test variation 391-50 using a base lexical representation of 0000.120400 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-50-InferPrecisionFromDecimals.xml
Id: V-51 Description: Test variation 391-51 using a base lexical representation of 1204 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-51-InferPrecisionFromDecimals.xml
Id: V-52 Description: Test variation 391-52 using a base lexical representation of 001204 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-52-InferPrecisionFromDecimals.xml
Id: V-53 Description: Test variation 391-53 using a base lexical representation of 001204. for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-53-InferPrecisionFromDecimals.xml
Id: V-54 Description: Test variation 391-54 using a base lexical representation of 1204. for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-54-InferPrecisionFromDecimals.xml
Id: V-55 Description: Test variation 391-55 using a base lexical representation of 1204.0000 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-55-InferPrecisionFromDecimals.xml
Id: V-56 Description: Test variation 391-56 using a base lexical representation of 001204.0000 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-56-InferPrecisionFromDecimals.xml
Id: V-57 Description: Test variation 391-57 using a base lexical representation of 120400 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-57-InferPrecisionFromDecimals.xml
Id: V-58 Description: Test variation 391-58 using a base lexical representation of 00120400 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-58-InferPrecisionFromDecimals.xml
Id: V-59 Description: Test variation 391-59 using a base lexical representation of 120400. for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-59-InferPrecisionFromDecimals.xml
Id: V-60 Description: Test variation 391-60 using a base lexical representation of 00120400. for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-60-InferPrecisionFromDecimals.xml
Id: V-61 Description: Test variation 391-61 using a base lexical representation of 120400.0000 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-61-InferPrecisionFromDecimals.xml
Id: V-62 Description: Test variation 391-62 using a base lexical representation of 00120400.0000 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-62-InferPrecisionFromDecimals.xml
Id: V-63 Description: Test variation 391-63 using a base lexical representation of 1204.001204 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-63-InferPrecisionFromDecimals.xml
Id: V-64 Description: Test variation 391-64 using a base lexical representation of 001204.001204 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-64-InferPrecisionFromDecimals.xml
Id: V-65 Description: Test variation 391-65 using a base lexical representation of 120400.001204 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-65-InferPrecisionFromDecimals.xml
Id: V-66 Description: Test variation 391-66 using a base lexical representation of 00120400.001204 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-66-InferPrecisionFromDecimals.xml
Id: V-67 Description: Test variation 391-67 using a base lexical representation of 1204.00120400 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-67-InferPrecisionFromDecimals.xml
Id: V-68 Description: Test variation 391-68 using a base lexical representation of 001204.00120400 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-68-InferPrecisionFromDecimals.xml
Id: V-69 Description: Test variation 391-69 using a base lexical representation of 120400.00120400 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-69-InferPrecisionFromDecimals.xml
Id: V-70 Description: Test variation 391-70 using a base lexical representation of 00120400.00120400 for the data value with various exponent parts
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/391-70-InferPrecisionFromDecimals.xml
Section 5.5.7.15 The DefinitionArc Element
Id: V-1 Description: 392.01 Valid example of essence-alias attribute.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/392-01-EssenceAliasValid.xml
Id: V-2 Description: 392.02 Valid example of essence-alias attribute using duplicate.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/392-02-EssenceAliasDuplicate.xml
Id: V-3 Description: 392.03 Valid example of essence-alias attribute using duplicate. No copy happens.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/392-03-EssenceAliasDuplicateNoEssence.xml
Id: V-4 Description: 392.04 Valid example of essence-alias attribute not to apply reverse direction.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/392-04-EssenceAliasReverse.xml
Id: V-5 Description: 392.05 Valid example of essence-alias attribute.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/392-05-EssenceAliasValidWithValue.xml
Id: V-6 Description: 392.06 Invalid example of essence-alias attribute.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Two facts in an essence-alias relationship that are c-equal and p-equal are not v-equal file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/392-06-EssenceAliasInvalid.xml#element(/1/6) and file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/392-06-EssenceAliasInvalid.xml#element(/1/4)
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/392-06-EssenceAliasInvalid.xml
Id: V-7 Description: 392.07 Valid example of essence-alias attribute. This testset has items set to essence-alias, but Essence item and alias items are located in other tuples, so even if these values are not identical but it is still valid.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/392-07-EssenceAliasDifferentScopeValid.xml
Id: V-8 Description: 392.08 Invalid example of essence-alias attribute. This testset has items set to essence-alias, but Essence item and alias items in same tuple are not identical but other essence item in other tuple is identical. So scoping is wrong, it is invalid.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Two facts in an essence-alias relationship that are c-equal and p-equal are not v-equal file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/392-08-EssenceAliasDifferentScopeInValid.xml#element(/1/4/3) and file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/392-08-EssenceAliasDifferentScopeInValid.xml#element(/1/4/2)
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/392-08-EssenceAliasDifferentScopeInValid.xml
Id: V-9 Description: 392.09 Valid example of essence-alias attribute. This testset has items set to essence-alias, One Essence item in same tuple with alias is identical and other essence items located in other tuples is no identical, By scoping, it is valid.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/392-09-EssenceAliasDifferentScopeValidWithValue.xml
Id: V-10 Description: 392.10 Invalid example of essence-alias attribute. This testset has numeric items set to essence-alias, but Essence item and alias item have different units. so it is invalid.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Two facts in an essence-alias relationship that are c-equal and p-equal are not u-equal file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/392-10-EssenceAliasDifferentUnit.xml#element(/1/6) and file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/392-10-EssenceAliasDifferentUnit.xml#element(/1/5)
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/392-10-EssenceAliasDifferentUnit.xml
Id: V-11 Description: 392.11 Valid example of essence-alias attribute. This testset has items set to essence-alias, but Essence item and alias item are different values and units. so it is valid.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/392-11-EssenceAliasDifferentContext.xml
Id: V-12 Description: 392.12 Invalid example of essence-alias attribute. This testset make an essence-alias relation between two different item type.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Two concepts in an essence-alias relationship MUST have the same item type file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/392-12-EssenceAliasInvalid.xsd#element(/1/4) and file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/392-12-EssenceAliasInvalid.xsd#element(/1/3)
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/392-12-EssenceAliasInvalid.xsd
Id: V-13 Description: 392.13 Invalid example of essence-alias attribute. This testset make an essence-alias relation between two items which are different period type.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Two concepts in an essence-alias relationship MUST have the same period type file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/392-13-EssenceAlias.xsd#element(/1/4) and file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/392-13-EssenceAlias.xsd#element(/1/3)
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/392-13-EssenceAliasDifferentPeriodType.xml
Id: V-14 Description: 392.14 Valid example of essence-alias attribute regarding nonNumericContext.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/392-14-EssenceAliasNonNumericValid.xml
Id: V-15 Description: 392.15 invalid example of essence-alias attribute regarding nonNumericContext.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Two facts in an essence-alias relationship that are c-equal and p-equal are not v-equal file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/392-15-EssenceAliasNonNumericInValid.xml#element(/1/3) and file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/392-15-EssenceAliasNonNumericInValid.xml#element(/1/4)
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/392-15-EssenceAliasNonNumericInValid.xml
Id: V-16 Description: 392.16 Valid example of essence-alias attribute regarding nonNumericContext.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/392-16-EssenceAliasNonNumericTupleValid.xml
Id: V-17 Description: 392.17 invalid example of essence-alias attribute regarding nonNumericContext.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Two facts in an essence-alias relationship that are c-equal and p-equal are not v-equal file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/392-17-EssenceAliasNonNumericTupleInValid.xml#element(/1/3/1) and file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/392-17-EssenceAliasNonNumericTupleInValid.xml#element(/1/3/2)
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/392-17-EssenceAliasNonNumericTupleInValid.xml
Section 5.2.5.2 The CalculationArc Element
Id: V-1 Description: 395.01 Valid example of summation-item attribute.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/395-01-InferCalculatedValueConsistencyValid.xml
Id: V-2 Description: 395.02 This is a test for detecting inconsistency between value in an Instance and value calculated by calculation link..This is set to invalid but the document validity itself is still valid.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Calculation mismatch {http://example.com/xbrl/taxonomy/SummationItem}Asset=1500.0 p(2) is not equal to: (1.0)x({http://example.com/xbrl/taxonomy/SummationItem}CurrentAsset=582.3000000000001 p(4)) + (1.0)x({http://example.com/xbrl/taxonomy/SummationItem}FixedAsset=985.0 p(3))
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/395-02-InferCalculatedValueConsistencyDifferentValue.xml
5.2.5.2 - Fully conformant XBRL processors MUST detect and signal inconsistencies, as defined above, between an XBRL instance and the summation-item arcs of calculation linkbases in its supporting DTS
Id: V-00 Description: A simple consistent instance; A = B + C
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/397-00-ConsistentInstance-valid.xbrl
Id: V-01 Description: A simple inconsistent instance; A != B + C
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Calculation mismatch {http://xbrl.example.com/397/ABC}A=4.0 p(INF) is not equal to: (1.0)x({http://xbrl.example.com/397/ABC}B=1.0 p(INF)) + (1.0)x({http://xbrl.example.com/397/ABC}C=2.0 p(INF))
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/397-01-InconsistentInstance-invalid.xbrl
Id: V-02 Description: A != B + C, but A is in a different context from B and C, so B and C are not contributing items for A. No checks are performed. The instance is consistent.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/397-02-NonCEqualContributing-valid.xbrl
Id: V-03 Description: A != B + C, but A has a different unit from B and C, so B and C are not contributing items for A. No checks are performed. The instance is consistent.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/397-03-NonUEqualContributing-valid.xbrl
Id: V-04 Description: B and C are c-equal and u-equal to A. B and C are contributing items for A, but A != B + C so the instance is inconsistent.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Calculation mismatch {http://xbrl.example.com/397/ABC}A=4.0 p(INF) is not equal to: (1.0)x({http://xbrl.example.com/397/ABC}B=1.0 p(INF)) + (1.0)x({http://xbrl.example.com/397/ABC}C=2.0 p(INF))
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/397-04-SEqualContextsAndUnitsContributing-invalid.xbrl
Id: V-05 Description: B and C are both nil-valued, so neither contributes to A. No checks are performed. The instance is consistent.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/397-05-BothNilContributing-valid.xbrl
Id: V-06 Description: B is nil-valued but C is not. A = C, so the instance is consistent.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/397-06-OneNilContributing-valid.xbrl
Id: V-07 Description: B is nil-valued but C is not. A != C, so the instance is not consistent.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Calculation mismatch {http://xbrl.example.com/397/ABC}A=4.0 p(INF) is not equal to: (1.0)x({http://xbrl.example.com/397/ABC}C=2.0 p(INF))
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/397-07-OneNilContributing-invalid.xbrl
Id: V-08 Description: A simple consistent instance; A = B; C not present
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/397-08-OneContributing-valid.xbrl
Id: V-09 Description: A simple inconsistent instance; A != B; C not present
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Calculation mismatch {http://xbrl.example.com/397/ABC}A=3.0 p(INF) is not equal to: (1.0)x({http://xbrl.example.com/397/ABC}B=1.0 p(INF))
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/397-09-OneContributing-invalid.xbrl
Id: V-10 Description: A (the summation item) is nil, so no checks are performed.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/397-10-NilSummationItem-valid.xbrl
Id: V-11 Description: Two occurrences of A, the first of which is nil. The first is ignored. The second would result in an inconsistency were it not for the fact that it is a duplicate of the first (because values are not considered).
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/397-11-DuplicateSummationItems-valid.xbrl
Id: V-12 Description: Things don't add up, but this goes undetected because one of the contributing items is duplicated.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/397-12-DuplicateContributingItems-valid.xbrl
Id: V-13 Description: All items within one tuple, and things don't add up.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Calculation mismatch {http://xbrl.example.com/397/ABC}A=0.0 p(INF) is not equal to: (1.0)x({http://xbrl.example.com/397/ABC}B=1.0 p(INF)) + (1.0)x({http://xbrl.example.com/397/ABC}C=1.0 p(INF))
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/397-13-InconsistentWithinTuple-invalid.xbrl
Id: V-14 Description: Summation item is in a separate tuple from occurrences of the contributing concepts. Because of tuple scoping rules, the summation item has no contributing items. Nothing is checked. The instance is consistent.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/397-14-SeparateTuplesConsistent-valid.xbrl
Id: V-15 Description: Contributing items (within tuples) are in-scope for the summation item (at top level). Inconsistency should be detected.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Calculation mismatch {http://xbrl.example.com/397/ABC}A=0.0 p(INF) is not equal to: (1.0)x({http://xbrl.example.com/397/ABC}B=1.0 p(INF)) + (1.0)x({http://xbrl.example.com/397/ABC}B=1.0 p(INF))
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/397-15-ContributingWithinTuples-invalid.xbrl
Id: V-16 Description: Summation item at top level has sibling contributing items and nephew contributing items. Inconsistency should be detected.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Calculation mismatch {http://xbrl.example.com/397/ABC}A=2.0 p(INF) is not equal to: (1.0)x({http://xbrl.example.com/397/ABC}C=1.0 p(INF)) + (1.0)x({http://xbrl.example.com/397/ABC}C=1.0 p(INF)) + (1.0)x({http://xbrl.example.com/397/ABC}B=1.0 p(INF)) + (1.0)x({http://xbrl.example.com/397/ABC}B=1.0 p(INF))
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/397-16-MultiLevelBinding-invalid.xbrl
Id: V-17 Description: Binding across many levels (consistent).
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/397-17-ConsistentCountdown-valid.xbrl
Id: V-18 Description: Binding across many levels (inconsistent).
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Calculation mismatch {http://xbrl.example.com/397/ABC}A=0.0 p(INF) is not equal to: (1.0)x({http://xbrl.example.com/397/ABC}B=1.0 p(INF))
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/397-18-InconsistentCountdown-invalid.xbrl
Id: V-19 Description: Would be inconsistent, were it not for the duplicate contributing items deep in the hierarchy.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/397-19-DuplicateCountdown-valid.xbrl
Id: V-20 Description: If you infer a value for 'A', then X is consistent, but since this is not allowed, the instance is inconsistent.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Calculation mismatch {http://xbrl.example.com/397/XYZ}X=3.0 p(INF) is not equal to: (1.0)x({http://xbrl.example.com/397/XYZ}Y=1.0 p(INF))
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/397-20-NoSummationItemInference-invalid.xbrl
Id: V-21 Description: If you infer a value for 'A', then X is consistent, but since this is not allowed, the instance is inconsistent.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Calculation mismatch {http://xbrl.example.com/397/XYZ}X=3.0 p(INF) is not equal to: (1.0)x({http://xbrl.example.com/397/XYZ}Y=1.0 p(INF))
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/397-21-NoEssenceAliasInference-invalid.xbrl
Id: V-22 Description: The 'B' and 'C' children both inside and outside the tuple are, according to the spec, bound in the summation of 'A' at the top level. 10 + 20 + 1 + 2 is not equal to 3.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Calculation mismatch {http://xbrl.example.com/397/ABC}A=3.0 p(INF) is not equal to: (1.0)x({http://xbrl.example.com/397/ABC}B=2.0 p(INF)) + (1.0)x({http://xbrl.example.com/397/ABC}B=20.0 p(INF)) + (1.0)x({http://xbrl.example.com/397/ABC}C=1.0 p(INF)) + (1.0)x({http://xbrl.example.com/397/ABC}C=10.0 p(INF))
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/397-22-TopAndTuple-inconsistent.xbrl
Id: V-23 Description: The 'B' children both inside and outside the tuple are, according to the spec, bound in the summation of 'A' at the top level. 20 + 2 equals 22.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/397-23-TopAndTuple-consistent.xbrl
Section 4.3 The Item Element
Id: v401-01 Description: 401-01 instance with valid QNamed, non existent element within fact value, element existence is not checked http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/#QName
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/401-01-instance_invalidQNamedElementwithinFactValue_withSchemaRef.xbrl
Id: v401-03 Description: 401-03 valid instance QNamed fact value - with namespace and schemaref
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/instance/401-03-instance_QnameFactValue_withSchemaRef.xbrl
Section 5 Taxonomies
Id: V-01 Description: 201.01 The LinkbaseRef elements MUST hold the URI of Linkbases. In this case the URI's do not resolve to XML documents.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLRuntimeException Excapsulated Exception
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/201-01-LinkbaseRefCounterExample.xsd
Id: V-02 Description: 201.02 The LinkbaseRef elements hold the URI of Linkbases. In this case the URI's actually resolve to documents that contain the right kinds of XBRL linkbases.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/201-02-LinkbaseRef.xsd
Id: V-03 Description: 201.03 XML Base must be used to process the URI of a LinkbaseRef. In this case the schema use the xml base attribute to get the linkbase to be picked up from the base directory instead of the current directory.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/201-03-LinkbaseRefXMLBase.xsd
Id: V-04 Description: 201.04 The LinkbaseRef XLink role attribute value must match the linkbase found at its target. In this case it does not. The role indicates a label linkbase and the actual linkbase is a reference linkbase.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLRuntimeException LinkbaseRef role and linkbase content does not match
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/201-04-LinkbaseRefLabelCounterExample.xsd
Id: V-05 Description: 201.05 The LinkbaseRef element role must match the linkbase found at its target. In this case it does not. The role indicates a reference linkbase and the actual linkbase is a label linkbase.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLRuntimeException LinkbaseRef role and linkbase content does not match
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/201-05-LinkbaseRefReferenceCounterExample.xsd
Id: V-06 Description: 201.06 The LinkbaseRef element role must match the linkbase found at its target. In this case a calculation linkbase is indicated and a definition linkbase is provided.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLRuntimeException LinkbaseRef role and linkbase content does not match
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/201-06-LinkbaseRefDefinitionCounterExample.xsd
Id: V-07 Description: 201.07 The LinkbaseRef element role must match the linkbase found at its target. In this case a definition linkbase is indicated and a presentation linkbase is provided.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLRuntimeException LinkbaseRef role and linkbase content does not match
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/201-07-LinkbaseRefPresentationCounterExample.xsd
Id: V-08 Description: 201.08 The LinkbaseRef element role must match the linkbase found at its target. In this case a presentation linkbase is indicated and a calculation linkbase is provided.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLRuntimeException LinkbaseRef role and linkbase content does not match
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/201-08-LinkbaseRefCalculationCounterExample.xsd
Id: V-09 Description: 201.09 There can be any number of LinkbaseRef elements having the same role but the role must always match the target.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/201-09-LinkbaseRefMultipleExample.xsd
Id: V-10 Description: 201.10 The LinkbaseRef element in the second appinfo section holds the URI of a reference linkbase, but uses a role that should only point to label Linkbases.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLRuntimeException LinkbaseRef role and linkbase content does not match
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/201-10-InvalidLinbaseRefInSecondAppinfo.xsd
Section 5.5.7.8 Arc equivalence 5.5.7.8
Id: V-01 Description: 202.01 A URI reference appearing in an href attribute must resolve to an XML Schema element element or an xlink resource-type element
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/202-01-HrefResolution-label.xml
Id: V-02 Description: 202.02 A URI reference appearing in an href attribute must resolve to an XML Schema element element or an xlink resource-type element
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLRuntimeException Duplicate element id in taxonomy this
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/202-02-HrefResolutionCounterExample-label.xml
Id: V-03 Description: 202.03 A URI reference appearing in an href attribute must be computed using the method described in XML Base [XMLBase]
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/base/202-03-HrefResolutionXMLBase-label.xml
Id: V-04 Description: 202.04 Arc-type elements connecting the same "from" and "to" labels MUST appear in different extended-type link elements even if the arcrole attributes are equal. This is an XLink constraint.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Two concepts in an essence-alias relationship MUST have the same period type file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/202-04-XLinkLabelCounterExample.xsd#element(/1/3) and file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/202-04-XLinkLabelCounterExample.xsd#element(/1/4)
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/202-04-XLinkLabelCounterExample-definition.xml
Id: V-05 Description: 202.05 element() scheme pointers are legal (Spec 3.5.4)
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/202-05-ElementLocatorExample-label.xml
Id: V-06 Description: 202.06 Locators with different xlink labels pointing to the same taxonomy element.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/202-06-DuplicateLocatorExample-label.xml
Id: V-07 Description: 202.07 shorthand pointers are legal (Spec 3.5.4)
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/202-07-ShorthandPointerExample-label.xml
Id: V-08 Description: 202.08 xpointer() Scheme pointers are illegal (Spec 3.5.4)
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLRuntimeException xpointer() Scheme pointers are illegal (Spec 3.5.4)
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/202-08-XPointerLocatorExample-label.xml
Id: V-09 Description: 202.09 element() Scheme pointers are legal (Spec 3.5.4)
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/202-09-ElementSchemeXPointerLocatorExample-label.xml
Id: V-10 Description: 202.10 A sequence of element() Schemes in an X pointer is legal (Spec 3.5.4). The first of the element schemes does not resolve but the second does.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/202-10-ElementSchemeXPointerLocatorExample-label.xml
Id: V-11 Description: 202.11 An xmlns() scheme in an X pointer is illegal in XBRL 2.1 (Spec 3.5.4) even if resolution of that scheme is not attempted because an early scheme resolves.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLRuntimeException xpointer contains an xmlns() definition which may be a valid XPointer but is not valid for XBRL
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/202-11-ElementSchemeXPointerLocatorExample-label.xml
Id: V-12 Description: 202.12 An element scheme in an X pointer in a label linkbase locator that does not resolve to a concept is illegal. See 5.2.2.1 in the XBRL 2.1 specification.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException From element in concept-label relationship file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/202-12-ElementSchemeXPointerLocatorExample.xsd#element(/1) is not a xbrl concept definition
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/202-12-ElementSchemeXPointerLocatorExample-label.xml
Id: V-13 Description: 202.13 An element scheme in an X pointer in a linkbaseRef. See 3.5.1.2 in the XBRL 2.1 specification.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/202-13-ElementSchemeXPointerLocatorExample-label.xml
Section 5.7.7 The arcrole Attribute
Id: V-4 Description: 204.04 parent-child arcs must not form directed cycles. This schema and linkbase creates a set of concepts (named conceptA to conceptL) and creates a presentation network of parent-child arc roles that contains no cycles.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/ArcCyclesPCNC.xml
Id: V-5 Description: 204.05 parent-child arcs must not form directed cycles. This schema and linkbase creates a set of concepts (named conceptA to conceptL) and creates two presentation networks of parent-child arc roles that contains no cycles. If the networks were interpreted as a single network than a cycle would occur.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/ArcCyclesPCNCWR.xml
Id: V-6 Description: 204.06 parent-child arcs must not form directed cycles. This schema and linkbase creates a set of concepts (named conceptA to conceptL) and creates a presentation network of parent-child arc roles that contain a directed cycle between conceptB, conceptE and conceptJ.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Directed cycles detected
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/ArcCyclesPCDC.xml
Id: V-7 Description: 204.07 parent-child arcs must not form directed cycles. This schema extends the ArcCyclesPCNC.xsd taxonomy and defines conceptZ. The linkbase adds conceptZ as a child of conceptG. It also prohibits the arc between conceptB and conceptD and creates a new arc between conceptA and conceptD. The ArcCyclesPCNCExtension.xsd taxonomy schema imports ArcCyclesPCNC.xsd
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/ArcCyclesPCNCExtension.xml
Id: V-8 Description: 204.08 parent-child arcs must not form directed cycles. This schema extends the ArcCyclesPCNC.xsd taxonomy and defines conceptZ. The linkbase adds conceptZ as a child of conceptG and a child of conceptL. This forms an undirected cycle bewteen conceptA, conceptB, conceptE, conceptI, conceptA, conceptG and conceptC. The ArcCyclesPCWCExtension.xsd taxonomy schema imports ArcCyclesPCNC.xsd
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Directed cycles found
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/ArcCyclesPCWCExtension.xml
Id: V-9 Description: 204.09 summation-item arcs may form any cycles. This schema and linkbase creates a set of concepts (named conceptA to conceptL) and creates a calculation network of summation-item arc roles that contains no cycles.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/ArcCyclesSINC.xml
Id: V-10 Description: 204.10 summation-item arcs may form any cycles. This schema and linkbase creates a set of concepts (named conceptA to conceptL) and creates two calculation networks of summation-item arc roles that contains no cycles. If the networks were interpreted as a single network than a cycle would occur.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/ArcCyclesSINCWR.xml
Id: V-11 Description: 204.11 summation-item arcs may form any cycles. This schema and linkbase creates a set of concepts (named conceptA to conceptL) and creates a calculation network of summation-item arc roles that contain an undirected cycle between conceptA, conceptB and conceptD.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/ArcCyclesSIUC.xml
Id: V-12 Description: 204.12 summation-item arcs may form any cycles. This schema and linkbase creates a set of concepts (named conceptA to conceptL) and creates a calculation network of summation-item arc roles that contain a directed cycle between conceptB, conceptE and conceptJ.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/ArcCyclesSIDC.xml
Id: V-13 Description: 204.13 summation-item arcs may form any cycles. This schema extends the ArcCyclesSINC.xsd taxonomy and defines conceptZ. The linkbase adds conceptZ as a child of conceptG. It also prohibits the arc between conceptB and conceptD and creates a new arc between conceptA and conceptD. The ArcCyclesSINCExtension.xsd taxonomy schema imports ArcCyclesSINC.xsd
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/ArcCyclesSINCExtension.xml
Id: V-14 Description: 204.14 summation-item arcs may form any cycles. This schema extends the ArcCyclesSINC.xsd taxonomy and defines conceptZ. The linkbase adds conceptZ as a child of conceptG and a child of conceptL. This forms an undirected cycle bewteen conceptA, conceptB, conceptE, conceptI, conceptA, conceptG and conceptC. The ArcCyclesSIWCExtension.xsd taxonomy schema imports ArcCyclesSINC.xsd
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/ArcCyclesSIWCExtension.xml
Id: V-15 Description: 204.15 general-special arcs must not form directed cycles. This schema and linkbase creates a set of concepts (named conceptA to conceptL) and creates a definition network of general-special arc roles that contains no cycles.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/ArcCyclesGSNC.xml
Id: V-16 Description: 204.16 general-special arcs must not form directed cycles. This schema and linkbase creates a set of concepts (named conceptA to conceptL) and creates two definition networks of general-special arc roles that contains no cycles. If the networks were interpreted as a single network than a cycle would occur.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/ArcCyclesGSNCWR.xml
Id: V-17 Description: 204.17 general-special arcs must not form directed cycles. This schema and linkbase creates a set of concepts (named conceptA to conceptL) and creates a definition network of general-special arc roles that contain an undirected cycle between conceptA, conceptB and conceptD.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/ArcCyclesGSUC.xml
Id: V-18 Description: 204.18 general-special arcs must not form directed cycles. This schema and linkbase creates a set of concepts (named conceptA to conceptL) and creates a definition network of general-special arc roles that contain a directed cycle between conceptB, conceptE and conceptJ.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Directed cycles detected
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/ArcCyclesGSDC.xml
Id: V-19 Description: 204.19 general-special arcs must not form directed cycles. This schema extends the ArcCyclesGSNC.xsd taxonomy and defines conceptZ. The linkbase adds conceptZ as a child of conceptG. It also prohibits the arc between conceptB and conceptD and creates a new arc between conceptA and conceptD. The ArcCyclesGSNCExtension.xsd taxonomy schema imports ArcCyclesGSNC.xsd
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/ArcCyclesGSNCExtension.xml
Id: V-20 Description: 204.20 general-special arcs must not form directed cycles. This schema extends the ArcCyclesGSNC.xsd taxonomy and defines conceptZ. The linkbase adds conceptZ as a child of conceptG and a child of conceptL. This forms an undirected cycle bewteen conceptA, conceptB, conceptE, conceptI, conceptA, conceptG and conceptC. The ArcCyclesGSWCExtension.xsd taxonomy schema imports ArcCyclesGSNC.xsd
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/ArcCyclesGSWUCExtension.xml
Id: V-21 Description: 204.21 general-special arcs must not form directed cycles. This schema extends the ArcCyclesGSNC.xsd taxonomy and defines conceptZ. The linkbase adds conceptZ as a child of conceptG and makes conceptC a child of concept A. This forms a directed cycle bewteen conceptC, conceptG and conceptZ. The ArcCyclesGSWCExtension.xsd taxonomy schema imports ArcCyclesGSNC.xsd
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Directed cycles detected
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/ArcCyclesGSWDCExtension.xml
Id: V-22 Description: 204.22 parent-child arcs must not form directed cycles. This schema defines concepts conceptA through conceptL. The presentation linkbase referenced in the linkbaseRef element creates a network of arcs that forms an undirected cycle between concepts A, B and D.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/ArcCyclesPCUC.xml
Id: V-23 Description: 204.23 essence-alias arcs must not form directed cycles. This schema and linkbase creates a set of concepts (named conceptA to conceptL) and creates a definition network of essence-alias arc roles that contain an undirected cycle between conceptA, conceptB and conceptD.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/ArcCyclesEAUC.xml
Id: V-24 Description: 204.24 essence-alias arcs must not form directed cycles. This schema and linkbase creates a set of concepts (named conceptA to conceptL) and creates a definition network of essence-alias arc roles that contain a directed cycle between conceptB, conceptE and conceptJ.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Directed cycles detected
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/ArcCyclesEADC.xml
Section 5.5.8
Id: V-1 Description: 205.01 A new role for use on a linkbaseRef is defined in RoleSSchema.xsd. A new extended link element and arc type element are also defined in this schema. The RoleS.xsd taxonomy schema uses the new role on the linkbaseRef element pointing to RoleS_linkbase.xml
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/RoleS.xml
Id: V-2 Description: 205.02 A new role for used on the extended-type presentationLink element is defined in RoleE.xsd. RoleE_presentation.xml uses the new role.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/RoleE.xml
Id: V-3 Description: 205.03 A new role for used on a label resource element is defined in RoleL.xsd. RoleL_label.xml uses the new role.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/RoleL.xml
Id: V-4 Description: 205.04 A new role for used on a reference resource element is defined in RoleR.xsd. RoleR_reference.xml uses the new role.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/RoleR.xml
Id: V-5 Description: 205.05 A new role for use on a presentationLink elment is defined in RoleSBUSchema.xsd. A new extended link element and arc type element are also defined in this schema. The RoleSBU.xsd taxonomy schema uses the new role on the linkbaseRef element pointing to RoleSBU_linkbase.xml. The role is defined to be used on a presentationLink element, but this does not matter since this is not checked for custom links.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/RoleSBU.xml
Id: V-6 Description: 205.06 A new role for use on a linkbaseRef elment is defined in RoleSBRSchema.xsd. A new extended link element and arc type element are also defined in this schema. The RoleSBR.xsd taxonomy schema attempts to use the new role on the linkbaseRef element pointing to RoleSBR_linkbase.xml. On the linkbaseRef element, the fragment identifier of the role does not match the name defined on the roleType element. This does not matter because this is not checked for linkbaseRefs.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/RoleSBR.xml
Id: V-7 Description: 205.07 A new role for use on a linkbaseRef elment is defined in RoleSBRSchema.xsd. The same role is also defined in RoleSDR2Schema.xsd. RoleSDRschema.xsd imports RoleSDR2Schema.xsd. Since both schemas are part of the DTS (via the import) the role is defined twice,however, this doesn't matter because they are equivalent, and, more importantly, this is not checked for linkbaseRefs anyway. The RoleSDR.xsd uses the new role on a linkbaseRef pointing to RoleSDR_linkbase.xml.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/RoleSDR.xml
Id: V-8 Description: 205.08 A new role for use on a linkbaseRef elment is defined in RoleSBRISchema.xsd. The same role is also defined in RoleSDRI2Schema.xsd with a different usedOn list. RoleSDRIschema.xsd imports RoleSDRI2Schema.xsd. Since both schemas are part of the DTS (via the import) the role is defined twice. Because role definitions for the same role are defined separately, the DTS is invalid. The RoleSDRI.xsd uses the new role on a linkbaseRef pointing to RoleSDRI_linkbase.xml.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLRuntimeException Role Type http://mycompany.com/xbrl/newRoleLinkbaseDR/newRole defined more than once in the DTS and definitions are not s-equal
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/RoleSDRI.xml
Id: V-9 Description: 205.09 A new role intended for used on the extended-type presentationLink element is defined in RoleE.xsd, however the usedOn attribute indicates the definitionLink. RoleE_presentation.xml uses the new role. The element that the role is used on does not match the usedOn attribute on the roleType.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLRuntimeException Role uri http://mycompany.com/xbrl/roleEBR/newExtendedRoleType is used on element {http://www.xbrl.org/2003/linkbase}presentationLink but there is no a usedOn declaration for that element QName. Valid elements are: {http://www.xbrl.org/2003/linkbase}definitionLink
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/RoleEBR.xml
Id: V-10 Description: 205.10 A role is defined in RoleE2.xsd, once for use on a presentationLink element and once for use on a defintionLink element. RoleE2.xsd points to RoleE2_presentation.xml (a presentation linkbase) and RoleE2_definition.xml (a definition linkbase) via linkbaseRef elements. The presentation linkbases uses the role on the presentationLink element. The definition linkbase uses the role on the definitionLink element. These uses are valid.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/RoleE2.xml
Id: V-11 Description: 205.11 Two roles with the same URI are defined in RoleLDR.xsd with one for use on a label and one for reference resources. The two definitions are not equivalent so this should be an error.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLRuntimeException Role type http://mycompany.com/xbrl/roleLDR/newLabelRole is defined more than once in the same taxonomy schema
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/RoleLDR.xml
Section 5.5.9
Id: V-1 Description: 206.01 ArcRoleG.xsd declares a new arc role called row-cell for use on prsentationArc elements.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/ArcRoleG.xml
Id: V-2 Description: 206.02 ArcRoleBU.xsd declares a new arc role called row-cell for use on prsentationArc elements. In the ArcRoleBU_calculation.xml linkbase, the new arc role is used on a calculation arc.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLRuntimeException Arcrole uri http://mycompany.com/xbrl/arcroleBU/row-cell is used on element {http://www.xbrl.org/2003/linkbase}calculationArc but there is no a usedOn declaration for that element QName. Valid elements are: {http://www.xbrl.org/2003/linkbase}presentationArc
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/ArcRoleBU.xml
Id: V-3 Description: 206.03 ArcRoleBR.xsd declares a new arc role called row-cell for use on prsentationArc elements. In the ArcroleBR_presentation.xml linkbase, a presentationArc element uses cell-row as the arc role which is not declared. The arcroleRef contains the URI for the cell-row arc role with an href pointing to the arcroleType for row-cell.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLRuntimeException ArcroleType definition http://mycompany.com/xbrl/arcroleBR/cell-row not found in the referenced schema file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/ArcRoleBR.xsd
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/ArcRoleBR.xml
Id: V-4 Description: 206.04 ArcRoleBR2.xsd declares a new arc role called row-cell for use on prsentationArc elements. In the ArcroleBR_presentation.xml linkbase, a presentationArc element uses cell-row as the arc role which is not declared. There is no arcroleRef to resolve the cell-row arc role.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLRuntimeException The arcroleURI http://mycompany.com/xbrl/arcroleBR2/cell-row is used on {http://www.xbrl.org/2003/linkbase}presentationLink but declaration of the arcroleType cannot be found via arcroleRef. XPath is /link:linkbase[1]/link:presentationLink[1]
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/ArcRoleBR2.xml
Id: V-5 Description: 206.05 ArcRoleDR.xsd declares a new arc role twice within the same taxonomy schema document called row-cell for use on prsentationArc elements.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLRuntimeException Arcrole type http://mycompany.com/xbrl/arcroleDR/row-cell is defined more than once in the same taxonomy schema
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/ArcRoleDR.xml
Id: V-6 Description: 206.06 ArcRoleDR2.xsd and ArcRoleDR2a declare a new arc role called row-cell for use on prsentationArc elements. The ArcRoleDR2_presentation.xml linkbase has locator to both of these schemas. So that in the DTS, the arc role is declared twice. Since the declarations are equivalent, the files are valid.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/ArcRoleDR2.xml
Id: V-7 Description: 206.07 ArcRoleDR3.xsd and ArcRoleDR3a declare a new arc role called row-cell for use on prsentationArc elements. The ArcRoleDR3_presentation.xml linkbase has locator to both of these schemas. So that in the DTS, the arc role is declared twice. Since the declarations are not equivalent, the files are not valid.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLRuntimeException Arcrole Type http://mycompany.com/xbrl/arcroleDR3/row-cell defined more than once in the DTS and definitions are not s-equal
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/ArcRoleDR3.xml
Id: V-8 Description: A set of custom arc roles are defined to demonstrate allowed end points differing from the usual, per Spec call July 13, 2006 (pursuant to "Create Conformance Suite entry for summation-item end points?" http://xbrl.org/scripts/wa.exe?A2=ind0607&L=int-spec&P=4022). Tests (a) that calculation arcs can be used between a string and a numeric end point (here to define a countOf-item relationship), (b) that calculation arcs can be used between an end point inside tuples and a statistic end point at root level (here an averageOf-quantity relationship), and (c) that definition arcs can be used between a tuple end point and an item end point at root level (here an isStatisticOf-tuple relationship). (Submitted by Herm Fischer, UBmatrix, herman.fischer@ubmatrix.com)
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/ArcRoleCustomEndPoints.xsd
Section 5.5.9
Id: V-1 Description: 207.01 DecArcCyclesNN.xsd declares an arcrole that does not allow any cycles. It references the DecArcCyclesNN_definition.xml linkbase.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/DecArcCyclesNN.xml
Id: V-2 Description: 207.02 DecArcCyclesNU.xsd declares an arcrole that does not allow any cycles. It references the DecArcCyclesNU_definition.xml linkbase which contains an undirected cycle.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Undirected cycles detected
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/DecArcCyclesNU.xml
Id: V-3 Description: 207.03 DecArcCyclesND.xsd declares an arcrole that does not allow any cycles. It references the DecArcCyclesND_definition.xml linkbase which contains a directed cycle.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Undirected cycles detected
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/DecArcCyclesND.xml
Id: V-4 Description: 207.04 DecArcCyclesNUE.xsd declares an arcrole that does not allow any cycles. It references the DecArcCyclesNUE_definition.xml linkbase which in itself contains no cycles. However, via the DTS DecArcCyclesNUE2.xsd and DecArcCyclesNUE2_definition.xml are also discovered. The combined linkbases form a network containing an undirected cycle.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Undirected cycles detected
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/DecArcCyclesNUE.xml
Id: V-5 Description: 207.05 DecArcCyclesNE.xsd declares an arcrole that does not allow any cycles. It references the DecArcCyclesNE_definition.xml linkbase which in itself contains an undirected cycle. However, via the DTS DecArcCyclesNE2.xsd and DecArcCyclesNE2_definition.xml are also discovered. DecArcCyclesNE2_definition.xml prohibits the arcs that form the undirected cycle.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/DecArcCyclesNE.xml
Id: V-6 Description: 207.06 DecArcCyclesUN.xsd declares an arcrole that allows undirected cycles. It references the DecArcCyclesUN_definition.xml linkbase which contains no cycles.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/DecArcCyclesUN.xml
Id: V-7 Description: 207.07 DecArcCyclesUU.xsd declares an arcrole that allows undirected cycles. It references the DecArcCyclesUU_definition.xml linkbase which contains an undirected cycle.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/DecArcCyclesUU.xml
Id: V-8 Description: 207.08 DecArcCyclesUD.xsd declares an arcrole that allows undirected cycles. It references the DecArcCyclesUD_definition.xml linkbase which contains a directed cycle.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Directed cycles detected
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/DecArcCyclesUD.xml
Id: V-9 Description: 207.09 DecArcCyclesUUE.xsd declares an arcrole that allows undirected cycles. It references the DecArcCyclesUUE_definition.xml linkbase which in itself contains no cycles. However, via the DTS DecArcCyclesUUE2.xsd and DecArcCyclesUUE2_definition.xml are also discovered. The combined linkbases form a network of arcs that have an undirected cycle.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/DecArcCyclesUUE.xml
Id: V-10 Description: 207.10 DecArcCyclesUDE.xsd declares an arcrole that allows undirected cycles. It references the DecArcCyclesUDE_definition.xml linkbase which in itself contains no cycles. However, via the DTS DecArcCyclesUDE2.xsd and DecArcCyclesUDE2_definition.xml are also discovered. The combined linkbases form a network of arcs that have a directed cycle.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Directed cycles detected
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/DecArcCyclesUDE.xml
Id: V-11 Description: 207.11 DecArcCyclesDN.xsd declares an arcrole that allows any cycles. It references the DecArcCyclesDN_definition.xml linkbase.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/DecArcCyclesDN.xml
Id: V-12 Description: 207.12 DecArcCyclesDU.xsd declares an arcrole that allows any cycles. It references the DecArcCyclesDU_definition.xml linkbase which contains an undirected cycle.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/DecArcCyclesDU.xml
Id: V-13 Description: 207.13 DecArcCyclesDD.xsd declares an arcrole that allows any cycles. It references the DecArcCyclesDD_definition.xml linkbase which contains a directed cycle.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/DecArcCyclesDD.xml
Id: V-14 Description: 207.14 DecArcCyclesNU2.xsd declares an arcrole that does not allow cycles. It references the DecArcCyclesNU2_definition.xml linkbase which contains a structure where A and Z are the parents of both B and C but there are no other cycles, directed or undirected. This forms an undirected cycle.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Undirected cycles detected
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/DecArcCyclesNU2.xml
Section 5 Taxonomies
Id: V-01 Description: 209.01 Checking that trivial undirected cycles (created by a pair of arcs with the same source and destination) are detected. As per http://xbrlbugs.decisionsoft.com/show_bug.cgi?id=7 such cycles are no longer illegal.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/209-01-DifferentWeights.xsd
Id: V-02 Description: 209.02 (Spec 2_1 - Section 5-2-4-2-1) Checking that two presentation arcs are NOT identified as being equivalent when they are equivalent in all other respects AND their preferredLabel attributes are not equal. There are two Presentation arcs that have exactly same structure and value except that they have preferred Label attributes different (standard, terse) The presentation arcs are not identical. the test is valid
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/209-02-DifferentPreferredLabels.xsd
Id: V-03 Description: 209.03 Verify that arcs in separate extended-links do not violate any XLink constraint even though their 'from' and 'to' labels identify identical hrefs. The definitionLink and general-special arc are used in this test because the general-special arc allows the undirected cycle formed by the pair of arcs in this test.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/209-03-SameDefinitionArcs.xsd
Id: V-04 Description: 209.04 This test is extended from "209.03". This arcs are same as 209.03 except arcrole value. This arcs have different arcrole value,then the result of 209-04-Out.xml has two arc elements.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/209-04-DifferentArcroles.xsd
Section 5.1.1.2 - An optional balance attribute MAY be added to the definition of an element if its type is monetaryItemType or derived from monetaryItemType. The balance attribute MUST NOT be used on items that do not have type equal to the monetaryItemType or to a type that is derived from monetaryItemType. If the idea of debit/credit balance is appropriate to the element, it MAY be indicated using this attribute.
Id: V-01 Description: 208.01 When the item and summation have no balance attribute they are consistent
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/208-01-ItemNoneSummationNone-instance.xml
Id: V-02 Description: 208.02 If an item is a credit, and the item it sums to is a credit, its weight MUST be +1 (greater than 0)
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/208-02-ItemCreditSumCreditWeight+1-instance.xml
Id: V-03 Description: 208.03 If an item is a credit and the item it sums to is a credit, its weight MUST NOT be -1 (less than 0)
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Invalid weight value CREDIT concept and CREDIT concept requires POSITIVE weight
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/208-03-ItemCreditSumCreditWeight-1-instance.xml
Id: V-04 Description: 208.04 If an item is a debit, and the item it sums to is a credit, its weight MUST NOT be +1 (greater than 0)
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Invalid weight value DEBIT concept and CREDIT concept requires NEGATIVE weight
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/208-04-ItemDebitSumCreditWeight+1-instance.xml
Id: V-05 Description: 208.05 If an item is a debit, and the item it sums to is a credit, its weight MUST be -1 (less than 0)
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/208-05-ItemDebitSumCreditWeight-1-instance.xml
Id: V-06 Description: 208.06 If an item is a credit, and the item it sums to is a credit, its weight MUST NOT be +1 (greate than 0)
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Invalid weight value CREDIT concept and DEBIT concept requires NEGATIVE weight
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/208-06-ItemCreditSumDebitWeight+1-instance.xml
Id: V-07 Description: 208.07 If an item is a credit, and the item it sums to is a debit, its weight MUST be -1 (less than 0)
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/208-07-ItemCreditSumDebitWeight-1-instance.xml
Id: V-08 Description: 208.08 If an item is a debit, and the item it sums to is a debit, its weight MUST be +1 (greater than 0)
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/208-08-ItemDebitSumDebitWeight+1-instance.xml
Id: V-09 Description: 208.09 If an item is a debit, and the item it sums to is a debit, its weight MUST NOT be -1 (less than 0)
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Invalid weight value DEBIT concept and DEBIT concept requires POSITIVE weight
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/208-09-ItemDebitSumDebitWeight-1-instance.xml
Id: V-10 Description: 208.10 The value of a weight attribute MUST NOT be 0 (zero)
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Calculation mismatch {http://mycompany.com/xbrl/taxonomy/ext}ItemCredit=5000.0 p(4) is not equal to: (0.0)x({http://mycompany.com/xbrl/taxonomy/ext}SumCredit=5000.0 p(4))
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/208-10-WeightNotZero-instance.xml
Checks that relationship equivalence is correctly evaluated.
Id: V-1 Description: 210.01 A prohibiting arc of a higher priority overrides a relationship, thus removing the calculation relationship. The instance would be invalid if the relationship had not been prohibited.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/210-01-RelationshipEquivalence-instance.xml
Id: V-2 Description: 210.02 A prohibiting arc of a higher priority has a different order to another arc and thus fails to prohibit the said arc. The instance is thus invalid since it doesn't add up.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Calculation mismatch {http://mycompany.com/xbrl/taxonomy}fixedAssets=5000.0 p(3) is not equal to: (1.0)x({http://mycompany.com/xbrl/taxonomy}changeInRetainedEarnings=1000.0 p(3))
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/210-02-DifferentOrder-instance.xml
Id: V-3 Description: 210.03 A prohibiting arc of a higher priority has no order attribute, and another arc has order one. The instance is thus valid since the arc is prohibited as the prohibiting arc's order takes the default value.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/210-03-MissingOrder-instance.xml
Id: V-4 Description: 210.04 A prohibiting arc of a higher priority overrides a relationship, thus removing the calculation relationship. The instance would be invalid if the relationship had not been prohibited. In this variation, linkbase calculation-2 has the "optional" arc appear before the "prohibited".
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/210-04-RelationshipEquivalence-instance.xml
Id: V-5 Description: 210.05 A prohibiting arc of a higher priority overrides a relationship, thus removing the calculation relationship. The instance would be invalid if the relationship had not been prohibited. In this variation, linkbase calculation-2 has the "prohibited" arc appear before the "optional".
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/210-05-RelationshipEquivalence-instance.xml
5.1.3.4 - Within a roleType element there MUST NOT be s-equal usedOn elements.
Id: V-00 Description: A valid roleType. usedOn elements refer to different elements in the same namespace.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/211-00-NonSEqualUsedOn-valid.xsd
Id: V-01 Description: Simple invalid roleType. usedOn elements refer to the same element twice. QName content of the two usedOn elements is lexically identical AND equal in the QName value space (same prefix, same namespace, same local name).
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLRuntimeException Same Used On {http://xbrl.example.com/foo}foo defined multiple times
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/211-01-SEqualUsedOnSamePrefixSameNamespace-invalid.xsd
Id: V-02 Description: roleType invalid according to erratum 041. usedOn elements refer to the same element twice. QName content of the two usedOn elements is lexically different, but equal in the QName value space (prefixes are different, but both prefixes are bound to the same namespace).
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLRuntimeException Same Used On {http://xbrl.example.com/foo}foo defined multiple times
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/211-02-SEqualUsedOnDifferentPrefixesSameNamespace-invalid.xsd
Id: V-03 Description: roleType that is valid according to erratum 041. usedOn elements refer to elements that have the same local name but different namespaces. QName content of the two usedOn elements is lexically identical but distinct in the QName value space (prefixes are the same, but each prefix is bound to a different namespace).
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/211-03-NonSEqualUsedOnSamePrefixDifferentNamespaces-valid.xsd
3.5.2.3 and 3.5.3.5 linkbase documentation elements.
Id: V-01 Description: A valid documentation element as a child of a linkbase element. There are no attributes on the documentation element.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/212-01-schema.xsd
Id: V-03 Description: A documentation element as a child of a linkbase element but where the documentation element has a valid xml:lang attribute.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/212-03-schema.xsd
Id: V-04 Description: A documentation element as a child of a linkbase element but where the documentation element has a valid attribute with an explicitly declared namespace.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/212-04-schema.xsd
Id: V-05 Description: A documentation element as a child of a linkbase element but where the documentation element has no content.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/212-05-schema.xsd
Id: V-06 Description: A valid documentation element as a child of an extended link. There are no attributes on the documentation element.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/212-06-schema.xsd
Id: V-08 Description: A documentation element as a child of an extended link but where the documentation element has a valid xml:lang attribute.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/212-08-schema.xsd
Id: V-09 Description: A documentation element as a child of an extended link but where the documentation element has a valid attribute with an explicitly declared namespace.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/212-09-schema.xsd
Id: V-10 Description: A documentation element as a child of an extended link element but where the documentation element has no content.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/212-10-schema.xsd
Section 5.2.5.2 - Summation-item arcs MUST represent relationships only between concepts that are in the item substitution group and whose type is numeric.
Id: V-01 Description: 213.01 When the Summation and Item are numeric it is consistent.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/213-01-SummationNumeric_ItemNumeric.xsd
Id: V-02 Description: 213.02 The
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException items in summation-item relationships MUST be numeric: The element {http://example.com/xbrl}str1 in source of a summation-item relationship is not numeric.
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/213-02-SummationNonNumeric_ItemNumeric.xsd
Id: V-03 Description: 213.03
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException items in summation-item relationships MUST be numeric: The element{http://example.com/xbrl}str1 in target of a summation-item relationship is not numeric.
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/213-03-SummationNumeric_ItemNonNumeric.xsd
Non-standard Embedded linkbases
Id: V-01 Description: A cycle between arcs in a non-core extended link, and non-core arcs.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/220-01-NonStandardArcrole.xsd
Id: V-02 Description: Cycle in custom arc with arcrole URI that isnt defined in an arcroleRef or arcroleType. Cycles should be OK.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/220-02-NonStandardArcWithUndefinedArcrole.xsd
Id: V-03 Description: ArcroleType and linkbase in same file, linkbase doesnt reference arcroleType which prohibits cycles. We have a cycle.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/220-03-CycleInUnreferencedArcrole.xsd
Id: V-04 Description: Arcrole defined in same file as linkbase where it is used, but with no arcroleRef. Should require arcroleRef.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLRuntimeException The arcroleURI http://mycompany.com/xbrl/arcroleDR/row-cell is used on {http://www.xbrl.org/2003/linkbase}labelLink but declaration of the arcroleType cannot be found via arcroleRef. XPath is /xs:schema[1]/xs:annotation[1]/xs:appinfo[1]/link:linkbase[1]/link:labelLink[1]
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/220-04-StandardArcWithUnreferencedArcrole.xsd
Id: V-05 Description: Custom arcrole type with usedOn of presentationArc. Referenced and used on a non-standard arc. Should get error according to 5.1.4.5.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/220-05-UsedOnSignificanceOnCustomArc.xsd
Id: V-06 Description: Individually linkbases are valid, but putting them together is undefined. Should we report the cycles?
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/220-06-Taxonomy.xsd
Id: V-07 Description: Test of just linkbase1. It has the cycle, but no arcrole ref.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/220-06-Linkbase1.xml
Id: V-08 Description: Test of just linkbase1. It has the cycle, but no arcrole ref. Yet we add the arcrole type definition to the DTS.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/220-08-Taxonomy.xsd
3.5.3.7.2 Locators may point to XML documents
Id: V-01 Description: 230.01 Section 3.5.3.7.2 allows locators to point to an XML document. If a link:loc points to a document, that document MUST be discovered and loaded into the DTS. In this case there is an instance document that contains facts from two taxonomies the first taxonomy is referenced in a schemaRef element. The second taxonomy is discovered through a link:loc in a custom linkbase of the first taxonomy.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/230-01-LocatorToADocumentWithoutFragment.xbrl
Id: V-02 Description: 230.02 only link:loc elements can be used to fire DTS discovery, in this case the custom linkbase contains an element in the link:loc substitution group but the file pointed to by that loc should not be included in the DTS. The file is an invalid taxonomy that will fire an error if included in the DTS.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/230-02-ElementInLinkLocSubGroup.xsd
XBRL 2.1 spec says duplicate arcs are not allowed on extended links. Two syntactically equal arcs in different extended links are not equal.
Id: V-01 Description: XBRL 2.1 spec says duplicate arcs are not allowed on extended links. Two syntactically equal arcs in different extended links are not equal. Th test case must raise a calculation mistmatch. If duplicate arcs are found then the 231-02 variation will also raise the same error and this means there is something wrong in the duplicate arc recognition. If a calculation mistmatch is not found then this could be that the processor is ignoring or not resolving appropiately the overwriten relationships.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Calculation mismatch {http://www.xbrl.org/testcases/arcEquality/01}A=2000.0 p(4) is not equal to: (1.0)x({http://www.xbrl.org/testcases/arcEquality/01}B=1000.0 p(4))
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/231-01-ArcsAreNotEqualButTheyLookAsEqual.xbrl
Id: V-02 Description: XBRL 2.1 spec says duplicate arcs are not allowed on extended links. Two syntactically equal arcs in different extended links are not equal. this is a valid instance document according to the taxonomy with syntactically equal arcs that are not duplicate arcs. The example must not raise duplicate arcs errors and no calculation mistmatch or warnings of this type.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/231-02-ArcsAreNotEqualButTheyLookAsEqual.xbrl
Section 5.5.7.10 Overriding arcs
Id: V-1 Description: 291.01 The two disjoint label linkbases of a schema together combine into a single PTVL.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/ArcOverrideDisjointLinkbases.xsd
Id: V-2 Description: 291.02One label linkbase overrides another label linkbase.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/291-02-ArcOverrideLabelLinkbases.xsd
Id: V-3 Description: 291.03 One label linkbase prohibits a link in another linkbase and link again. But use attribute must be prohibited so the second override must not be permitted.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException To element in concept-label relationship file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/291-03-ArcOverrideLabelLinkbases-1-label.xml#element(/1/1/2) is not a local resource and relationship is not use="prohibited"
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/291-03-ArcOverrideLabelLinkbases.xsd
Id: V-4 Description: 291.04 The two disjoint definition linkbases of a schema together combine into a single PTVL.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/291-04-ArcOverrideDisjointLinkbases.xsd
Id: V-5 Description: 291.05 One Linkbase prohibits one link in another linkbase.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/291-05-ArcOverrideDisjointLinkbases.xsd
Id: V-6 Description: 291.06 One Linkbase prohibits and another Linkbase links againt the link in other linkbase.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/291-06-ArcOverrideDisjointLinkbases.xsd
Id: V-7 Description: 291.07 One label linkbase overrides another label linkbase. But overriding labelArc element's use attribute value is "optional". That's why this must be invalid.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException To element in concept-label relationship file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/291-07-ArcOverrideLabelLinkbases-1-label.xml#element(/1/1/2) is not a local resource and relationship is not use="prohibited"
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/291-07-ArcOverrideLabelLinkbases.xsd
Id: V-08 Description: 291.08 One label linkbase overrides another label linkbase. But overriding labelArc element have from and to attribute which both points to item in a schema.That's why this must be invalid.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException To element in concept-label relationship is not a local or external resource
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/291-08-ArcOverrideLabelLinkbases.xsd
Id: V-09 Description: 291.09 One label linkbase overrides another label linkbase. But overriding labelLink has different role. There seems to have no special usecase for this. But it is no problem from the Specificaiton point of view. That's why this must be valid and ignored or warned.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/291-09-ArcOverrideLabelLinkbases.xsd
Id: V-10 Description: 291.10 The two disjoint reference linkbases of a schema together combine into a single PTVL.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/291-10-ArcOverrideDisjointLinkbases.xsd
Id: V-11 Description: 291.11 One reference linkbase overrides another reference linkbase.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/291-11-ArcOverrideReferenceLinkbases.xsd
Id: V-12 Description: 291.12 One reference linkbase prohibits a link in another linkbase and link again. But use attribute must be prohibited so the second override must not be permitted.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLRuntimeException Encapsulated Exception
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/291-12-ArcOverrideReferenceLinkbases.xsd
Id: V-13 Description: 291.13 One reference linkbase overrides another reference linkbase. But overriding referenceArc element's use attribute value is "optional". That's why this must be invalid.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException To element in concept-reference relationship file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/291-13-ArcOverrideReferenceLinkbases-1-reference.xml#element(/1/1/2) is not a local resource and relationship is not use="prohibited"
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/291-13-ArcOverrideReferenceLinkbases.xsd
Id: V-14 Description: 291.14 One reference linkbase overrides another reference linkbase. But overriding referenceArc element have from and to attribute which both points to item in a schema.That's why this must be invalid.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException To element in concept-reference relationship is not a local or external resource
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/291-14-ArcOverrideReferenceLinkbases.xsd
Id: V-15 Description: 291.15 One reference linkbase overrides another reference linkbase. But overriding referenceLink has different role. There seems to have no special usecase for this. But it is no problem from the Specificaiton point of view. That's why this must be valid and ignored or warned.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/291-15-ArcOverrideReferenceLinkbases.xsd
Embedded linkbases
Id: V-00 Description: Embedded linkbase
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/292-00-Embeddedlinkbaseinthexsd.xsd
Id: V-01 Description: Multiple embedded linkbases
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/292-01-Embeddedlinkbaseinthexsd.xsd
Id: V-02 Description: Multiple embedded linkbases, and a linkbaseref
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/292-02-EmbeddedLinkbaseAndLinkbaseRef.xsd
Id: V-03 Description: Multiple embedded linkbases, the second uses invalid arcroles
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLRuntimeException Arcrole uri http://www.xbrl.org/2003/arcrole/parent-child is used on element {http://www.xbrl.org/2003/linkbase}calculationArc but there is no a usedOn declaration for that element QName.
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/292-03-EmbeddedLinkbaseSecondInvalid.xsd
5.1.3.4 The usedOn element in roleType elements / 5.1.4.5 The usedOn element on arcroleType elements
Id: V-1 Description: 293.01 A usedOn element in a roleType element identifies which standard extended link elements and resource elements may use the role type being defined. It is valid.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/293-01-RoleTypeUsedOnValid.xsd
Id: V-2 Description: 293.02 A usedOn element in a roleType element identifies which non-standard extended link elements and resource elements may use the role type being defined. It is valid.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/293-02-RoleTypeUsedOnValid.xsd
Id: V-3 Description: 293.03 A usedOn element in a roleType element identifies which standard arc elements may use the role type being defined. It is meaningless, but it is still valid.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/293-03-RoleTypeUsedOnValid.xsd
Id: V-4 Description: 293.04 A usedOn element in a roleType element identifies which standard elements other than link elements may use the role type being defined. It is meaningless, but it is still valid.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/293-04-RoleTypeUsedOnValid.xsd
Id: V-5 Description: 293.05 A usedOn element in an arcroleType element identifies which standard arc elements may use the arcrole type being defined. It is valid.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/293-05-ArcroleTypeUsedOnValid.xsd
Id: V-6 Description: 293.06 A usedOn element in an arcroleType element identifies which non-standard arc elements may use the arcrole type being defined. It is valid.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/293-06-ArcroleTypeUsedOnValid.xsd
Id: V-7 Description: 293.07 A usedOn element in an arcroleType element identifies which standard extended link elements may use the arcrole type being defined. It is meaningless, but it is still valid.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/293-07-ArcroleTypeUsedOnValid.xsd
Id: V-8 Description: 293.08 A usedOn element in an arcroleType element identifies which standard elements other than link elements may use the arcrole type being defined. It is meaningless, but it is still valid.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/293-08-ArcroleTypeUsedOnValid.xsd
Section 5.2.4.2.1 The preferredLabel attribute (optional)
Id: V-1 Description: The presentationArc's 'to' concept has label resource with a role value which is equal to the value of the preferredLabel attribute.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/prefLabel-single-language-valid.xsd
Id: V-2 Description: The presentationArc's 'to' concept does not have label resource with a role value which is equal to the value of the preferredLabel attribute.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException There is no a label defined for the concept {http://www.example.com/conformance/test}CurrentAsset with preferredLabel=http://www.xbrl.org/2003/role/verboseLabel relationship from {http://www.example.com/conformance/test}Asset
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/prefLabel-single-language-invalid.xsd
Id: V-3 Description: The presentationArc's 'from' concept has label resource with a role value which is equal to the value of the preferredLabel attribute. But the presentationArc's 'to' concept does not have label resource with a role value which is equal to the value of the preferredLabel attribute.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException There is no a label defined for the concept {http://www.example.com/conformance/test}CurrentAsset with preferredLabel=http://www.xbrl.org/2003/role/verboseLabel relationship from {http://www.example.com/conformance/test}Asset
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/prefLabel-single-language-invalid2.xsd
Id: V-4 Description: The presentationArc's 'to' concept does not have 'en' label resource with a role value which is equal to the value of the preferredLabel attribute, but has 'ja' label resource with a role value which is equal to the value of the preferredLabel attribute.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/prefLabel-incomplete-multi-languageset.xsd
Id: V-5 Description: The presentationArc's 'to' concept does not have label resource with a role value which is equal to the value of the preferredLabel attribute, but the presentationArc's 'from' concept has 'ja' label resource with a role value which is equal to the value of the preferredLabel attribute.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException There is no a label defined for the concept {http://www.example.com/conformance/test}CurrentAsset with preferredLabel=http://www.xbrl.org/2003/role/verboseLabel relationship from {http://www.example.com/conformance/test}Asset
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/linkbase/prefLabel-incomplete-multi-languageset-invalid.xsd
Section 5.4 Taxonomy Elements
Id: V-1 Description: 102.01 The periodType attribute is required all item types.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/102-01-SpecExample.xml
Id: V-2 Description: 102.02 The periodType attribute is required for both numeric and non-numeric item types.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Item {http://www.example.com/test}t1 does not have a period type
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/102-02-MissingPeriodType.xsd
Id: V-3 Description: 102.03 The periodTyope attribute is not allowed on tuples.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Tuples must not have xbrli:periodType attribute
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/102-03-NoPeriodTypeTuple.xsd
Id: V-4 Description: 102.04 Valid example for usage of substitutionGroup for item type elements. Added test erratam #021
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/102-04-substitutionItem.xsd
Id: V-5 Description: 102.05 Valid example for usage of substitutionGroup for item type elements. Added test erratam #021
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/102-05-substitutionItem.xsd
Id: V-6 Description: 102.06 Valid example for usage of substitutionGroup for item type elements. Added test erratam #021
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/102-06-substitutionItemValid.xbrl
Id: V-8 Description: 102.08 Valid example for usage of substitutionGroup for tuple type elements. Added test erratam #021
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/102-08-substitutionTuple.xsd
Id: V-9 Description: 102.09 Valid example for usage of substitutionGroup for tuple type elements. Added test erratam #021
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/102-09-substitutionTuple.xsd
Id: V-10 Description: 102.10 Valid example for usage of substitutionGroup for tuple type elements. Added test erratam #021
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/102-10-substitutionTupleValid.xbrl
Id: V-11 Description: 102.11 Valid example for usage of substitutionGroup. The element substituted is declared in an external schema. Note this test case has been submited by Ignacio Hernandez-Ros ignacio@hernandez-ros.com on May 2007
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/102-11-DerivedElementFromAnElementInAnotherSchema.xsd
Section 5.3 Other Data Types
Id: V-1 Description: 103.01 An item type in a taxonomy can never have complex content unless it is derived by restriction from fractionItemType.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException The item type of {http://mycompany.com/xbrl/taxonomy}companyLocation is not derived from any of the xbrl defined types
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/103-01-ComplexContentCounterExample.xsd
Section 4.5 The tuple element
Id: V-1 Description: 104.01 Tuples are derived from tupleType.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/104-01-SpecTupleExample.xml
Id: V-2 Description: 104.02 Tuples are derived from tupleType and subelements all appear as references.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/104-02-TupleExampleAnyOrder.xml
Id: V-3 Description: 104.03 Subelements of a tuple may use minOccurs and maxOccurs.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/104-03-TupleExampleCardinality.xml
Id: V-4 Description: 104.04 Tuples may be defined as a complex type.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/104-04-TupleExampleComplextype.xml
Id: V-5 Description: 104.05 Tuples may be defined as a complex type containing other tuples.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/104-05-TupleExampleNestedComplextype.xml
Id: V-6 Description: 104.06 Anonymous type definitions are fine, per erratum 054.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/104-06-TupleCounterExampleNestedComplexType.xsd
Id: V-7 Description: 104.07 Tuples may be defined using choice, sequence and all elements.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/104-07-TupleChoiceExample.xml
Id: V-8 Description: 104.08 Tuples can use the any element, section 4.9, point 7, erratum 2.8.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/104-08-TupleAnyCounterExample.xsd
Id: V-9 Description: 104.09 Tuples can have unqualified local attributes other than id.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/104-09-TupleAttributeCounterExample.xml
Id: V-10 Description: 104.10 Tuples should not have attributes in XBRL spec defined namespaces. The tuple declaration allows "anyAttribute", and the instance takes advantage of this by putting xbrli:periodType on the tuple fact.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Tuple contains an attribute in the xbrli namespace
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/104-10-TupleXBRLAttributeCounterExample.xml
Id: V-10b Description: 104.10b Tuples should not have attributes in XBRL spec defined namespaces. Like v-10, but without the instance. Tests whether processors reject "anyAttribute" in tuple declarations as illegal at the schema level.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/104-10-TupleXBRLAttributeCounterExample.xsd
Id: V-10c Description: 104.10c Tuples should not have attributes in XBRL spec defined namespaces. This schema contains a tuple *requires* the use of xbrli:periodType.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Tuple definition contains attributes in the XBRL Instance namespace
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/104-10c-TupleXBRLAttributeCounterExample.xsd
Id: V-10d1 Description: 104.10d1 Tuples should not have attributes in XBRL spec defined namespaces. This variation tests the http://www.xbrl.org/2003/instance namespace, by including a tuple that allows the use of xbrli:periodType.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Tuple definition contains attributes in the XBRL Instance namespace
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/104-10d1-TupleXBRLAttributeCounterExample.xsd
Id: V-10d2 Description: 104.10d2 Tuples should not have attributes in XBRL spec defined namespaces. This variation tests the http://www.w3.org/1999/xlink namespace, by including a tuple that allows the use of xlink:href.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Tuple definition contains attributes in the XLink namespace
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/104-10d2-TupleXBRLAttributeCounterExample.xsd
Id: V-10d3 Description: 104.10d3 Tuples should not have attributes in XBRL spec defined namespaces. This variation tests the http://www.xbrl.org/2003/linkbase namespace, by including a tuple that allows the use of any attributes from the namespace (there aren't currently any global attributes in this namespace). Are such wildcards illegal?
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/104-10d3-TupleXBRLAttributeCounterExample.xsd
Id: V-10d4 Description: 104.10d4 Tuples should not have attributes in XBRL spec defined namespaces. This variation tests the http://www.xbrl.org/2003/XLink namespace, by including a tuple that allows the use of any attributes from the namespace (there aren't currently any global attributes in this namespace). Are such wildcards illegal?
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/104-10d4-TupleXBRLAttributeCounterExample.xsd
Id: V-11 Description: 104.11 Tuples can use the group element.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/104-11-TupleGroupCounterExample.xsd
Id: V-12 Description: 104.12 Tuples must not use the mixed attribute.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Tuples MUST NOT have mixed content
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/104-12-TupleMixedCounterExample.xsd
Id: V-13 Description: 104.13 A tuple's content model can be derived by restriction from xsd:anyType.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/104-13-TupleRestrictionExample.xml
Id: V-14 Description: 104.14 a tuple's content model may be derived by either restriction or extension from a data type derived by xsd:anyType. This is the case of derivation of restriction.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/104-14-TupleNestedRestrictionExample.xml
Id: V-16 Description: Errata #23 - 104.16 Tuple elements can be declared abstract.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/104-16-TupleAbstractCounterExample.xsd
Id: V-17 Description: 104.17 In the declaration of any tuple in a taxonomy schema, declarations of child elements of that tuple MUST be references to global element declarations that are in a substitution group that has either item or tuple as its head.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Tuple definition contains elements that are not global
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/104-17-TupleAnonymousCounterExample.xsd
Id: V-18 Description: 104.18 Redefine element MUST NOT be used. This is bug#30 and erratam #30
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Usage of xs:redefine is not legal in XBRL taxonomies
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/104-18-redefine.xsd
Id: V-19 Description: 104.19 Abstract tuple definition can be possible. bug# 31.Erratum#28
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/104-19-abstractTuple.xsd
Section 5.5.9 (Optional) An optional balance attribute MAY be added to the definition of an element if its type is monetaryItemType or derived from monetaryItemType. The balance attribute MUST NOT be used on items that do not have type equal to the monetaryItemType or to a type that is derived from monetaryItemType. If the idea of debit/credit balance is appropriate to the element, it MAY be indicated using this attribute.
Id: V-01 Description: 105.01 Any element with a balance attibute MUST have a type attribute value of monetaryItemType
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException The item type of {http://mycompany.com/xbrl/taxonomy/ext}ItemWithBalance contains a balance attribute but type is not derived from moneratyItemType
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/105-01-ElementWithBalanceTypeNotMonetary-instance.xml
Id: V-02 Description: 105.02 Elemements where the substitutionGroup attribute value is tuple MUST NOT have a balance attribute
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException Tuples must not have xbrli:balance attribute
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/105-02-TuplesMustHaveNoBalanceAttribute-instance.xml
Id: V-03 Description: 105.03 An optional balance attribute MAY be added to the definition of an element if its type is monetaryItemType or derived from monetaryItemType.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/105-03-ElementWithBalanceTypeMonetary.xml
Id: V-04 Description: 105.04 Derived element of Monetary datatype with Balance defined
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/105-04-DerivedElementWithBalanceTypeMonetary.xsd
Id: V-05 Description: 105.05 Derived element with string datatype with Balance defined
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLValidationException The item type of {http://mycompany.com/xbrl/taxonomy/ext}ItemWithBalance contains a balance attribute but type is not derived from moneratyItemType
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/105-05-DerivedElementWithBalanceTypeString.xsd
Section 5.1.1 - TypeExtension
Id: Description: Type Extension - Valid
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/155-TypeExtension-Valid.xsd
Section 5.1 Taxonomy schemas
Id: V-1 Description: 106.01 Taxonomy schema has non-empty targetNamespace attribute value.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/106-01-NonEmptyTargetNamespace.xsd
Id: V-2 Description: 106.02 Taxonomy schema has empty targetNamespace attribute value. Empty targetNamespace attribute is prohibited by Section 5.1.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.DTSDiscoveryException DTSDiscoveryException URI is: file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/106-02-EmptyTargetNamespace.xsd
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/106-02-EmptyTargetNamespace.xsd
Id: V-3 Description: 106.03 Both including and included Taxonomy schemas have identical targetNamespace attribute values. Valid and XBRL specification 5.1 recommended approach.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/106-03-ExtTargetNamespace.xsd
Id: V-4 Description: 106.04 Included taxonomy schema has no targetNamespace attribute but including taxonomy schema has targetNamespace attribute which it is valid. Even though this usage does not recommended by XBRL Specification section 5.1, this is valid.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/106-04-ExtTargetNamespace.xsd
DTS discovery when linkbases are not root elements of XML documents.
Id: V-1 Description: 107.01 DTS descovery begins from a taxonomy schema that contains a linkbase reference to a linkbase that that is placed inside the documentation of another XML schema. The other XML schema also contains valid XML Schema markup but the markup violates the requirements of the XBRL 2.1 specification. By following the rules of DTS discovery the linkbase in the second schema should be discovered, and processed *as a taxonomy schema* so the material that violates the XBRL 2.1 specification should trigger a determination that the result is invalid.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLRuntimeException Document referenced in a link:linkbaseRef element is not a linkbase
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/107-01-SchemaLinkingToALinkbaseInAnotherSchema.xsd
Section 5.1.3.4 and Section 5.1.4.5 - The element where the role/arcrole is used MUST correspont to an instance of the QName defined in the roleType/arcroleType declaration but ONLY if it is used inside a standard extended link or in a custom extended link with a roleRef/arcroleRef pointing to the roleType/arcroleType declaration
Id: Description: A new roleType definition contains a usedOn element pointing to a valid QName but a standard linkbase uses it in a different element (a label resource)- Invalid
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLRuntimeException Role uri http://xbrl.org/role/conformance is used on element {http://www.xbrl.org/2003/linkbase}label but there is no a usedOn declaration for that element QName. Valid elements are: {http://www.w3.org/1999/xlink}label
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/160-01-roleType-standard-linkbase-incorrect-element-Invalid.xsd
Id: Description: A new roleType definition contains a usedOn element pointing to a valid QName but a standard linkbase uses it in a different element (a labelLink element)- Invalid
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLRuntimeException Role uri http://xbrl.org/role/conformance is used on element {http://www.xbrl.org/2003/linkbase}labelLink but there is no a usedOn declaration for that element QName. Valid elements are: {http://www.xbrl.org/2003/linkbase}label
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/160-02-roleType-standard-linkbase-incorrect-element-Invalid.xsd
Id: Description: A new roleType definition contains a usedOn element pointing to a valid QName; a custom linkbase uses it in a different element but there is no a roleRef pointing to the roleType declaration - Valid
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/160-04-roleType-non-standard-linkbase-incorrect-element-Valid.xsd
Id: Description: This is the same 160-04 test case but the hidden schema imports a new taxonomy in the DTS. That imported schema is not a valid taxonomy and it should be ignored because it is not in the DTS. - valid
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/160-05-roleType-non-standard-linkbase-incorrect-element-invalid.xsd
Id: Description: A role that is only used on elements that cannot accept an xlink:role attribute is nonsensical but valid.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/RoleUsedOnArcElement.xsd
Id: Description: An arcrole that is only used on elements that cannot accept an xlink:arcrole attribute is nonsensical but valid.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/ArcroleUsedOnNonArcElements.xsd
Id: Description: The UsedOn values are not S-Equal even though they have the same namespace prefix and element name, because the namespace prefixes resolve to different namespaces.
OK. Expected valid - result is valid
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/UsedOnSEquality-valid.xsd
Id: Description: The UsedOn values are S-Equal even though they have different namespace prefixes, because the namespace prefixes resolve to the same namespace.
OK. Expected invalid - result is invalid com.ihr.xbrl.om.XBRLRuntimeException Same Used On {http://www.xbrl.org/2003/linkbase}someArc defined multiple times
file:/C:/Documents%20and%20Settings/Ignacio/workspace/conformance/Common/schema/UsedOnSEquality-invalid.xsd
Not passed: 0
Passed: 447
Not executed: 0