Re: Assertion Summary Texts in Part 1

Ram,

This is too open-ended. Could you list all the assertions that you think 
are incomplete and suggest an improvement. The text is copied directly 
front from the spec so the suggested improvement might require an edit to 
the enclosing paragraph too. We should be able to treat these changes as 
editorial. Thx.

Arthur Ryman,
IBM Software Group, Rational Division

blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca



"Ramkumar Menon" <ramkumar.menon@gmail.com> 
Sent by: www-ws-desc-request@w3.org
02/05/2007 06:50 PM

To
www-ws-desc@w3.org
cc

Subject
Assertion Summary Texts in Part 1






Hi Gurus,
 
One suggestion.Part 1 - Appendix E [Assertion Summary] is a great view of 
all assertions about component models and documents.
I would appreciate if the Summary text be a complete English sentence that 
contains the complete text about the assertion.
 
For instance, see the following assertion.
 
-----------------------------------------------
Assertion Id                 Summary
-----------------------------------------------
Description-1201005     Zero or more element information items amongst its 
[children], in order as follows: 
 
If the User were reading this in soft copy, he/she could click on the 
Assertion Id hyperlink to navigate to the section that states the 
assertion. But if the User were reading the specification on a hard print, 
it would not be possible for he/she to get a clear understanding on what 
it means.  Note that there are other assertions in this section which 
depict similar behaviour. 
 
Hope that helps.
rgds,
Ram



-- 
Shift to the left, shift to the right!
Pop up, push down, byte, byte, byte!

-Ramkumar Menon
A typical Macroprocessor