Re: [Fwd: CAP-12 - interm version 'A']

Nathaniel Borenstein <[email protected]>
Newsgroups gmane.ietf.calendar
Message-ID <[email protected]>
What Mark did simply proved that it is possible to do what Bruce had  
asked for.  It is silly for more than one person to have to do this,  
and I always understood this to be a part of the job of the document  
editor.

BTW the whole problem can be simplified a bit if the editor uses a tool  
like xml2rfc and produces diffs using the relevant component files...   
-- Nathaniel

On Monday, September 8, 2003, at 05:31  PM, Mark Smith wrote:

>
> [email protected] wrote:
>
>> If he cant change things in CAP then why are there 707 changes
>> reported by diff?  Whats the rush to have CAP-12 and CAP-12-a so soon
>> after CAP-11 if nothings changed?  If you honestly believe there were
>> "thousands" of typos and grammar changes then I have some land to sell
>> you...
>
> Just looking at your own diff file and doing some math:
>
> Some one cut out many diffs and header/footer from your diff so I am
> guessing to some of these numbers.
>
> (142) were footer changed and would have changed
> anyway because the date of the draft changed.
> That Bruce finds it necessary to comment about on this list.
>
> (147) were because the expire date changed on header
> and elsewhere and would have changed anyway.
> That Bruce finds it necessary to comment about on this list.
>
> The TOC is 3 pages, so I'll assume that is (3) changes in your diff
> count.
> That Bruce finds it necessary to comment about on this list.
>
> (1) changed because the name of the draft version.
>
> That is about (293) utterly nontechnical changes so far that would
> have changed anyway just by releasing a new version.
> That Bruce finds it necessary to comment about on this list.
>
> That leaves about (414) changes.
>
> About (100) typos that were fixed - double words, missing words,
> spelling
> errors and wrong words.
> And Bruce does not comment on or care about on this list.
>
> That leaves about (314) changes.
>
> (1) added explanation about the ordering of properties and parameters.
>     And Bruce does not comment on or care about on this list.
>
> (13) abnf fixes (5 misspelled names fixed).
>      That Bruce does not comment on or care about on this list.
>
> (1) fix to the name of valid/recommended components.
>     And Bruce does not comment on or care about on this list.
>
> (2) changes to remove that mysterious missing text that you can not
>     seem to find.
>     And Bruce does not comment on or care about on this list.
>
> (1) change to the security considerations.
>     And Bruce does not comment on or care about on this list.
>
> Conclusions (based on your 707 number):
>   About 118 changes that if done incorrectly would effect the protocol
>   And Bruce does not comment on or care about on this list.
>
>   And about 589 changes that Bruce seems to focus on that have no
>   effect on the protocol. Again, get a life! It sure looks to me
>   as if Bruce is trying to stall CAP.
>
>> Whats the rush to have CAP-12 and CAP-12-a so soon after CAP-11 i
>> nothings changed?
>
> So you want to complain if he waits for lots of changes.
> And you want to complain if he does not wait for lots of canges.
> You want me to take you seriously?
>
>> If you honestly believe there were "thousands" of typos
>> and grammar changes then I have some land to sell you...
>
> Yet another dishonest (sorry Pat, it is a lie. Enthusiasm is for
> children)
> statement from Bruce. Doug said "thousands WG and private emails" not
> thousands of typos. Now who is the one trying to mislead this list?
>
> Mark
>
>> Bruce
>> ====================================================================== 
>> =====
>> Bruce Kahn                                INet:
>> [email protected]
>> Messaging & Collaboration                 Phone: 978.399.6496
>> IBM Software Group                         FAX: and nothing but the
>> FAX...
>> Standard disclaimers apply, even where prohibited by law...
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.