 |
|
|
Two tuples in the "ifrs-gp-2006-08-15.xsd" contain child elements which
themselves are declared with an attribute abstract="true". This I
believe would cause these items to be unusable in a schema-validated
instance.
TUPLE
DefinedBenefitPlan
CHILD HAVING @abstract="true"
EffectsOfChangesOfOnePercentagePointInAssumedMedicalCostTrendRates
ExpenseRecognisedInProfitAndLossStatementTotal
TUPLE
AmountForCurrentAnnualPeriodAndPreviousFourAnnualPeriods
CHILD HAVING @abstract="true"
ExperienceAdjustmentArisingOnPlanAssetsExpressedAsAmountOrPercentageOfPlanAssetsAtBalanceSheetDate
ExperienceAdjustmentArisingOnPlanLiabilitiesExpressedAsAmountOrPercentageOfPlanLiabilitiesAtBalanceSheetDate
From a general development perspective, the way I can notice these
anomalies is enlightening. Basically it is through better presentation
of schemas in terms of sequence, tuple participation and meta-data on
attributes. As a result, I have less interest in the sequence of schemas
(which have been conveniently, yet nonsensically, mixed alphabetically
by name), because we must look at <xsd:element>s in an xbrl schema
sorted on various combinations of "attributes". The same routine
sorting and summary applies to any xbrl schema of typical items..
regards,
bill p
|
|
| |
These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.
| |
| |
|
|
|
