Pre-CR review - Section 4 comments

Section 4

* "Both algorithms are euqivalent..." - "equivalent" is mis-spelled

Section 4.3

* My last call comment on this still stands: Doesn't this definition of a
mandatory error contradict our stated intent of: if data values fall
outside of the intersection of SQL data types and XSD data types then the
behavior is undefined (but throwing an error is not required)? I don't
remember seeing a place in the spec that captures our intent regarding the
intersection of SQL and XSD data types.

-David