DISCUSSION OF SUBSEQUENT ITEMS

This is a last call comment from Jim Melton (jim.melton@acm.org) on
the Character Model for the World Wide Web 1.0
(http://www.w3.org/TR/2002/WD-charmod-20020430/).

Semi-structured version of the comment:

Submitted by: Jim Melton (jim.melton@acm.org)
Submitted on behalf of (maybe empty): W3C XML Query Working Group
Comment type: other
Chapter/section the comment applies to: 4.4 Responsibility for Normalization
The comment will be visible to: public
Comment title: DISCUSSION OF SUBSEQUENT ITEMS
Comment:


Section 4.4, "Responsibility for Normalization", is the section in which the Query WG is most interested.  Intense discussions have taken place in the past over the subject of when normalization should, should not, must, or must not be performed, and what components of an environment have responsibilities in that area.  Implementers of data repositories that might contain vast quantities of data (e.g., database systems) have expressed particular concerns about this, observing that some applications involve the need to store data very quickly, but retrieve it in a less urgent fashion, while other applications place severe demands on retrieval but have fewer constraints on storing data.  In other words, the demands of users of applications, not a rigid policy, must govern *some* aspects of the decision about when normalization is performed and by whom.






Structured version of  the comment:

<lc-comment
  visibility="public" status="pending"
  decision="pending" impact="pending">
  <originator email="jim.melton@acm.org" represents="W3C XML Query Working Group"
      >Jim Melton</originator>
  <charmod-section href='http://www.w3.org/TR/2002/WD-charmod-20020430/#sec-NormalizationApplication'
    >4.4</charmod-section>
  <title>DISCUSSION OF SUBSEQUENT ITEMS</title>
  <description>
    <comment>
      <dated-link date="2002-05-31"
        >DISCUSSION OF SUBSEQUENT ITEMS</dated-link>
      <para>

Section 4.4, "Responsibility for Normalization", is the section in which the Query WG is most interested.  Intense discussions have taken place in the past over the subject of when normalization should, should not, must, or must not be performed, and what components of an environment have responsibilities in that area.  Implementers of data repositories that might contain vast quantities of data (e.g., database systems) have expressed particular concerns about this, observing that some applications involve the need to store data very quickly, but retrieve it in a less urgent fashion, while other applications place severe demands on retrieval but have fewer constraints on storing data.  In other words, the demands of users of applications, not a rigid policy, must govern *some* aspects of the decision about when normalization is performed and by whom.



</para>
    </comment>
  </description>
</lc-comment>

Received on Friday, 31 May 2002 05:51:54 UTC