XBRL International - Specification Working Group

Comments on Public Working Draft of XBRL 2.1, Specification dated 2003-04-23

Resolution Status

Last updated: 2003-06-11 08:34 Eastern Daylight Time (= UTC - 5 hours)

Purpose of this document:

This document shows the status of resolution of comments made to the Specification Working Group of XBRL International on the Public Working Draft of the XBRL 2.1, Specification dated 2003-04-23, at the time it was last updated (see above). It will be continuously updated on a regular basis. This document is maintained by Hugh Wallis - hugh_wallis@hyperion.com to whom questions and notification of any errors or omissions should be made. This document is provided on a "best effort" basis and no liability is accepted for any errors or omissions by either Hugh Wallis, Hyperion Solutions Corporation or XBRL International Inc. Users making use of the information provided in this document do so at their own risk.

Where the detailed text of any comment is contained in an e-mail message sent to one of the XBRL mailing lists it is hyperlinked to the relevant place in the archive for that mailing list. It is necessary to be a subscriber to that mailing list in order to view the archived message. Membership of all XBRL mailing lists except XBRL-Public is available only to members of XBRL International. Any such archived message will open in a new browser window so users should turn off any "pop-up stopper" software they may have installed in order to follow such links.

Latest Version:

The latest version of the Public Working Draft is available from the XBRL.org website at the following URLs:

PDF Version: http://www.xbrl.org/2003/XBRL-WD-2003-05-16.pdf

Word Version: http://www.xbrl.org/2003/XBRL-WD-2003-05-16.doc

Zip file with schemas: http://www.xbrl.org/2003/XBRL-WD-2003-05-16.zip

Index to Comments:

A comment may be in one of the states shown below. Colour coding is used in the index as a quick reference to the state of any comment - 

Red - Comment not yet being addressed
Blue - Resolution pending or under discussion
Green - Resolved

Note: by clicking on the comment number in the index you will be taken to the detail section for the comment in question.

Comment
Number		 Commentator Date Submitted Comment Abstract
001 Suguru WASHIO - wasio@jp.fujitsu.com 2003-04-24

duplicatesLegal attribute should be split to handle tuples and items separately - items should default to "false", tuples to "true"
002 Hugh Wallis - hugh_wallis@hyperion.com 2003-04-25

Either allow "all" in tuples or state reason why not allowed in the specification text
003 Hugh Wallis - hugh_wallis@hyperion.com 2003-04-25 Various errors in Example 20
004 Hugh Wallis - hugh_wallis@hyperion.com 2003-04-25 Various typos around Example 22
005 Hugh Wallis - hugh_wallis@hyperion.com 2003-04-25 Typo in section 5.3 - should be 4 types (not 3)
006 Hugh Wallis - hugh_wallis@hyperion.com 2003-04-25 Editorial - can make use of the standard definition of "parent" in sec 4.5.2
007 Hugh Wallis - hugh_wallis@hyperion.com 2003-04-25

Suggest clarification of various points about the fractionItemType in section 5.2
008 Hugh Wallis - hugh_wallis@hyperion.com 2003-04-25

xbrli:instantaneous attribute missing in Example 29
009 Hugh Wallis - hugh_wallis@hyperion.com 2003-04-25 Clarify overview text on type derivation and move it to taxonomy section
010 Charles Hoffman - CharlesHoffman@olywa.net 2003-04-25

Suggest naming profile attributes positively (e.g. "allowDeprecated") instead of negatively (e.g. "noDeprecated")
011 Hugh Wallis - hugh_wallis@hyperion.com 2003-04-29

The Schema Fragment in 5.5.2 is inconsistent with the actual schema in respect of the namespace namespace. (xml:)
012 Hugh Wallis - hugh_wallis@hyperion.com 2003-04-29 The definitions of the various profile attributes are inconsistent between linkbases and instance documents. 
013 Hugh Wallis - hugh_wallis@hyperion.com 2003-04-29 Example 7 refers to decimals where it should refer to significant figures 
014 Hugh Wallis - hugh_wallis@hyperion.com 2003-04-29 Inconsistent definition of XBRL instance between 1.4 and 4.3 
015 Hugh Wallis - hugh_wallis@hyperion.com 2003-04-30 Confusing namespace in Example 27 
016 Hugh Wallis - hugh_wallis@hyperion.com 2003-04-30 Replace "sub-element" and other terms with the XPATH equivalent throughout the document. e.g. Sec 4.5 para 2 
017 David vun Kannon - dvunkannon@hotmail.com   2003-05-01 Duplicate detection is more important than precision, but the choices provided make duplicate detection much harder. Suggest an "ignorePrecision" profile
018 Hugh Wallis - hugh_wallis@hyperion.com 2003-05-02 Since the <group> element is no longer permitted except at root level by the xbrl-instance schema it is not necessary to include the last sentence in 4.3 which envisages such a situation
019 Hugh Wallis - hugh_wallis@hyperion.com 2003-05-02 Update 4.3 to reflect the fact that <group> prohibits all profile type attributes, not just "profile" itself
020 Hugh Wallis - hugh_wallis@hyperion.com 2003-05-02 (deprecated) precision attribute on numericContext has inconsistent type between text of spec and accompanying schema file
021 Hugh Wallis - hugh_wallis@hyperion.com 2003-05-07 Correct definition of decimalsType and precisionType to avoid inappropriate use of "INF" from the float datatype - use "INF" from the string datatype instead
022 Hugh Wallis - hugh_wallis@hyperion.com 2003-05-07 fractionItemType should use decimal instead of float
023 Charles Hoffman - CharlesHoffman@olywa.net 2003-05-07 Need scenarioType (and segmentType)
024 Walter Hamscher - walter@hamscher.com 2003-05-09 Eliminate the need for symmetric arcs in linkbases
025 Walter Hamscher - walter@hamscher.com 2003-05-09 Remove unused parts from the xlink.xsd and xl.xsd schemas
026 Hugh Wallis - hugh_wallis@hyperion.com 2003-05-07 Resolve inconsistencies in the definition of equality
027 David vun Kannon - dvunkannon@hotmail.com   2003-05-13 Remove the requirement (in section 6) to use the xbrl.org supplied schema for ISO4217 codes since it is too onerous for xbrl.org to commit to maintain it
028 Bill Palmer - palmer@execpc.com  2003-05-13 Correct the XPATH terminology used to define the relationships such as Uncle and Sibling
029 Charles Hoffman - CharlesHoffman@olywa.net 2003-05-12

A calculation summation­item arc where the summation has a balance attribute and the item does not is an ERROR. 

The item may have a balance attribute when the summation does not.
030 Walter Hamscher - walter@hamscher.com 2003-05-12 Provide a means to identify when an item has effectively been removed by an extension taxonomy
031 Don Dwiggins - Don.Dwiggins@ubmatrix.com  2003-05-02 Section 5.5.7.13.1: the third sentence has "from" and "to" backward; the "to" element must be the sibling or uncle of the "from" element
032 Bill Palmer - palmer@execpc.com  2003-05-13 Improve clarity in Example 24
033 Dennis McCarthy - Dennis_McCarthy@onesource.com  2003-05-07 The spec does not explicitly address the manner and effect of the use of the XML Schema construct "nillable" in taxonomy elements. Various opinions have been expressed about whether to mandate its  use. This comment seeks to have all aspects surrounding this construct addressed in the spec. 
034 Hugh Wallis - hugh_wallis@hyperion.com
 Walter Hamscher - walter@hamscher.com
 David vun Kannon - dvunkannon@hotmail.com  		 2003-05-08 Clarify the normative status and location of provided schemas
