*** previous/dimension-filters.xml	2008-03-12 10:59:14.000000000 +0100
--- current/dimension-filters.xml	2008-02-27 11:44:33.000000000 +0100
***************
*** 63,74 ****
        </p>
  
        <p>
!         All of the filters defined in this specification have a <elt>df:dimension</elt> element.
          <definition id="term-filter-dimension" term="filter dimension">
!           The <term>filter dimension</term> is the dimension that is being filtered by a filter.
!           This dimension is identified by the <elt>df:dimension</elt> child element of the filter.
          </definition>
        </p>
  
        <section id="sec-background">
          <head>Background</head>
--- 63,94 ----
        </p>
  
        <p>
!         <definition id="term-dimension-filter" term="dimension filter">
!           All of the filters defined in this specification are referred to 
!           collectively as <term>filter dimensions</term>.
!         </definition>
!       </p>
! 
!       <p>
          <definition id="term-filter-dimension" term="filter dimension">
!           The <term>filter dimension</term> is the dimension being filtered by a dimension filter.
!           This dimension is identified by the <elt>df:dimension</elt> child element of the 
!           dimension filter.
          </definition>
        </p>
+       
+       <p>
+         All dimension filters have a <xmlref ref="xml-dimension-model"><elt>df:dimension</elt></xmlref> element.  
+         That element specifies both the filter dimension and whether the filter can cover a   
+         <xtermref bibref="VARIABLES" idref="term-segment-dimension-aspect">segment dimension aspect</xtermref> or
+         <xtermref bibref="VARIABLES" idref="term-segment-dimension-aspect">scenario dimension aspect</xtermref>.
+         If the <elt>df:dimension</elt> element contains a <att>contextElement</att> attribute equal to
+         <val>segment</val> then the dimension filter can cover the segment dimension aspect for the dimension
+         identified by the <elt>df:dimension</elt> element.
+         If the <elt>df:dimension</elt> element contains a <att>contextElement</att> attribute equal to
+         <val>scenario</val> then the dimension filter can cover the scenario dimension aspect for the 
+         filter dimension.
+       </p>      
  
        <section id="sec-background">
          <head>Background</head>
***************
*** 131,138 ****
  
          <p>
            <definition id="term-explicit-dimension-filter" term="explicit dimension filter">
!           An <term>explicit dimension filter</term> is declared by a <elt>df:explicitDimension</elt>
!           element.</definition>
          </p>
  
          <p>
--- 151,159 ----
  
          <p>
            <definition id="term-explicit-dimension-filter" term="explicit dimension filter">
!             An <term>explicit dimension filter</term> is declared by 
!             a <elt>df:explicitDimension</elt> element.
!           </definition>
          </p>
  
          <p>
***************
*** 227,245 ****
          <p>
            If the explicit dimension filter has no <termref ref="term-filter-member">filter members</termref>
            then all domain members in the <termref ref="term-recognised-domain-for-a-dimension">recognised domain 
!           for the filter dimension</termref> meet the filter criteria. The implied XPath expression is then:
          </p>
  
