Re: REMINDER: Approve WSUS

Addison Phillips [wM] wrote:

> WSTF members:
> 
> I was looking forward to coming back and finding the Usage Scenarios
> published... only they aren't. 

Optimists are always disappointed :-P

> Please send your approval to this list or plan
> to attend this week's meeting. If you think something needs fixing, please
> send your comments PRIOR to this week's meeting.

Mea culpa, mea maxima culpa.  I was sick, synchronously with attending a 
conference and going out of town. Production low, fever high.

OK, so since this is very late, I presume these changes won't go in.  None of 
them are Earth-shattering, so I approve the document.   But if these changes 
could go in, it would make the document a bit more readable.

Minor comments:

3.1.2 "::" change to ":" after Scenario A, Different Locale Identifiers
4.1.4.1 in the Implementation Decision example, to keep with the example in the 
preceding text it would be better to have Locale.GERMANY instead of Locale.US
4.1.5.3 change "is this case" to "in this case"
4.2.2 change "a provide" to "a provider", and "euro" should not be capitalized 
(just like "dollar")
4.2.3 number 2, "is requests" change to "it requests" or "are requests" or "is a 
request"
4.4.2 change "formating" to "formatting"
4.4.3 Scenario B change "different results than they" to "different results from 
what they"
4.5.4 change "not supported requester" to "not supported by the requester"
4.5.5 change "this is rare problem" to "this is a rare problem"
4.5.6 "non-Unicode" in title to "Non-Unicode"
4.5.7 change "describes that" to "states that"

"implementers" and "implementors" in various spots in the doc - standardize.

4.6 "valuespassed" => "values passed" (may be an artifact of my printout)
4.8 "data, might" => "data might"    "case, would" => "case would"
4.8.1 make title titlecase to match other titles
4.9.2 unless "be adorned" is XML jargon, replace with "has" or "contains" 
("adorned" has a connotation of decoration, which gives the phrase a weird and 
frivolous air).  Item 4 still has ??? after RFC3066.  Under Example: 
Translation, it looks like "transliteration" was written where "translation" was 
meant.  Example: Multiple Names, the description completely ignores the 5th 
<name> element, which is the romanization of the name (also, wouldn't it make 
more sense to have the kana be hiragana and not katakana since the name is 
native Japanese?). "adornment" => "attribute"
4.11 "rules. (For" => "rules (for" ;  "has no correlation with" => "has no 
correlation to"   ;   "I-013for a some examples" => "I-013 for some examples"
4.12 "down the may" => "down the road may" ?
4.12.1 "Locale-Neutral" => "Language-Neutral" to match the descriptive text in 
the preceding sentence.  "asian" => "Asian"
4.12.1.1 "language neutral" => "language-neutral" consistency
4.12.1.2 "supported should" => "supported, should"  ;  "item, with" => "item with"
4.12.2.1 "asian" => "Asian"  "E.g." => "For example"
4.12.2.2 "increase number" => "increase the number"
4.12.2.4 make title titlecase to match other titles.  "and a second or more 
search" => "and a second search (and possibly more)"  ;  "As and" => "As an"
4.12.2.5 make title titlecase to match other titles
4.13.3 "Matercard/Eurocard" => "MasterCard/Eurocard"

Also change all instances of "Mastercard" and "Master Card" to "MasterCard" 
including in examples
4.13.3.1 "values, that" => "values that"
4.13.3.2 Change of person suddenly to "we", need to impersonalize/formalize.
4.13.3.3 has identical title to 4.13.3.1, and no text - should be removed I think
4.13.3.4 should be deleted
4.16.1 "succesor" => "successor"
4.16.3.1 still an @@@ in this section
4.16.4 still wasn't in as of July 2

> 
> Addison
> 
> Addison P. Phillips Director, Globalization Architecture webMethods |
> Delivering Global Business Visibility http://www.webMethods.com Chair, W3C
> Internationalization (I18N) Working Group Chair, W3C-I18N-WG, Web Services
> Task Force http://www.w3.org/International
> 
> Internationalization is an architecture. It is not a feature.
> 

-- 
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.
-Bjarne Stroustrup, designer of C++ programming language (1950- )

Received on Thursday, 15 July 2004 18:42:21 UTC