035 Don Dwiggins - Don.Dwiggins@ubmatrix.com
Walter Hamscher - walter@hamscher.com 		2003-05-15 The spec needs to permit some cyclic item-summation arcs which are currently prohibited
036 Hugh Wallis - hugh_wallis@hyperion.com 2003-05-21 Change 4.5 to correct restrictions on derivations from tupleType
037 Tom Egan - tegan@deloitte.com 2003-05-12 Incorrect text in definition of the monthYear type periodConstraint element (sec 5.5.6.5.4)
038 Don Bruey - dbruey@CreativeSolutions.com  2003-05-22 Section 5.5.7.10.2 - Why is priority an integer, when order is a decimal? Why not make priority a decimal for the same reason as the spec says order is one - for inserting values
039 Hugh Wallis - hugh_wallis@hyperion.com 2003-05-29 In 5.5.7.15 there are no rules that enable the inference of the values of alias concepts from known or inferred values of their associated essence concept.
040 Hugh Wallis - hugh_wallis@hyperion.com 2003-05-29 Although the xbrli:shares and xbrli:pure types have been provided for use as the units of items with sharesItemType and pureItemType there is no requirement or guidance given in this regard. 
041 David vun Kannon - dvunkannon@hotmail.com   2003-05-28 The scope of application of use="required" arcs on a definitionArc having the whole-part or part-whole arcrole is insufficiently defined in 5.5.7.10.1
042 Bill Palmer - palmer@execpc.com  2003-05-31 Propose simplification of relativeContext constructs
043 Frank Lippold - frank.lippold@datev.de  2003-05-21 The specification needs to be more specific about the ambiguity when converting parent-child roles from 2.0 to 2.1 definition arcs.
044 Hugh Wallis - hugh_wallis@hyperion.com 2003-05-31 The text of the specification is inconsistent as to whether it refers to "arc role" or "arcrole". The XLink spec uses "arc role" in the one place where the term is used in the same way in the text (http://www.w3.org/TR/xlink/index.html#xlg). I think we should do the same thing
045 Geoff Shuetrim - gshuetrim@kpmg.com.au 2003-05-31 The definitions of concrete and abstract element in Table 1.4 should be tighter, referring to the relevant parts of the XML Schema specification
046 Geoff Shuetrim - gshuetrim@kpmg.com.au 2003-05-31 Review the definition of CWA because an assertion of CWA is only true in the context of a specific set of possible calculations. Add new calculations and the assertion needs to be reviewed.
047 Geoff Shuetrim - gshuetrim@kpmg.com.au 2003-06-02 Need to be more specific in 5.5.6.5.3 (what is an "empty portion"?)
048 Hugh Wallis - hugh_wallis@hyperion.com 2003-06-04 Error and potentially ambiguous or unclear wording in 5.5.7.13.1 Calculation scoping within tuples
049 Masatomo Goto - mg@jp.fujitsu.com  2003-06-02 Eliminate xsi:type in an instance
050 Campbell Pryde - cpryde@kpmg.com  2003-05-30 Change the Example 23 to use whole-part rather than container-content
051 Hugh Wallis - hugh_wallis@hyperion.com 2003-06-09 4.4.2 specifies illegal syntax (T24:00:00) when defining the interpretation of endDate
052 Hugh Wallis - hugh_wallis@hyperion.com 2003-06-09 Example 54 (numbering from 2003-05-16 draft) in section 5.5.7.12 is incorrect - the instant in context "ni1" should be 2001-04-01 because of the date interpretation rules in 4.4.2
053 Bill Palmer - palmer@execpc.com  2003-06-09 Suggest emphasizing the aggregate or primary part of arcrole names by capitalization (e.g. WHOLE-part and part-WHOLE)
054 Hugh Wallis - hugh_wallis@hyperion.com 2003-06-09 It is not explicit that the value of an element at the "item" end of an "item-summation" type arc cannot be inferred. i.e. you MUST NOT infer the value of B from the known values of A and C in the equation A + B = C unless B is at the summation end of one of the arcs that define this equation.
055 Charles Hoffman - CharlesHoffman@olywa.net 2003-06-09 Table 9, page 58, “Standard label role attribute values" - positiveTerseLabel appears twice - second one should be negativeTerseLabel

Comment Details:

Comment Number:

 001
Commentator's name and e-mail address: Suguru WASHIO - wasio@jp.fujitsu.com
Date comment submitted: 2003-04-24
Comment Abstract:

duplicatesLegal attribute should be split to handle tuples and items separately - items should default to "false", tuples to "true"
Comment Detail: See duplicatesLegal attribute

See also follow up from commentator at Re- Draft teleconference minutes 1 May 2003
Other related comments (if any) 010, 012, 017
Comment State Comment under discussion by appropriate WG
Back to Index

 

Comment Number:

 002
Commentator's name and e-mail address: Hugh Wallis - hugh_wallis@hyperion.com
Date comment submitted: 2003-04-25
Comment Abstract:

Either allow "all" in tuples or state reason why not allowed in the specification text
Comment Detail: COMMENT- Tuples - "sequence", "choice" - but not "all"-
Other related comments (if any)
Comment State Comment under discussion by appropriate WG
Back to Index

 

Comment Number:

 003
Commentator's name and e-mail address: Hugh Wallis - hugh_wallis@hyperion.com
Date comment submitted: 2003-04-25
Comment Abstract: Various errors in Example 20
Comment Detail: COMMENT- Errors in Example 20
Other related comments (if any)
Comment State Resolution approved by Spec and Domain WGs
Proposed Resolution:
  • Change example to read:

<schema targetNamespace="http://mycompany.com/xbrl/taxonomy"
        xmlns="http://www.w3.org/2001/XMLSchema" 
        xmlns:s="http://mycompany.com/xbrl/taxonomy"
        xmlns:xbrli="http://www.xbrl.org/2003/instance" >

<element name="managementName" type="xbrli:tokenItemType" xbrli:instantaneous="true"
         substitutionGroup="xbrli:item"/>
  <element name="managementTitle" type="xbrli:tokenItemType" xbrli:instantaneous="true" 
         substitutionGroup="xbrli:item"/>
  <element name="managementAge" type="xbrli:nonNegativeIntegerItemType" 
         xbrli:instantaneous="true" substitutionGroup="xbrli:item"/>

etc.

  • Change the first paragraph after this example so that the words sequence and choice are in courier font (with lower case "s" for sequence)
Either:
Date of approval of resolution by the Spec Working Group
2003-05-01
Date of approval of resolution by the Domain Working Group
2003-05-12
Or:
Notice that approval not required
Date commentator notified of resolution: 2003-05-12
Commentator's response to resolution (if any)
Back to Index

 

Comment Number:

 004
Commentator's name and e-mail address: Hugh Wallis - hugh_wallis@hyperion.com
Date comment submitted: 2003-04-25
Comment Abstract: Various typos around Example 22
Comment Detail: COMMENT- Typos around Example 22
Other related comments (if any)
Comment State Minor comment, resolution of which does not require explicit approval of a WG – resolution complete.
Proposed Resolution:
  1. Change the sentence before Example 22 to read: "Although the description and date acquired are relevant for any property, the property either has a fair market value or has already been disposed of, but not both." - i.e. remove the extra "is" after the second "property"
  2. Change the text of Example 22 to read: "Example: tuples associate concepts that cannot be understood independently and repeat within an XBRL instance. Multiple occurrences of a tuple within an XBRL instance are distinguished by having different content and contexts."
Either:
Date of approval of resolution by the Spec Working Group
Date of approval of resolution by the Domain Working Group
Or:
Notice that approval not required
Not required
Date commentator notified of resolution: 2003-05-08
Commentator's response to resolution (if any)
Back to Index

 

Comment Number:

 005
Commentator's name and e-mail address: Hugh Wallis - hugh_wallis@hyperion.com
Date comment submitted: 2003-04-25
Comment Abstract: Typo in section 5.3 - should be 4 types (not 3)
Comment Detail: COMMENT- Typo - section 5.3
Other related comments (if any)
Comment State Minor comment, resolution of which does not require explicit approval of a WG – resolution complete.
Proposed Resolution: Change "3" to "4" in third line of section 5.3
Either:
Date of approval of resolution by the Spec Working Group
Date of approval of resolution by the Domain Working Group
Or:
Notice that approval not required
Approval not required
Date commentator notified of resolution: 2003-04-26
Commentator's response to resolution (if any)
Back to Index

 

Comment Number:

 006
Commentator's name and e-mail address: Hugh Wallis - hugh_wallis@hyperion.com
Date comment submitted: 2003-04-25
Comment Abstract: Editorial - can make use of the standard definition of "parent" in sec 4.5.2
Comment Detail: COMMENT- Editorial - can make use of the standard definition of "par
Other related comments (if any)
Comment State Minor comment, resolution of which does not require explicit approval of a WG – resolution complete.
Proposed Resolution: Remove second sentence so paragraph now reads:

No two tuples in an XBRL instance may have the same structure and content under a common parent.  This does not refer to any relationship expressed in a linkbase among taxonomy elements.
Either:
Date of approval of resolution by the Spec Working Group
Date of approval of resolution by the Domain Working Group
Or:
Notice that approval not required
Approval not required
Date commentator notified of resolution: 2003-04-30
Commentator's response to resolution (if any)
Back to Index

 

Comment Number:

 007
Commentator's name and e-mail address: Hugh Wallis - hugh_wallis@hyperion.com
Date comment submitted: 2003-04-25
Comment Abstract:

Suggest clarification of various points about the fractionItemType in section 5.2
Comment Detail: COMMENT- Clarification - section 5.2
Other related comments (if any) 009
Comment State Resolution approved by Spec and Domain WGs
Proposed Resolution:
  1. Change the section title of 5.2 to be "The fractionItemType data type"
  2. remove the word "new" from the 4th line of 5.2
  3. Add the schema fragment for fractionItemType to the end of section 5.2
Either:
Date of approval of resolution by the Spec Working Group
2003-05-15
Date of approval of resolution by the Domain Working Group
2003-05-20
Or:
Notice that approval not required
Date commentator notified of resolution: 2003-05-20
Commentator's response to resolution (if any)
Back to Index

 

Comment Number:

 008
Commentator's name and e-mail address: Hugh Wallis - hugh_wallis@hyperion.com
Date comment submitted: 2003-04-25
Comment Abstract:

xbrli:instantaneous attribute missing in Example 29
Comment Detail: COMMENT- Example 29 needs xbrli-instantaneous attribute
Other related comments (if any)
Comment State Resolution approved by Spec and Domain WGs
Proposed Resolution: Change tag in the example to read :

<element name="stateProvince" id="my_stateProvince" xbrli:instantaneous="true"
 substitutionGroup="xbrli:item" type="my:stateProvinceItemType"/>
Either:
Date of approval of resolution by the Spec Working Group
2003-05-01
Date of approval of resolution by the Domain Working Group
2003-05-12
Or:
Notice that approval not required
Date commentator notified of resolution: 2003-05-12
Commentator's response to resolution (if any)
Back to Index

 

Comment Number:

 009
Commentator's name and e-mail address: Hugh Wallis - hugh_wallis@hyperion.com
Date comment submitted: 2003-04-25
Comment Abstract: Clarify overview text on type derivation and move it to taxonomy section
Comment Detail: COMMENT- Clarification and location - last para sec 2.1
Other related comments (if any) 007
Comment State Resolution approved by Spec and Domain WGs
Proposed Resolution:
  1. Delete the last paragraph from section 2.1

"Derivation of new item and tuple types from those defined by XBRL itself have been restricted so that item types may only be defined by extension from simple types in XML Schema or the fraction item type, and tuples may only be derived by restriction using the choice and sequence constructs of XML Schema. "

  1. Add the following paragraph to section 2.2

"Derivation of new item and tuple types from those defined by XBRL itself has been limited so that item types may only be defined by restriction from the set of item types provided by XBRL. This set contains item types that are derived by extension from all the built-in simple types of XML Schema and a special purpose type with complex content, the fractionItemType. Tuples may be derived by restriction using only the choice and sequence constructs of XML Schema. "
Either:
Date of approval of resolution by the Spec Working Group
2003-05-01
Date of approval of resolution by the Domain Working Group
2003-05-12
Or:
Notice that approval not required
Date commentator notified of resolution: 2003-05-12
Commentator's response to resolution (if any)
Back to Index

 

Comment Number:

 010
Commentator's name and e-mail address: Charles Hoffman - CharlesHoffman@olywa.net
Date comment submitted: 2003-04-25
Comment Abstract:

Suggest naming profile attributes positively (e.g. "allowDeprecated") instead of negatively (e.g. "noDeprecated")
Comment Detail: COMMENT- 4.1.1 Profile Attributes
Other related comments (if any) 001, 012
Comment State Not implemented
Proposed Resolution: No action to be taken
Either:
Date of approval of resolution by the Spec Working Group
2003-05-01
Date of approval of resolution by the Domain Working Group
Or:
Notice that approval not required
Date commentator notified of resolution: 2003-05-02
Commentator's response to resolution (if any)
Back to Index

 

Comment Number:

 011
Commentator's name and e-mail address: Hugh Wallis - hugh_wallis@hyperion.com
Date comment submitted: 2003-04-29
Comment Abstract: The Schema Fragment in 5.5.2 is inconsistent with the actual schema in respect of the namespace namespace. 
Comment Detail: COMMENT- 5.5.2 Schema Fragment inconsistent
Other related comments (if any)
Comment State Resolution approved by Spec and Domain WGs
Proposed Resolution: In the text of the specification document 

1) Delete "xmlns:x=..." from the <schema> tag
2) Change ref="x:specialAttrs" to ref="xml:specialAttrs"