!         <p>
!           <code>
!             some $member in xfi:concept-explicit-dimension-values(fn:node-name(.),#dimension,#linkrole), 
!                  $value in xfi:fact-explicit-dimension-value(.,#dimension) 
!             satisfies ($value eq $member)
!           </code>
!         </p>
  
          <p>
!           Otherwise the implied XPath expression is constructed by combining, using the
            XPath <code>or</code> operator, a set of terms, one for 
            <termref ref="term-filter-member">filter member</termref> 
            in the explicit dimension filter.
--- 248,291 ----
          <p>
            If the explicit dimension filter has no <termref ref="term-filter-member">filter members</termref>
            then all domain members in the <termref ref="term-recognised-domain-for-a-dimension">recognised domain 
!           for the filter dimension</termref> meet the filter criteria. The implied XPath expression is then 
!           that specified in the following table.  It depends upon the value of the 
!           <att>contextElement</att> attribute on the filter's <elt>df:dimension</elt> child element.
          </p>
  
!         <table>
!           <thead>
!             <tr>
!               <th><att>contextElement</att> attribute value</th>
!               <th>Implied XPath expression</th>
!             </tr>
!           </thead>
!           <tbody>
!             <tr>
!               <td><val>segment</val></td>
!               <td>
!                 <code>
!                 some $member in xfi:concept-explicit-segment-dimension-values(fn:node-name(.),#dimension,#linkrole), 
!                      $value in xfi:fact-explicit-segment-dimension-value(.,#dimension) 
!                 satisfies ($value eq $member)
!                 </code>
!               </td>
!             </tr>
!             <tr>
!               <td><val>scenario</val></td>
!               <td>
!                 <code>
!                 some $member in xfi:concept-explicit-scenario-dimension-values(fn:node-name(.),#dimension,#linkrole), 
!                      $value in xfi:fact-explicit-scenario-dimension-value(.,#dimension) 
!                 satisfies ($value eq $member)
!                 </code>
!               </td>
!             </tr>
!           </tbody>
!         </table>
  
          <p>
!           Otherwise the implied XPath expression is constructed by combining, using the 
            XPath <code>or</code> operator, a set of terms, one for 
            <termref ref="term-filter-member">filter member</termref> 
            in the explicit dimension filter.
***************
*** 311,326 ****
          </p>
  
          <p>
!           The term in the implied XPath expression, for each filter member is:
          </p>
  
!         <p>
!           <code>
!             some  $member in xfi:concept-select-explicit-dimension-values(fn:node-name(),#dimension,#linkrole,#member,#axis),
!                   $value  in xfi:fact-explicit-dimension-value(.,#dimension) 
!             satisfies ($value eq $member)
!           </code>
!         </p>
  
          <p>
            where <val>#axis</val> is equal to the value of the <att>axis</att> attribute on the filter member.
--- 357,397 ----
          </p>
  
          <p>
!           The term in the implied XPath expression, for each filter member is given in the table below.  It 
!           depends upon the value of the <att>contextElement</att> attribute
!           on the filter's <elt>df:dimension</elt> child element.
          </p>
  
!         <table>
!           <thead>
!             <tr>
!               <th><att>contextElement</att> attribute value</th>
!               <th>Implied XPath expression</th>
!             </tr>
!           </thead>
!           <tbody>
!             <tr>
!               <td><val>segment</val></td>
!               <td>
!                 <code>
!                 some  $member in xfi:concept-select-explicit-segment-dimension-values(fn:node-name(),#dimension,#linkrole,#member,#axis),
!                       $value  in xfi:fact-explicit-segment-dimension-value(.,#dimension) 
!                 satisfies ($value eq $member)
!                 </code>
!               </td>
!             </tr>
!             <tr>
!               <td><val>scenario</val></td>
!               <td>
!                 <code>
!                 some  $member in xfi:concept-select-explicit-scenario-dimension-values(fn:node-name(),#dimension,#linkrole,#member,#axis),
!                       $value  in xfi:fact-explicit-scenario-dimension-value(.,#dimension) 
!                 satisfies ($value eq $member)
!                 </code>
!               </td>
!             </tr>
!           </tbody>
!         </table>
  
          <p>
            where <val>#axis</val> is equal to the value of the <att>axis</att> attribute on the filter member.
***************
*** 332,337 ****
--- 403,409 ----
                <thead>
                  <tr>
                    <th>Filter dimension</th>
+                   <th>Context element</th>
                    <th>
                      Filter member
                      <footnote>
***************
*** 350,355 ****
--- 422,430 ----
                      <val>eg:region</val>
                    </td>
                    <td>
+                     <val>segment</val>
+                   </td>
+                   <td>
                      None
                    </td>
                    <td>
***************
*** 365,370 ****
--- 440,448 ----
                      <val>eg:region</val>
                    </td>
                    <td>
+                     <val>segment</val>
+                   </td>
+                   <td>
                      <val>eg:australasia</val>
                    </td>
                    <td>
***************
*** 381,386 ****
--- 459,467 ----
                      <val>eg:region</val>
                    </td>
                    <td>
+                     <val>segment</val>
+                   </td>
+                   <td>
                      <val>eg:australasia</val>
                    </td>
                    <td>
***************
*** 399,404 ****
--- 480,488 ----
                      <val>eg:region</val>
                    </td>
                    <td>
+                     <val>segment</val>
+                   </td>
+                   <td>
                      <val>eg:australasia</val>
                    </td>
                    <td>
***************
*** 416,421 ****
--- 500,508 ----
                      <val>eg:region</val>
                    </td>
                    <td>
+                     <val>segment</val>
+                   </td>
+                   <td>
                      <val>eg:australasia</val>
                    </td>
                    <td>
***************
*** 457,468 ****
          <p>
            If the typed dimension filter does not contain a 
            <att>test</att> attribute, then its implied XPath 
!           expression is:
          </p>
  
!         <p>
!           <code>xfi:concept-has-dimension(fn:node-name(.),#dimension)</code>
!         </p>
  
          <p>
            where <val>#dimension</val> is determined as specified 
--- 544,581 ----
          <p>
            If the typed dimension filter does not contain a 
            <att>test</att> attribute, then its implied XPath 
!           expression is specified in the following table.  
!           It depends upon the value of the 
!           <att>contextElement</att> attribute on the 
!           filter's <elt>df:dimension</elt> child element.
          </p>
  
!         <table>
!           <thead>
!             <tr>
!               <th><att>contextElement</att> attribute value</th>
!               <th>Implied XPath expression</th>
!             </tr>
!           </thead>
!           <tbody>
!             <tr>
!               <td><val>segment</val></td>
!               <td>
!                 <code>
!                 xfi:concept-has-segment-dimension(fn:node-name(.),#dimension)
!                 </code>
!               </td>
!             </tr>
!             <tr>
!               <td><val>scenario</val></td>
!               <td>
!                 <code>
!                 xfi:concept-has-scenario-dimension(fn:node-name(.),#dimension)
!                 </code>
!               </td>
!             </tr>
!           </tbody>
!         </table>
  
          <p>
            where <val>#dimension</val> is determined as specified 
***************
*** 472,486 ****
          <p>
            If the typed dimension filter does contain a 
            <att>test</att> attribute, then its implied XPath 
!           expression is:
          </p>
  
!         <p>
!           <code>
!           xfi:concept-has-dimension(fn:node-name(.),#dimension) and 
!           xfi:dimension-value(.,#dimension)[#test]
!           </code>
!         </p>
  
          <p>
            where <val>#dimension</val> is determined as specified 
--- 585,624 ----
          <p>
            If the typed dimension filter does contain a 
            <att>test</att> attribute, then its implied XPath 
!           expression is given in the table below.
!           It depends upon the value of the 
!           <att>contextElement</att> attribute on the 
!           filter's <elt>df:dimension</elt> child element.
          </p>
  
!         <table>
!           <thead>
!             <tr>
!               <th><att>contextElement</att> attribute value</th>
!               <th>Implied XPath expression</th>
!             </tr>
!           </thead>
!           <tbody>
!             <tr>
!               <td><val>segment</val></td>
!               <td>
!                 <code>
!                 xfi:concept-has-segment-dimension(fn:node-name(.),#dimension) and 
!                 xfi:fact-typed-segment-dimension-value(.,#dimension)[#test]
!                 </code>
!               </td>
!             </tr>
!             <tr>
!               <td><val>scenario</val></td>
!               <td>
!                 <code>
!                 xfi:concept-has-scenario-dimension(fn:node-name(.),#dimension) and 
!                 xfi:fact-typed-scenario-dimension-value(.,#dimension)[#test]
!                 </code>
!               </td>
!             </tr>
!           </tbody>
!         </table>
  
          <p>
            where <val>#dimension</val> is determined as specified 
***************
*** 514,519 ****
--- 652,658 ----
                <thead>
                  <tr>
                    <th>Dimension QName</th>
+                   <th>Context element</th>
                    <th><att>test</att></th>
                    <th>Selection criteria</th>
                  </tr>
***************
*** 524,529 ****
--- 663,671 ----
                      <val>eg:altitude</val>
                    </td>
                    <td>
+                     <val>segment</val>
+                   </td>
+                   <td>
                      <val>xs:boolean('true')</val>
                    </td>
                    <td>
***************
*** 536,541 ****
--- 678,686 ----
                      <val>eg:altitude</val>
                    </td>
                    <td>
+                     <val>segment</val>
+                   </td>
+                   <td>
                      <val>eg:height &gt; 0</val>
                    </td>
                    <td>
***************
*** 867,872 ****
--- 1012,1040 ----
            </p>
          </revision>
  
+         <revision ref="person-geoff" 
+         day="25" month="02" year="2008">
+           <p>
+             Restored the sentence to the introduction of the specification
+             defining which aspects can be covered by explicit and typed dimension
+             filters.  This drafting regression, introduced on 23 January 2008, was 
+             identified by <personref ref="person-herm"/>.
+           </p>
+         </revision>
+ 
+         <revision ref="person-geoff" 
+         day="27" month="02" year="2008">
+           <p>
+             Added a <att>contextElement</att> attribute to the dimension filters to 
+             simplify the determination of whether a given filter can cover a segment dimension
+             aspect or a scenario dimension aspect.  The aspect covering properties of a filter
+             no longer dependent upon the facts being filtered.  This dependency could have caused 
+             problems when using the filter with variables that bind as sequences.
+             This modification has also required changing the function calls in the implied 
+             XPath expressions for the various filters.
+           </p>
+         </revision>
+ 
        </revisions>
  
      </section>
*** previous/dimension-filters.xml	2008-03-12 10:59:14.000000000 +0100
--- current/dimension-filters.xml	2008-03-20 20:55:00.000000000 +0100
***************
*** 41,47 ****
        <p>
          The filters defined in this specification facilitate selection
          of facts based on dimension information in both the 
!         <xtermref bibref="VARIABLES" idref="term-target-instance">target XBRL instance</xtermref> 
          and in its supporting DTS. Both 
          <xtermref bibref="DIMENSIONS" idref="_2.5.2">typed</xtermref> 
          and 
--- 41,47 ----
        <p>
          The filters defined in this specification facilitate selection
          of facts based on dimension information in both the 
!         <xtermref bibref="VARIABLES" idref="term-target-xbrl-instance">target XBRL instance</xtermref> 
          and in its supporting DTS. Both 
          <xtermref bibref="DIMENSIONS" idref="_2.5.2">typed</xtermref> 
          and 
***************
*** 63,74 ****
        </p>
  
        <p>
!         All of the filters defined in this specification have a <elt>df:dimension</elt> element.
          <definition id="term-filter-dimension" term="filter dimension">
!           The <term>filter dimension</term> is the dimension that is being filtered by a filter.
!           This dimension is identified by the <elt>df:dimension</elt> child element of the filter.
          </definition>
        </p>
  
        <section id="sec-background">
          <head>Background</head>
--- 63,94 ----
        </p>
  
        <p>
!         <definition id="term-dimension-filter" term="dimension filter">
!           All of the filters defined in this specification are referred to 
!           collectively as <term>filter dimensions</term>.
!         </definition>
!       </p>
! 
!       <p>
          <definition id="term-filter-dimension" term="filter dimension">
!           The <term>filter dimension</term> is the dimension being filtered by a dimension filter.
!           This dimension is identified by the <elt>df:dimension</elt> child element of the 
!           dimension filter.
          </definition>
        </p>
+       
+       <p>
+         All dimension filters have a <xmlref ref="xml-dimension-model"><elt>df:dimension</elt></xmlref> element.  
+         That element specifies both the filter dimension and whether the filter can cover a   
+         <xtermref bibref="VARIABLES" idref="term-segment-dimension-aspect">segment dimension aspect</xtermref> or
+         <xtermref bibref="VARIABLES" idref="term-segment-dimension-aspect">scenario dimension aspect</xtermref>.
+         If the <elt>df:dimension</elt> element contains a <att>contextElement</att> attribute equal to
+         <val>segment</val> then the dimension filter can cover the segment dimension aspect for the dimension
+         identified by the <elt>df:dimension</elt> element.
+         If the <elt>df:dimension</elt> element contains a <att>contextElement</att> attribute equal to
+         <val>scenario</val> then the dimension filter can cover the scenario dimension aspect for the 
+         filter dimension.
+       </p>      
  
        <section id="sec-background">
          <head>Background</head>
***************
*** 131,138 ****
  
          <p>
            <definition id="term-explicit-dimension-filter" term="explicit dimension filter">
!           An <term>explicit dimension filter</term> is declared by a <elt>df:explicitDimension</elt>
!           element.</definition>
          </p>
  
          <p>
--- 151,159 ----
  
          <p>
            <definition id="term-explicit-dimension-filter" term="explicit dimension filter">
!             An <term>explicit dimension filter</term> is declared by 
!             a <elt>df:explicitDimension</elt> element.
!           </definition>
          </p>
  
          <p>
***************
*** 227,245 ****
          <p>
            If the explicit dimension filter has no <termref ref="term-filter-member">filter members</termref>
            then all domain members in the <termref ref="term-recognised-domain-for-a-dimension">recognised domain 
!           for the filter dimension</termref> meet the filter criteria. The implied XPath expression is then:
          </p>
  
!         <p>
!           <code>
!             some $member in xfi:concept-explicit-dimension-values(fn:node-name(.),#dimension,#linkrole), 
!                  $value in xfi:fact-explicit-dimension-value(.,#dimension) 
!             satisfies ($value eq $member)
!           </code>
!         </p>
  
          <p>
!           Otherwise the implied XPath expression is constructed by combining, using the
            XPath <code>or</code> operator, a set of terms, one for 
            <termref ref="term-filter-member">filter member</termref> 
            in the explicit dimension filter.
--- 248,291 ----
          <p>
            If the explicit dimension filter has no <termref ref="term-filter-member">filter members</termref>
            then all domain members in the <termref ref="term-recognised-domain-for-a-dimension">recognised domain 
!           for the filter dimension</termref> meet the filter criteria. The implied XPath expression is then 
!           that specified in the following table.  It depends upon the value of the 
!           <att>contextElement</att> attribute on the filter's <elt>df:dimension</elt> child element.
          </p>
  
!         <table>
!           <thead>
!             <tr>
!               <th><att>contextElement</att> attribute value</th>
!               <th>Implied XPath expression</th>
!             </tr>
!           </thead>
!           <tbody>
!             <tr>
!               <td><val>segment</val></td>
!               <td>
!                 <code>
!                 some $member in xfi:concept-explicit-segment-dimension-values(fn:node-name(.),#dimension,#linkrole), 
!                      $value in xfi:fact-explicit-segment-dimension-value(.,#dimension) 
!                 satisfies ($value eq $member)
!                 </code>
!               </td>
!             </tr>
!             <tr>
!               <td><val>scenario</val></td>
!               <td>
!                 <code>
!                 some $member in xfi:concept-explicit-scenario-dimension-values(fn:node-name(.),#dimension,#linkrole), 
!                      $value in xfi:fact-explicit-scenario-dimension-value(.,#dimension) 
!                 satisfies ($value eq $member)
!                 </code>
!               </td>
!             </tr>
!           </tbody>
!         </table>
  
          <p>
!           Otherwise the implied XPath expression is constructed by combining, using the 
            XPath <code>or</code> operator, a set of terms, one for 
            <termref ref="term-filter-member">filter member</termref> 
            in the explicit dimension filter.
***************
*** 311,326 ****
          </p>
  
          <p>
!           The term in the implied XPath expression, for each filter member is:
          </p>
  
!         <p>
!           <code>
!             some  $member in xfi:concept-select-explicit-dimension-values(fn:node-name(),#dimension,#linkrole,#member,#axis),
!                   $value  in xfi:fact-explicit-dimension-value(.,#dimension) 
!             satisfies ($value eq $member)
!           </code>
!         </p>
  
          <p>
            where <val>#axis</val> is equal to the value of the <att>axis</att> attribute on the filter member.
--- 357,397 ----
          </p>
  
          <p>
!           The term in the implied XPath expression, for each filter member is given in the table below.  It 
!           depends upon the value of the <att>contextElement</att> attribute
!           on the filter's <elt>df:dimension</elt> child element.
          </p>
  
!         <table>
!           <thead>
!             <tr>
!               <th><att>contextElement</att> attribute value</th>
!               <th>Implied XPath expression</th>
!             </tr>
!           </thead>
!           <tbody>
!             <tr>
!               <td><val>segment</val></td>
!               <td>
!                 <code>
!                 some  $member in xfi:concept-select-explicit-segment-dimension-values(fn:node-name(),#dimension,#linkrole,#member,#axis),
!                       $value  in xfi:fact-explicit-segment-dimension-value(.,#dimension) 
!                 satisfies ($value eq $member)
!                 </code>
!               </td>
!             </tr>
!             <tr>
!               <td><val>scenario</val></td>
!               <td>
!                 <code>
!                 some  $member in xfi:concept-select-explicit-scenario-dimension-values(fn:node-name(),#dimension,#linkrole,#member,#axis),
!                       $value  in xfi:fact-explicit-scenario-dimension-value(.,#dimension) 
!                 satisfies ($value eq $member)
!                 </code>
!               </td>
!             </tr>
!           </tbody>
!         </table>
  
          <p>
            where <val>#axis</val> is equal to the value of the <att>axis</att> attribute on the filter member.
***************
*** 332,337 ****
--- 403,409 ----
                <thead>
                  <tr>
                    <th>Filter dimension</th>
+                   <th>Context element</th>
                    <th>
                      Filter member
                      <footnote>
***************
*** 350,355 ****
--- 422,430 ----
                      <val>eg:region</val>
                    </td>
                    <td>
+                     <val>segment</val>
+                   </td>
+                   <td>
                      None
                    </td>
                    <td>
***************
*** 365,370 ****
--- 440,448 ----
                      <val>eg:region</val>
                    </td>
                    <td>
+                     <val>segment</val>
+                   </td>
+                   <td>
                      <val>eg:australasia</val>
                    </td>
                    <td>
***************
*** 381,386 ****
--- 459,467 ----
                      <val>eg:region</val>
                    </td>
                    <td>
+                     <val>segment</val>
+                   </td>
+                   <td>
                      <val>eg:australasia</val>
                    </td>
                    <td>
***************
*** 399,404 ****
--- 480,488 ----
                      <val>eg:region</val>
                    </td>
                    <td>
+                     <val>segment</val>
+                   </td>
+                   <td>
                      <val>eg:australasia</val>
                    </td>
                    <td>
***************
*** 416,421 ****
--- 500,508 ----
                      <val>eg:region</val>
                    </td>
                    <td>
+                     <val>segment</val>
+                   </td>
+                   <td>
                      <val>eg:australasia</val>
                    </td>
                    <td>
***************
*** 457,468 ****
          <p>
            If the typed dimension filter does not contain a 
            <att>test</att> attribute, then its implied XPath 
!           expression is:
          </p>
  
!         <p>
!           <code>xfi:concept-has-dimension(fn:node-name(.),#dimension)</code>
!         </p>
  
          <p>
            where <val>#dimension</val> is determined as specified 
--- 544,581 ----
          <p>
            If the typed dimension filter does not contain a 
            <att>test</att> attribute, then its implied XPath 
!           expression is specified in the following table.  
!           It depends upon the value of the 
!           <att>contextElement</att> attribute on the 
!           filter's <elt>df:dimension</elt> child element.
          </p>
  
!         <table>
!           <thead>
!             <tr>
!               <th><att>contextElement</att> attribute value</th>
!               <th>Implied XPath expression</th>
!             </tr>
!           </thead>
!           <tbody>
!             <tr>
!               <td><val>segment</val></td>
!               <td>
!                 <code>
!                 xfi:concept-has-segment-dimension(fn:node-name(.),#dimension)
!                 </code>
!               </td>
!             </tr>
!             <tr>
!               <td><val>scenario</val></td>
!               <td>
!                 <code>
!                 xfi:concept-has-scenario-dimension(fn:node-name(.),#dimension)
!                 </code>
!               </td>
!             </tr>
!           </tbody>
!         </table>
  
          <p>
            where <val>#dimension</val> is determined as specified 
***************
*** 472,486 ****
          <p>
            If the typed dimension filter does contain a 
            <att>test</att> attribute, then its implied XPath 
!           expression is:
          </p>
  
!         <p>
!           <code>
!           xfi:concept-has-dimension(fn:node-name(.),#dimension) and 
!           xfi:dimension-value(.,#dimension)[#test]
!           </code>
!         </p>
  
          <p>
            where <val>#dimension</val> is determined as specified 
--- 585,624 ----
          <p>
            If the typed dimension filter does contain a 
            <att>test</att> attribute, then its implied XPath 
!           expression is given in the table below.
!           It depends upon the value of the 
!           <att>contextElement</att> attribute on the 
!           filter's <elt>df:dimension</elt> child element.
          </p>
  
!         <table>
!           <thead>
!             <tr>
!               <th><att>contextElement</att> attribute value</th>
!               <th>Implied XPath expression</th>
!             </tr>
!           </thead>
!           <tbody>
!             <tr>
!               <td><val>segment</val></td>
!               <td>
!                 <code>
!                 xfi:concept-has-segment-dimension(fn:node-name(.),#dimension) and 
!                 xfi:fact-typed-segment-dimension-value(.,#dimension)[#test]
!                 </code>
!               </td>
!             </tr>
!             <tr>
!               <td><val>scenario</val></td>
!               <td>
!                 <code>
!                 xfi:concept-has-scenario-dimension(fn:node-name(.),#dimension) and 
!                 xfi:fact-typed-scenario-dimension-value(.,#dimension)[#test]
!                 </code>
!               </td>
!             </tr>
!           </tbody>
!         </table>
  
          <p>
            where <val>#dimension</val> is determined as specified 
***************
*** 514,519 ****
--- 652,658 ----
                <thead>
                  <tr>
                    <th>Dimension QName</th>
+                   <th>Context element</th>
                    <th><att>test</att></th>
                    <th>Selection criteria</th>
                  </tr>
***************
*** 524,529 ****
--- 663,671 ----
                      <val>eg:altitude</val>
                    </td>
                    <td>
+                     <val>segment</val>
+                   </td>
+                   <td>
                      <val>xs:boolean('true')</val>
                    </td>
                    <td>
***************
*** 536,541 ****
--- 678,686 ----
                      <val>eg:altitude</val>
                    </td>
                    <td>
+                     <val>segment</val>
+                   </td>
+                   <td>
                      <val>eg:height &gt; 0</val>
                    </td>
                    <td>
***************
*** 579,585 ****
            <includeChunk ref="boilerplate/references/XMLNAMES.xml"/>
            <includeChunk ref="boilerplate/references/XMLSCHEMA-STRUCTURES.xml"/>
            <includeChunk ref="boilerplate/references/XBRL.xml"/>
-           <includeChunk ref="boilerplate/references/XBRLFUNCTIONS.xml"/>
            <includeChunk ref="boilerplate/references/VARIABLES.xml"/>
            <includeChunk ref="boilerplate/references/DIMENSIONS.xml"/>
      	</bibliography>
--- 724,729 ----
***************
*** 867,872 ****
--- 1011,1045 ----
            </p>
          </revision>
  
+         <revision ref="person-geoff" 
+         day="25" month="02" year="2008">
+           <p>
+             Restored the sentence to the introduction of the specification
+             defining which aspects can be covered by explicit and typed dimension
+             filters.  This drafting regression, introduced on 23 January 2008, was 
+             identified by <personref ref="person-herm"/>.
+           </p>
+         </revision>
+ 
+         <revision ref="person-geoff" 
+         day="27" month="02" year="2008">
+           <p>
+             Added a <att>contextElement</att> attribute to the dimension filters to 
+             simplify the determination of whether a given filter can cover a segment dimension
+             aspect or a scenario dimension aspect.  The aspect covering properties of a filter
+             no longer dependent upon the facts being filtered.  This dependency could have caused 
+             problems when using the filter with variables that bind as sequences.
+             This modification has also required changing the function calls in the implied 
+             XPath expressions for the various filters.
+           </p>
+         </revision>
+ 
+         <revision ref="person-geoff" day="20" month="03" year="2008">
+           <p>
+             Fixed broken hyperlinks.
+           </p>
+         </revision>
+         
        </revisions>
  
      </section>
