DR 09-0233- SML, core: Shortcoming with ValIso
Shawn Villaron
shawnv at microsoft.com
Fri Jun 5 18:36:58 CEST 2009
Here is my proposed response for this defect report:
DR 09-0233- SML, core: Shortcoming with ValIso
Part 1, §18.3.2.5 will be updated as follows:
Attributes
Description
maxValIso (Max ISO Value)
A maximum value for dynamic filter. maxValIso shall be required for today, yesterday, tomorrow, nextWeek, thisWeek, lastWeek, nextMonth, thisMonth, lastMonth, nextQuarter, thisQuarter, lastQuarter, nextYear, thisYear, lastYear, and yearToDate.
The above criteria are based on a value range; that is, if today's date is September 22nd, then the range for thisWeek is the values greater than or equal to September 17 and less than September 24. In the thisWeek range, the lower value is expressed valIso. The higher value is expressed using maxValIso.
These dynamic filters shall not require valIso or maxValIso:
Q1, Q2, Q3, Q4, M1, M2, M3, M4, M5, M6, M7, M8, M9, M10, M11 and M12.
The above criteria shall not specify the range using valIso and maxValIso because Q1 always starts from M1 to M3, and M1 is always January.
These types of dynamic filters shall use valIso and shall not use maxValIso:
· aboveAverage and belowAverage
The possible values for this attribute are defined by the W3C XML Schema dateTime datatype.
val (Value)
A minimum value for dynamic filter. See description of valIso to understand when val is required.
The possible values for this attribute are defined by the W3C XML Schema double datatype.
valIso (ISO Value)
A minimum value for dynamic filter. (See description of maxValIso to understand when val/valIso is required.)
Only these types of dynamic filters shall use val and shall not use valIso:
· aboveAverage and belowAverage
The possible values for this attribute are defined by the W3C XML Schema dateTime datatype.
Part 4, §10.3.2 will be updated as follows:
10.3.2 Additional attributes for dynamicFilter element (Part 1, §18.3.2.5)
The following additional attributes have modified descriptions when can be specified for a document of a transitional conformance class:
Attributes
Description
maxVal (Max Value)
A maximum value for dynamic filter. maxVal/maxValIso shall be required for today, yesterday, tomorrow, nextWeek, thisWeek, lastWeek, nextMonth, thisMonth, lastMonth, nextQuarter, thisQuarter, lastQuarter, nextYear, thisYear, lastYear, and yearToDate.
The above criteria are based on a value range. [Example: If today's date is September 22nd, then the range for thisWeek is the values greater than or equal to September 17 and less than September 24. end example] In the thisWeek range, the lower value is expressed using val or valIso. The higher value is expressed using maxVal or maxValIso.
These dynamic filter shall not require val/valIso or maxVal/maxValIso:
Q1, Q2, Q3, Q4,
M1, M2, M3, M4, M5, M6, M7, M8, M9, M10, M11 and M12.
The above criteria shall not specify the range using val/valIso and maxVal/maxValIso because Q1 always starts from M1 to M3, and M1 is always January.
These types of dynamic filters shall use val/valIso and shall not use maxVal/maxValIso:
aboveAverage and belowAverage.
If maxValIso and maxVal are both present, maxValIso shall take precedence.
The possible values for this attribute are defined by the W3C XML Schema double datatype.
val (Value)
A minimum value for dynamic filter. See description of valIso to understand when val is required.
If valIso and val are both present, valIso shall take precedence.
The possible values for this attribute are defined by the W3C XML Schema double datatype.
valIso (ISO Value)
A minimum value for dynamic filter. (See description of maxVal/maxValIso to understand when val/valIso is required.)
The possible values for this attribute are defined by the W3C XML Schema dateTime datatype.
Schema changes are needed.
Relax NG changes are needed.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.vse.cz/pipermail/sc34wg4/attachments/20090605/c048d48a/attachment.htm>
More information about the sc34wg4
mailing list