to make it consistent with the schema distributed concurrently
Either:
Date of approval of resolution by the Spec Working Group
2003-05-01
Date of approval of resolution by the Domain Working Group
2003-05-12
Or:
Notice that approval not required
Date commentator notified of resolution: 2003-05-12
Commentator's response to resolution (if any)
Back to Index

 

Comment Number:

 012
Commentator's name and e-mail address: Hugh Wallis - hugh_wallis@hyperion.com
Date comment submitted: 2003-04-29
Comment Abstract: The definitions of the various profile attributes are inconsistent between linkbases and instance documents. 
Comment Detail: COMMENT- Inconsistent profile defintiions for instances and linkbase

see also Fwd- [DISCUSSION] Profile Attributes
Other related comments (if any) 001, 010, 017
Comment State Comment under discussion by appropriate WG
Back to Index

 

Comment Number:

 013
Commentator's name and e-mail address: Hugh Wallis - hugh_wallis@hyperion.com
Date comment submitted: 2003-04-29
Comment Abstract: Example 7 refers to decimals where it should refer to significant figures 
Comment Detail: COMMENT- Example 7 has "decimal" where it refers to "precision"
Other related comments (if any)
Comment State Minor comment, resolution of which does not require explicit approval of a WG – resolution complete.
Proposed Resolution: Change the first sentence of the explanatory text of Example 7 to read "The value of Capital Leases in the numeric context labelled c1 is 727000 accurate to 3 significant figures. "
Either:
Date of approval of resolution by the Spec Working Group
Date of approval of resolution by the Domain Working Group
Or:
Notice that approval not required
Approval not required
Date commentator notified of resolution: 2003-04-29
Commentator's response to resolution (if any)
Back to Index

 

