[Standards-JIG] XHTML further simplification

Ian Paterson ian.paterson at clientside.co.uk
Tue Sep 21 00:02:03 UTC 2004


IMHO JEP-0071 may be simplified further. The changes below would all make
implementation easier without reducing functionality.

1. The Text Module Profile should not include the <div/> element. For IM
purposes <p/> is almost identical. The difference being that <p/> is more
simple to implement because it does not allow the nesting of blocks. For
example:
<p>Nested paragraphs<p>like this one</p>are NOT allowed.</p>

2. The Text Module Profile should not include the <br/> element. The two
examples below render identically with any combination of the Recommended
Style Properties:
<p>Line one<br/>Line two</p>
<p>Line one</p><p>Line two</p>

3. Whitespace should not be preserved (see Business Rule 7) since this is
NOT consistent with standard XHTML rendering. The sending client should
always use <p/> elements to indicate line breaks. It may replace multiple
spaces in user input with multiple non-breaking spaces ( ), or use the
CSS padding-left property. For examples:
<p>Name:   Macbeth</p>
<p>Name:<span style="padding-left:2em">Macbeth</span></p>

4. <img/> width/height should be REQUIRED not just RECOMMENDED since:
- "It gives the receiving application hints as to whether the image is too
big to fit into the current interface."
- The message can be displayed in the correct layout (with an image
placeholder) before the image file has finished being downloaded.
- Clients may decide to avoid downloading very large images.




More information about the Standards mailing list