*** previous/match-filters.xml	2008-09-28 14:59:48.000000000 +1000
--- current/match-filters.xml	2008-11-17 11:46:20.000000000 +1100
***************
*** 292,297 ****
--- 292,331 ----
          
        </section>
  
+       <section id="sec-dimension-matching-filter">
+         <head>Dimension matching filter</head>
+ 
+         <p>
+           <definition id="term-dimension-matching-filter" term="dimension matching filter">
+           A <term>dimension matching filter</term> is declared by a <elt>mf:matchDimension</elt>
+           element.</definition>
+         </p>
+ 
+         <p>
+           The syntax for the
+           <xmlref ref="xml-match-dimension-filter"><elt>mf:matchDimension</elt></xmlref>
+           element is defined by the normative schema supplied with this specification.
+         </p>
+ 
+         <p>
+           The dimension matching filter can be used to select facts that have
+           the same value for a specified XBRL Dimension <bibref ref="DIMENSIONS"/>.
+         </p>
+ 
+         <p>
+           This filter can 
+           <xtermref bibref="VARIABLES" idref="term-covers-an-aspect">cover</xtermref> a
+           <xtermref bibref="VARIABLES" idref="term-dimension-aspect">dimension aspect</xtermref>.
+         </p>
+         
+         <p>
+           The QName of the dimension in the XPath expression implied by a 
+           dimension matching filter is given by the 
+           <att>dimension</att> attribute on the dimension matching filter.
+         </p>
+ 
+       </section>
+ 
        <section id="sec-complete-segment-matching-filter">
          <head>Complete-segment matching filter</head>
  
***************
*** 350,390 ****
          
        </section>
        
-       <section id="sec-segment-dimension-matching-filter">
-         <head>Segment-dimension matching filter</head>
- 
-         <p>
-           <definition id="term-segment-dimension-matching-filter" term="segment-dimension matching filter">
-           A <term>segment-dimension matching filter</term> is declared by a <elt>mf:matchSegmentDimension</elt>
-           element.</definition>
-         </p>
- 
-         <p>
-           The syntax for the
-           <xmlref ref="xml-match-segment-dimension-filter"><elt>mf:matchSegmentDimension</elt></xmlref>
-           element is defined by the normative schema supplied with this specification.
-         </p>
- 
-         <p>
-           The segment-dimension matching filter can be used to select facts that have
-           the same value for a specified XBRL Dimension <bibref ref="DIMENSIONS"/> 
-           in their segment.
-         </p>
- 
-         <p>
-           This filter can 
-           <xtermref bibref="VARIABLES" idref="term-covers-an-aspect">cover</xtermref> a
-           <xtermref bibref="VARIABLES" idref="term-segment-dimension-aspect">segment-dimension aspect</xtermref>.
-         </p>
-         
-         <p>
-           The QName of the dimension in the XPath expression implied by a 
-           segment-dimension matching filter is given by the 
-           <att>dimension</att> attribute on the segment-dimension matching filter.
-         </p>
- 
-       </section>
-       
        <section id="sec-complete-scenario-matching-filter">
          <head>Complete-scenario matching filter</head>
  
--- 384,389 ----
***************
*** 443,483 ****
  
        </section>
        
-       <section id="sec-scenario-dimension-matching-filter">
-         <head>Scenario-dimension matching filter</head>
- 
-         <p>
-           <definition id="term-scenario-dimension-matching-filter" term="scenario-dimension matching filter">
-           A <term>scenario-dimension matching filter</term> is declared by a <elt>mf:matchScenarioDimension</elt>
-           element.</definition>
-         </p>
- 
-         <p>
-           The syntax for the
-           <xmlref ref="xml-match-scenario-dimension-filter"><elt>mf:matchScenarioDimension</elt></xmlref>
-           element is defined by the normative schema supplied with this specification.
-         </p>
- 
-         <p>
-           The scenario-dimension matching filter can be used to select facts that have
-           the same value for a specified XBRL Dimension <bibref ref="DIMENSIONS"/> 
-           in their scenario.
-         </p>
- 
-         <p>
-           This filter can 
-           <xtermref bibref="VARIABLES" idref="term-covers-an-aspect">cover</xtermref> a
-           <xtermref bibref="VARIABLES" idref="term-scenario-dimension-aspect">scenario dimension aspect</xtermref>.
-         </p>
-         
-         <p>
-           The QName of the dimension in the XPath expression implied by a 
-           scenario-dimension matching filter is given by the 
-           <att>dimension</att> attribute on the scenario-dimension matching filter.
-         </p>
-         
-       </section>
-       
      </section><!-- Syntax -->
          
    </body>
--- 442,447 ----
***************
*** 555,562 ****
            </p>
          </revision>
  
!         <revision ref="person-geoff" 
!         day="31" month="01" year="2008">
            <p>
              Standardised the format of the hyperlinks to the normative schema.
            </p>
--- 519,525 ----
            </p>
          </revision>
  
!         <revision ref="person-geoff" day="31" month="01" year="2008">
            <p>
              Standardised the format of the hyperlinks to the normative schema.
            </p>
***************
*** 566,573 ****
            </p>
          </revision>
          
!         <revision ref="person-geoff" 
!         day="01" month="02" year="2008">
            <p>
              Fixed the implied XPath expression for the match filter covering the concept
              aspect as suggested by <personref ref="person-goto"/>. The arguments to the functions
--- 529,535 ----
            </p>
          </revision>
          
!         <revision ref="person-geoff" day="01" month="02" year="2008">
            <p>
              Fixed the implied XPath expression for the match filter covering the concept
              aspect as suggested by <personref ref="person-goto"/>. The arguments to the functions
***************
*** 575,588 ****
            </p>
          </revision>
          
!         <revision ref="person-geoff" 
!         day="13" month="03" year="2008">
            <p>
              Changed period to unit in the explanation of the unit matching filter as 
              suggested by CompSci Resources.
            </p>
          </revision>
  
        </revisions>
  
      </section>
--- 537,565 ----
            </p>
          </revision>
          
!         <revision ref="person-geoff" day="13" month="03" year="2008">
            <p>
              Changed period to unit in the explanation of the unit matching filter as 
              suggested by CompSci Resources.
            </p>
          </revision>
  
+         <revision ref="person-geoff" day="27" month="08" year="2008">
+           <p>
+             Collapsed the segment dimension and scenario dimension
+             aspects into the one dimension aspect in line with changes
+             to the dimensional aspect model.
+           </p>
+         </revision>
+ 
+         <revision ref="person-geoff" day="17" month="11" year="2008">
+           <p>
+             Made the <att>variable</att> attribute have type <code>variable:QName</code>
+             because it contains variable name QNames that do not resolve according to the
+             rules used for QNames with data type xs:QName. This change was suggested by 
+             <personref ref="person-herm"/>.
+           </p>
+         </revision>
        </revisions>
  
      </section>