Comment Number:

 014
Commentator's name and e-mail address: Hugh Wallis - hugh_wallis@hyperion.com
Date comment submitted: 2003-04-29
Comment Abstract: Inconsistent definition of XBRL instance between 1.4 and 4.3 
Comment Detail: COMMENT- When is an instance not an instance?
Other related comments (if any)
Comment State Resolution approved by Spec and Domain WGs
Proposed Resolution: Update the 1.4 definition of XBRL Instance to conform to that in 4.3 so that it reads:

An occurrence of the xbrl element (not necessarily an entire document) which contains concrete elements that together constitute one or more business reports.  The financial statements of Apple, expressed in XBRL, would be an XBRL instance. Note that this definition envisages that more than one XBRL instance MAY be contained in another non-XBRL instance document.
Either:
Date of approval of resolution by the Spec Working Group
2003-05-01
Date of approval of resolution by the Domain Working Group
2003-05-12
Or:
Notice that approval not required
Date commentator notified of resolution: 2003-05-12
Commentator's response to resolution (if any)
Back to Index

 

Comment Number:

 015
Commentator's name and e-mail address: Hugh Wallis - hugh_wallis@hyperion.com
Date comment submitted: 2003-04-30
Comment Abstract: Confusing namespace in Example 27 
Comment Detail: COMMENT: (was DISCUSSION:) Example 27
Other related comments (if any)
Comment State Minor comment, resolution of which does not require explicit approval of a WG – resolution complete.
Proposed Resolution: Change the namespace to be http://www.mycompany.com/taxonomy/2003-10-19
Either:
Date of approval of resolution by the Spec Working Group
Date of approval of resolution by the Domain Working Group
Or:
Notice that approval not required
Approval not required
Date commentator notified of resolution: 2003-04-30
Commentator's response to resolution (if any)
Back to Index

 

Comment Number:

 016
Commentator's name and e-mail address: Hugh Wallis - hugh_wallis@hyperion.com
Date comment submitted: 2003-04-30
Comment Abstract: Replace "sub-element" and other terms with the XPATH equivalent throughout the document. e.g. Sec 4.5 para 2 
Comment Detail: COMMENT- (was DISCUSSION-) 4.5 - para 2
Other related comments (if any)
Comment State Assigned to an editor – proposed resolution pending
Back to Index

 

Comment Number:

 017
Commentator's name and e-mail address: David vun Kannon - dvunkannon@hotmail.com  
Date comment submitted: 2003-05-01
Comment Abstract: Duplicate detection is more important than precision, but the choices provided make duplicate detection much harder. Suggest an "ignorePrecision" profile
Comment Detail: COMMENT: precision/decimal
Other related comments (if any) 001, 012
Comment State Assigned to an editor – proposed resolution pending
Back to Index

 

Comment Number:

 018
Commentator's name and e-mail address: Hugh Wallis - hugh_wallis@hyperion.com
Date comment submitted: 2003-05-02
Comment Abstract: Since the <group> element is no longer permitted except at root level by the xbrl-instance schema it is not necessary to include the last sentence in 4.2 which envisages such a situation.
Comment Detail: COMMENT- <group> no longer permitted except as root
Other related comments (if any)
Comment State Resolution approved by Spec and Domain WGs
Proposed Resolution: Remove the last sentence from section 4.2

Consuming applications MUST process occurrences of the (deprecated) group element not at top level (which were allowed in XBRL 2.0) as if their child elements appeared in their place.
Either:
Date of approval of resolution by the Spec Working Group
2003-05-15
Date of approval of resolution by the Domain Working Group
2003-05-20
Or:
Notice that approval not required
Date commentator notified of resolution: 2003-05-20
Commentator's response to resolution (if any)
Back to Index

 

Comment Number:

 019
Commentator's name and e-mail address: Hugh Wallis - hugh_wallis@hyperion.com
Date comment submitted: 2003-05-02
Comment Abstract: Update 4.3 to reflect the fact that <group> may not carry any profile type attributes, not just "profile" itself
Comment Detail: COMMENT- <group> prohibits all profile type attributes, not just "pr
Editor Responsible: Hugh Wallis - hugh_wallis@hyperion.com
Other related comments (if any)
Comment State Resolution approved by Spec and Domain WGs
Proposed Resolution:
Change the second sentence of 4.2 from
 
"Other than not allowing the profile attribute, its content model is identical to the xbrl element."
 
to
 
"Other than not allowing any of the profile attributes, its content model is identical to the xbrl element."
 
Either:
Date of approval of resolution by the Spec Working Group
2003-05-15
Date of approval of resolution by the Domain Working Group
2003-05-20
Or:
Notice that approval not required
Date commentator notified of resolution: 2003-05-20
Commentator's response to resolution (if any)
Back to Index

 

Comment Number:

 020
Commentator's name and e-mail address: Hugh Wallis - hugh_wallis@hyperion.com
Date comment submitted: 2003-05-02
Comment Abstract: (deprecated) precision attribute on numericContext has inconsistent type between text of spec and accompanying schema file
Comment Detail: COMMENT- numericContext inconsistency
Editor Responsible: Hugh Wallis - hugh_wallis@hyperion.com
Other related comments (if any)
Comment State Resolution approved by Spec and Domain WGs
Proposed Resolution: Change text of document (section 4.4) so that the attribute is declared the same as in the schema file. i.e.:

<attribute name="precision" type="positiveInteger" use="optional"/>

Also add the following text to section 4.4.4

As a deprecated attribute the facility to specify precision="INF" is not available on the numericContext element.
Either:
Date of approval of resolution by the Spec Working Group
2003-05-15
Date of approval of resolution by the Domain Working Group
2003-05-20
Or:
Notice that approval not required
Date commentator notified of resolution: 2003-05-20
Commentator's response to resolution (if any)
Back to Index

 

Comment Number:

 021
Commentator's name and e-mail address: Hugh Wallis - hugh_wallis@hyperion.com
Date comment submitted: 2003-05-07
Comment Abstract: Correct definition of decimalsType and precisionType to avoid inappropriate use of "INF" from the float datatype - use "INF" from the string datatype instead
Comment Detail: COMMENT: Correct definition of decimalsType and precisionType to avo
Editor Responsible: Hugh Wallis - hugh_wallis@hyperion.com
Other related comments (if any)
Comment State Resolution approved by Spec and Domain WGs
Proposed Resolution:
1) Change the definitions in the xbrl-linkbase.xsd to be as follows:
 

     <simpleType name="precisionType">

          <annotation>

               <documentation>

This type is used to specify the value of the (deprecated) precision attribute on numericContext and the precision attribute on numeric items.

It consists of the union of nonNegativeInteger and "INF" (used to signify infinite precision or "exact value")

    </documentation>

          </annotation>

          <union memberTypes="nonNegativeInteger">

               <simpleType>

                    <restriction base="string">

                         <enumeration value="INF"/>

                    </restriction>

               </simpleType>

          </union>

     </simpleType>

     <simpleType name="decimalsType">

          <annotation>

               <documentation>

This type is used to specify the value of the decimals attribute on numeric items.

It consists of the union of integer and "INF" (used to signify that a number is expressed to an infinite number of decimal places or "exact value")

          </documentation>

          </annotation>

          <union memberTypes="integer">

               <simpleType>

                    <restriction base="string">

                         <enumeration value="INF"/>

                    </restriction>

               </simpleType>

          </union>

     </simpleType>

 

2) Change the text and the schema fragments in 4.3.1 and 4.3.2 accordingly
Either:
Date of approval of resolution by the Spec Working Group
2003-05-15
Date of approval of resolution by the Domain Working Group
2003-05-20
Or:
Notice that approval not required
Date commentator notified of resolution: 2003-05-20
Commentator's response to resolution (if any)
Back to Index

 

Comment Number:

 022
Commentator's name and e-mail address: Hugh Wallis - hugh_wallis@hyperion.com
Date comment submitted: 2003-05-07
Comment Abstract: fractionItemType should use decimal instead of float
Comment Detail: COMMENT: Propose fractionItemType should use decimal instead of floa
Editor Responsible: Hugh Wallis - hugh_wallis@hyperion.com
Other related comments (if any)
Comment State Resolution approved by Spec and Domain WGs
Proposed Resolution:
1) Remove the following part of the xbrl-linkbase.xsd schema:
 

     <!-- nonZeroNonInfiniteFloat   -->

     <simpleType name="nonZeroNonInfiniteFloat">

          <annotation>

               <documentation>

As the name implies this is a float value that can not take the value ±0 or ±INF - it is used as the type for the denominator of a fractionItemType

          </documentation>

          </annotation>

          <union>

               <simpleType>

                    <restriction base="float">

                         <minExclusive value="0"/>

                         <maxExclusive value="INF"/>

                    </restriction>

               </simpleType>

               <simpleType>

                    <restriction base="float">

                         <minExclusive value="-INF"/>

                         <maxExclusive value="-0"/>

                    </restriction>

               </simpleType>

          </union>

     </simpleType>

 

 
and replace it as follows:
 

     <!-- nonZeroDecimal   -->

     <simpleType name="nonZeroDecimal">

          <annotation>

               <documentation>

As the name implies this is a decimal value that can not take the value 0 - it is used as the type for the denominator of a fractionItemType

          </documentation>

          </annotation>

          <union>

               <simpleType>

                    <restriction base="decimal">

                         <minExclusive value="0"/>

                    </restriction>

               </simpleType>

               <simpleType>

                    <restriction base="decimal">

                         <maxExclusive value="0"/>

                    </restriction>

               </simpleType>

          </union>

     </simpleType>

 

2) Change the definition of fractionItemType to be as follows:
 

     <!--                 fractionItemType        -->

     <complexType name="fractionItemType" final="extension">

          <sequence>

               <element name="numerator" type="decimal"/>

               <element name="denominator" type="xbrli:nonZeroDecimal"/>

          </sequence>

          <attribute name="numericContext" type="IDREF" use="required"/>

          <anyAttribute namespace="##other" processContents="lax"/>

     </complexType>

 

3) Update the schema fragment in section 4.3 of the spec accordingly

 
Either:
Date of approval of resolution by the Spec Working Group
2003-05-15
Date of approval of resolution by the Domain Working Group
2003-05-20
Or:
Notice that approval not required
Date commentator notified of resolution: 2003-05-20
Commentator's response to resolution (if any)
Back to Index

 

Comment Number:

 023
Commentator's name and e-mail address: Charles Hoffman - CharlesHoffman@olywa.net
Date comment submitted: 2003-05-07
Comment Abstract: Need scenarioType (and segmentType)
Comment Detail: COMMENT- SenarioType

expanded on further by Walter Hamscher in a private e-mail

"Define an xbrli:segmentType and abstract element -- analogous to xbrli:partType and allowing only those elements to appear in the segment.

Define an xbrli:scenarioType and abstract element -- analogous to xbrli:partType and allowing only those elements to appear in the scenario."
Editor Responsible: Hugh Wallis - hugh_wallis@hyperion.com
Other related comments (if any)
Comment State Not implemented
Proposed Resolution: After discussion at the joint Spec Domain WG meeting in Amsterdam 2003-05-20 the comment was withdrawn by the commentator
Either:
Date of approval of resolution by the Spec Working Group
2003-05-20
Date of approval of resolution by the Domain Working Group
2003-05-20
Or:
Notice that approval not required
Date commentator notified of resolution: 2003-05-20
Commentator's response to resolution (if any)
Back to Index

 

Comment Number:

 024
Commentator's name and e-mail address: Walter Hamscher - walter@hamscher.com
Date comment submitted: 2003-05-09
Comment Abstract: Eliminate the need for symmetric arcs in linkbases
Comment Detail: COMMENT- Redundant arc roles should be deprecated
Editor Responsible: Walter Hamscher - walter@hamscher.com - now Hugh Wallis - hugh_wallis@hyperion.com
Other related comments (if any)
Comment State Comment under discussion by appropriate WG
Back to Index

 

Comment Number:

 025
Commentator's name and e-mail address: Walter Hamscher - walter@hamscher.com
Date comment submitted: 2003-05-09
Comment Abstract: Remove unused parts from the xlink.xsd and xl.xsd schemas
Comment Detail: COMMENT- Remove the xl-title abstract element and other unused mater
Editor Responsible: Walter Hamscher - walter@hamscher.com
Other related comments (if any)
Comment State Not implemented
Proposed Resolution: The commentator withdrew the comment taking the pragmatic approach of "if it isn't broken, don,t fix it"
Either:
Date of approval of resolution by the Spec Working Group
Date of approval of resolution by the Domain Working Group
Or:
Notice that approval not required
Not required
Date commentator notified of resolution: 2003-05-15
Commentator's response to resolution (if any)
Back to Index

 

Comment Number:

 026
Commentator's name and e-mail address: Hugh Wallis - hugh_wallis@hyperion.com
Date comment submitted: 2003-05-07
Comment Abstract: Resolve inconsistencies in the definition of equality
Comment Detail: COMMENT: resolve inconsistencies in the definition of equality
Editor Responsible: Hugh Wallis - hugh_wallis@hyperion.com
Other related comments (if any)
Comment State Resolution approved by Spec and Domain WGs
Proposed Resolution: See Re- COMMENT- resolve inconsistencies in the definition of equality 
Either:
Date of approval of resolution by the Spec Working Group
2003-05-15 (it was noted that further changes may be necessary but that the proposed resolution represents an improvement over the original text)
Date of approval of resolution by the Domain Working Group
2003-05-20
Or:
Notice that approval not required
Date commentator notified of resolution: 2003-05-20
Commentator's response to resolution (if any)
Back to Index

 

Comment Number:

 027
Commentator's name and e-mail address: David vun Kannon - dvunkannon@hotmail.com  
Date comment submitted: 2003-05-13
Comment Abstract: Remove the requirement (in section 6) to use the xbrl.org supplied schema for ISO4217 codes since it is too onerous for xbrl.org to commit to maintain it
Comment Detail: Re- COMMENT- Remove the xl-title abstract element and other unused m (note that the title of this post does not relate to this comment - this comment arose during the discussion of another comment)
Editor Responsible: Phillip Engel - phillipengel@kpmg.com
Other related comments (if any) 040
Comment State Comment under discussion by appropriate WG
Back to Index

 

Comment Number:

 028
Commentator's name and e-mail address: Bill Palmer - palmer@execpc.com 
Date comment submitted: 2003-05-13
Comment Abstract: Correct the XPATH terminology used to define the relationships such as Uncle and Sibling
Comment Detail: COMMENT- Terminology XPATH
Editor Responsible: Hugh Wallis - hugh_wallis@hyperion.com
Other related comments (if any)
Comment State Resolution approved by Spec and Domain WGs
Proposed Resolution: Replace the relevant definitions in section 1.4 with the following:

child, parent, sibling, grandparent, uncle, ancestor

Relationships among elements in an XBRL instance: using the terminology of [XPATH], for any element E, another element F is its:

 

  • child if and only if F appears on the child axis of E
  • parent if and only if F appears on the parent axis of E
  • sibling if and only if F appears on the child axis of the parent of E and is not E itself
  • grandparent if and only if F is the parent of the parent of E
  • uncle if and only if F is a sibling of the parent of E
  • ancestor if and only if F appears on the ancestor axis of E

 

Either:
Date of approval of resolution by the Spec Working Group
2003-05-15
Date of approval of resolution by the Domain Working Group
2003-05-20
Or:
Notice that approval not required
Date commentator notified of resolution: 2003-05-15
Commentator's response to resolution (if any)
Back to Index

 

Comment Number:

 029
Commentator's name and e-mail address: Charles Hoffman - CharlesHoffman@olywa.net
Date comment submitted: 2003-05-12
Comment Abstract:

A calculation summation­item arc where the summation has a balance attribute and the item does not is an ERROR. 

The item may have a balance attribute when the summation does not.
Comment Detail: Fw- COMMENT- Add new constraint to balances
Editor Responsible: Walter Hamscher - walter@hamscher.com
Other related comments (if any)
Comment State Comment under discussion by appropriate WG
Back to Index

 

Comment Number:

 030
Commentator's name and e-mail address: Walter Hamscher - walter@hamscher.com
Date comment submitted: 2003-05-13
Comment Abstract: Provide a means to identify when an item has effectively been removed by an extension taxonomy
Comment Detail: Fw- COMMENT- As if the item had been removed
Editor Responsible: Walter Hamscher - walter@hamscher.com
Other related comments (if any)
Comment State Not implemented
Proposed Resolution: Discussion at the joint meeting of Spec and Domain WGs in Amsterdam 2003-05-20 determined that there was no requirement for this feature at this time
Either:
Date of approval of resolution by the Spec Working Group
2003-05-20
Date of approval of resolution by the Domain Working Group
2003-05-20
Or:
Notice that approval not required
Date commentator notified of resolution: 203-05-20
Commentator's response to resolution (if any)
Back to Index

 

Comment Number:

 031
Commentator's name and e-mail address: Don Dwiggins - Don.Dwiggins@ubmatrix.com 
Date comment submitted: 2003-05-02
Comment Abstract: Section 5.5.7.13.1: the third sentence has "from" and "to" backward; the "to" element must be the sibling or uncle of the "from" element
Comment Detail: See COMMENT- Section 5.5.7.13.1
Editor Responsible: Hugh Wallis - hugh_wallis@hyperion.com
Other related comments (if any) 042, 048
Comment State Comment under discussion by appropriate WG
Back to Index

 

Comment Number:

 032
Commentator's name and e-mail address: Bill Palmer - palmer@execpc.com
Date comment submitted: 2003-05-14
Comment Abstract: Improve clarity in Example 24 
Comment Detail: Improve clarity in Example 24 as follows:
    a) either change s:totalGross to 12000 (since it appears to be the sum
of numbers that add to 12000 rather than 6000 notwithstanding the lack of
any computation linkbase) or remove it altogether since it is not used
elsewhere in the example, and
    b) make the period of the numericContext the same as that of the
nonNumericContext
Editor Responsible: Hugh Wallis - hugh_wallis@hyperion.com
Other related comments (if any)
Comment State Comment under discussion by appropriate WG
Back to Index

 

Comment Number:

 033
Commentator's name and e-mail address: Dennis McCarthy - Dennis_McCarthy@onesource.com 
Date comment submitted: 2003-05-07
Comment Abstract: The spec does not explicitly address the manner and effect of the use of the XML Schema construct "nillable" in taxonomy elements. Various opinions have been expressed about whether to mandate its  use. This comment seeks to have all aspects surrounding this construct addressed in the spec. 
Comment Detail: Re- Nillable-
Editor Responsible: Hugh Wallis - hugh_wallis@hyperion.com
Other related comments (if any)
Comment State Comment under discussion by appropriate WG
Back to Index

 

Comment Number:

 034
Commentator's name and e-mail address:

Hugh Wallis - hugh_wallis@hyperion.com
 Walter Hamscher - walter@hamscher.com
 David vun Kannon - dvunkannon@hotmail.com  

Date comment submitted: 2003-05-08
Comment Abstract: Clarify the normative status and location of provided schemas
Comment Detail: COMMENT- was - DISCUSSION- Schema locations
Editor Responsible: Hugh Wallis - hugh_wallis@hyperion.com
Other related comments (if any)
Comment State Comment under discussion by appropriate WG
Back to Index

 

Comment Number:

 035
Commentator's name and e-mail address: Don Dwiggins - Don.Dwiggins@ubmatrix.com 
Walter Hamscher - walter@hamscher.com
Date comment submitted: 2003-05-15
Comment Abstract: The spec needs to permit some cyclic item-summation arcs which are currently prohibited
Comment Detail: COMMENT- some cycles in the item-summation arcs may be permissible

Additional related point made by Walter Hamscher in private e-mail:

"A new calculation arcrole, base-self, is needed.  Directed and undirected cycles are legal when the relativeContext attribute ensures that the base and target contexts are in non-overlapping periods."
Editor Responsible: Walter Hamscher - walter@hamscher.com
Other related comments (if any)
Comment State Assigned to an editor – proposed resolution pending
Back to Index

 

Comment Number:

 036
Commentator's name and e-mail address: Hugh Wallis - hugh_wallis@hyperion.com
Date comment submitted: 2003-05-21
Comment Abstract: Change 4.5 to correct restrictions on derivations from tupleType
Comment Detail: The wording of 4.5 should be changed to read "To be in the substitution group of tuple, a tuple element must have a type that is derived from tupleType.  The type tupleType is final with respect to extension, so that and all tuples MUST be derived only by restriction directly from tupleType (not by restriction from any type derived from tupleType)"
Editor Responsible: Hugh Wallis - hugh_wallis@hyperion.com
Other related comments (if any)
Comment State Comment under discussion by appropriate WG
Back to Index

 

Comment Number:

 037
Commentator's name and e-mail address: Tom Egan - tegan@deloitte.com 
Date comment submitted:
Comment Abstract: Incorrect text in definition of the monthYear type periodConstraint element (sec 5.5.6.5.4)
Comment Detail: endDateConstraint should be on year and month only (no day component)
Editor Responsible: Hugh Wallis - hugh_wallis@hyperion.com
Other related comments (if any)
Comment State Minor comment, resolution of which does not require explicit approval of a WG – resolution complete.
Proposed Resolution: last row of table in sec 5.5.6.5.4 should read:

monthYear (list)

month and year component both EQ a member of the list

both month and year 
dateTime components of startDate EQ a member of the list

n/a; any period matches

both month and year
dateTime components of endDate EQ a member of the list

Either:
Date of approval of resolution by the Spec Working Group
Date of approval of resolution by the Domain Working Group
Or:
Notice that approval not required
Not required
Date commentator notified of resolution:
Commentator's response to resolution (if any)
Back to Index

 

Comment Number:

 038
Commentator's name and e-mail address: Don Bruey - dbruey@CreativeSolutions.com 
Date comment submitted: 2003-05-22
Comment Abstract: Section 5.5.7.10.2 - Why is priority an integer, when order is a decimal? Why not make priority a decimal for the same reason as the spec says order is one - for inserting values
Comment Detail: COMMENT- from Don Bruey - Shouldn't priority be decimal just like or
Editor Responsible: Hugh Wallis - hugh_wallis@hyperion.com
Other related comments (if any)
Comment State Comment under discussion by appropriate WG
Back to Index

 

Comment Number:

 039
Commentator's name and e-mail address: Hugh Wallis - hugh_wallis@hyperion.com
Date comment submitted: 2003-05-29
Comment Abstract: In 5.5.7.15 there are no rules that enable the inference of the values of alias concepts from known or inferred values of their associated essence concept.
Comment Detail: COMMENT- Inference of values of alias concepts not possible
Editor Responsible: Hugh Wallis - hugh_wallis@hyperion.com
Other related comments (if any)
Comment State Assigned to an editor – proposed resolution pending
Back to Index

 

Comment Number:

 040
Commentator's name and e-mail address: Hugh Wallis - hugh_wallis@hyperion.com
Date comment submitted: 2003-05-29
Comment Abstract: Although the xbrli:shares and xbrli:pure types have been provided for use as the units of items with sharesItemType and pureItemType there is no requirement or guidance given in this regard. 
Comment Detail: COMMENT- Units in numericContexts for sharesItemType and pureItemTyp
Editor Responsible: Phillip Engel - phillipengel@kpmg.com
Other related comments (if any) 027
Comment State Comment under discussion by appropriate WG
Back to Index

 

Comment Number:

 041
Commentator's name and e-mail address: David vun Kannon - dvunkannon@hotmail.com  
Date comment submitted: 2003-05-28
Comment Abstract: The scope of application of use="required" arcs on a definitionArc having the whole-part or part-whole arcrole is insufficiently defined in 5.5.7.10.1
Comment Detail: COMMENT- scope of use="required" - was Re- [XBRL-SpecV2] Can a taxon

In addition to the general issue raised in the referenced e-mail the wording should be tightened up - contexts should probably be "s-equal" not "same" - also the spec leaves open the semantics of use="required" on arcs with other arcroles
Editor Responsible: Hugh Wallis - hugh_wallis@hyperion.com
Other related comments (if any)
Comment State Comment under discussion by appropriate WG
Back to Index

 

Comment Number:

 042
Commentator's name and e-mail address: Bill Palmer - palmer@execpc.com 
Date comment submitted: 2003-05-31
Comment Abstract: Propose simplification of relativeContext constructs
Comment Detail: Re- COMMENT-simplistic "relative context"
Editor Responsible: Hugh Wallis - hugh_wallis@hyperion.com
Other related comments (if any) 031, 048
Comment State Assigned to an editor – proposed resolution pending
Back to Index

 

Comment Number:

 043
Commentator's name and e-mail address: Frank Lippold - frank.lippold@datev.de  
Date comment submitted: 2003-05-21 (in face to face meeting in Amsterdam)
Comment Abstract: The specification needs to be more specific about the ambiguity when converting parent-child roles from 2.0 to 2.1 definition arcs.
Comment Detail: Re- Questions on linkbases
Editor Responsible: Hugh Wallis - hugh_wallis@hyperion.com
Other related comments (if any)
Comment State Comment under discussion by appropriate WG
Back to Index

 

Comment Number:

 044
Commentator's name and e-mail address: Hugh Wallis - hugh_wallis@hyperion.com
Date comment submitted: 2003-05-31
Comment Abstract: The text of the specification is inconsistent as to whether it refers to "arc role" or "arcrole". The XLink spec uses "arc role" in the one place where the term is used in the same way in the text (http://www.w3.org/TR/xlink/index.html#xlg). I think we should do the same thing
Comment Detail: COMMENT- "arc role" or "arcrole"
Editor Responsible: Hugh Wallis - hugh_wallis@hyperion.com
Other related comments (if any)
Comment State Comment under discussion by appropriate WG
Back to Index

 

Comment Number:

 045
Commentator's name and e-mail address: Geoff Shuetrim - gshuetrim@kpmg.com.au
Date comment submitted: 2003-05-31
Comment Abstract: The definitions of concrete and abstract element in Table 1 should be tighter, referring to the relevant parts of the XML Schema specification
Comment Detail: The definitions of concrete and abstract element in Table 1 should be tighter, referring to the relevant parts of the XML Schema specification
Editor Responsible: Hugh Wallis - hugh_wallis@hyperion.com
Other related comments (if any)
Comment State Minor comment, resolution of which does not require explicit approval of a WG – resolution complete.
Proposed Resolution: Change the definitions of abstract and concrete element in Table 1 as follows:

abstract element

An element for which the attribute abstract in its XML schema declaration has the value "true" and which, therefore, cannot be used in an XBRL instance.  Instead, concrete elements that substitute for abstract elements must be used.

concrete element

An element for which the attribute abstract in its XML schema declaration has the value "false" and which, therefore, may appear in an XML instance.

Either:
Date of approval of resolution by the Spec Working Group
Date of approval of resolution by the Domain Working Group
Or:
Notice that approval not required
Not required
Date commentator notified of resolution: 2003-05-31
Commentator's response to resolution (if any)
Back to Index

 

Comment Number:

 046
Commentator's name and e-mail address: Geoff Shuetrim - gshuetrim@kpmg.com.au
Date comment submitted: 2003-05-31
Comment Abstract: Review the definition of CWA because an assertion of CWA is only true in the context of a specific set of possible calculations. Add new calculations and the assertion needs to be reviewed.
Comment Detail: COMMENT- Review definition of CWA (from Geoff Shuetrim) and subsequent thread
Editor Responsible: Hugh Wallis - hugh_wallis@hyperion.com
Other related comments (if any)
Comment State Assigned to an editor – proposed resolution pending
Back to Index

 

Comment Number:

 047
Commentator's name and e-mail address: Geoff Shuetrim - gshuetrim@kpmg.com.au
Date comment submitted: 2003-06-02
Comment Abstract: Need to be more specific in 5.5.6.5.3 (what is an "empty portion"?)
Comment Detail: COMMENT- Need to be more specific in 5.5.6.5.3 (from Geoff Shuetrim0
Editor Responsible: Hugh Wallis - hugh_wallis@hyperion.com
Other related comments (if any)
Comment State Assigned to an editor – proposed resolution pending
Back to Index

 

Comment Number:

 048
Commentator's name and e-mail address: Hugh Wallis - hugh_wallis@hyperion.com
Date comment submitted: 2003-06-04
Comment Abstract: Error and potentially ambiguous or unclear wording in 5.5.7.13.1 Calculation scoping within tuples
Comment Detail: COMMENT- Error and potentially ambiguous or unclear wording in 5.5.7
Editor Responsible: Hugh Wallis - hugh_wallis@hyperion.com
Other related comments (if any) 031, 042
Comment State Comment under discussion by appropriate WG
Back to Index

 

Comment Number:

 049
Commentator's name and e-mail address: Masatomo Goto - mg@jp.fujitsu.com 
Date comment submitted: 2003-06-02
Comment Abstract: Eliminate xsi:type in an instance
Comment Detail: COMMENT- eliminate xsi-type in an instance.
Editor Responsible: Hugh Wallis - hugh_wallis@hyperion.com
Other related comments (if any)
Comment State Comment under discussion by appropriate WG
Back to Index

 

Comment Number:

 050
Commentator's name and e-mail address: Campbell Pryde - cpryde@kpmg.com 
Date comment submitted: 2003-05-30
Comment Abstract: Change the Example 23 to use whole-part rather than container-content
Comment Detail: Re- Tuple Specialization and Inheritance
Editor Responsible: Hugh Wallis - hugh_wallis@hyperion.com
Other related comments (if any)
Comment State Assigned to an editor – proposed resolution pending
Back to Index

 

Comment Number:

 051
Commentator's name and e-mail address: Hugh Wallis - hugh_wallis@hyperion.com
Date comment submitted: 2003-06-09
Comment Abstract: 4.4.2 specifies illegal syntax (T24:00:00) when defining the interpretation of endDate
Comment Detail: COMMENT- Correct interpretation of endDate (T24-00-00 is illegal syn
Editor Responsible: Hugh Wallis - hugh_wallis@hyperion.com
Other related comments (if any)
Comment State Comment under discussion by appropriate WG
Back to Index

 

Comment Number:

 052
Commentator's name and e-mail address: Hugh Wallis - hugh_wallis@hyperion.com
Date comment submitted: 2003-06-09
Comment Abstract: Example 54 (numbering from 2003-05-16 draft) in section 5.5.7.12 is incorrect - the instant in context "ni1" should be 2001-04-01 because of the date interpretation rules in 4.4.2
Comment Detail: COMMENT- Example 54 in 5.5.7.12 is incorrect - was Re- [XBRL-SpecV2]
Editor Responsible: Hugh Wallis - hugh_wallis@hyperion.com
Other related comments (if any)
Comment State Comment under discussion by appropriate WG
Back to Index

 

Comment Number:

 053
Commentator's name and e-mail address: Bill Palmer - palmer@execpc.com 
Date comment submitted: 2003-06-06
Comment Abstract: Suggest emphasizing the aggregate or primary part of arcrole names by capitalization (e.g. WHOLE-part and part-WHOLE)
Comment Detail: COMMENT- capitalize SUMMATION, WHOLE, etc.
Editor Responsible: Hugh Wallis - hugh_wallis@hyperion.com
Other related comments (if any)
Comment State Assigned to an editor – proposed resolution pending
Back to Index

 

Comment Number:

 054
Commentator's name and e-mail address: Hugh Wallis - hugh_wallis@hyperion.com
Date comment submitted: 2003-06-09
Comment Abstract: It is not explicit that the value of an element at the "item" end of an "item-summation" type arc cannot be inferred. i.e. you MUST NOT infer the value of B from the known values of A and C in the equation A + B = C unless B is at the summation end of one of the arcs that define this equation.
Comment Detail: COMMENT- Make explicit that "item" values can NOT be inferred from "
Editor Responsible: Hugh Wallis - hugh_wallis@hyperion.com
Other related comments (if any)
Comment State Comment under discussion by appropriate WG
Back to Index

 

Comment Number:

 055
Commentator's name and e-mail address: Charles Hoffman - CharlesHoffman@olywa.net
Date comment submitted: 2003-06-09
Comment Abstract: Table 9, page 58, “Standard label role attribute values" - positiveTerseLabel appears twice - second one should be negativeTerseLabel
Comment Detail: COMMENT- Error in Table 9, page 58 - Standard label role attribute
Editor Responsible: Hugh Wallis - hugh_wallis@hyperion.com
Other related comments (if any)
Comment State Minor comment, resolution of which does not require explicit approval of a WG – resolution complete.
Proposed Resolution: Change second appearance of http://www.xbrl.org/2003/role#positiveTerseLabel in Table 9 to read http://www.xbrl.org/2003/role#negativeTerseLabel
Either:
Date of approval of resolution by the Spec Working Group
Date of approval of resolution by the Domain Working Group
Or:
Notice that approval not required
Not required
Date commentator notified of resolution: 2003-06-09
Commentator's response to resolution (if any)
Back to Index

 

End of Document