RE: [Fwd: Re: WSTF Teleconference Meeting Notes]

To answer your question: "no", since we don't know any better than anyone else what the major numbered sections are going to end up doing: we were all at the F2F where these sections were created. Our work together (and mine individually) has been linear, working down to 4.x. This material has mostly been cohesive. We haven't discussed at all the structure of the following material and my edits in these sections has been confined to wordsmithing and cleanup.

Much of the stuff at the very bottom of the document is slag waiting to be moved up into an appropriate position. The empty stuff in 5.x and 6.x was the outline we created. If we can't figure out what to do with a section, maybe it shouldn't be there?

I'm a bit concerned that our document illustrate our requirements better. Some of the other material strikes me as extraneous if that is our goal.

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.

> -----Original Message-----
> From: public-i18n-ws-request@w3.org
> [mailto:public-i18n-ws-request@w3.org]On Behalf Of A. Vine
> Sent: vendredi 6 février 2004 17:09
> To: I18n WSTF
> Subject: [Fwd: Re: WSTF Teleconference Meeting Notes]
> 
> 
> 
> I won't be at the meeting next week.
> Since I didn't receive any sort of response or clarification on 
> the below, I 
> have made no progress on it.
> 
> Andrea
> 
> -------- Original Message --------
> Subject: Re: WSTF Teleconference Meeting Notes
> Date: Tue, 27 Jan 2004 17:43:00 -0800
> From: A. Vine <andrea.vine@sun.com>
> Reply-To: andrea.vine@sun.com
> Organization: Sun Microsystems
> To: aphillips@webmethods.com
> CC: public-i18n-ws@w3.org
> References: <PNEHIBAMBMLHDMJDDFLHMEDHHJAA.aphillips@webmethods.com>
> 
> A quick pass over the document seems to indicate that the 
> following sections
> need text:
> 
> 5.3 Providing Support for Locale Patterns
> 5.4 SOAP Header Structures
> 5.6 SOAP Faults and the Reason Text Element
> 5.7 UDDI Search and Multilingual Text
> 5.8 Introspection Service Signature When Generating WSDL
> 6.1 use locale neutral data structures
> 6.2.1 JIS sort vs. Unicode sort
> 6.2.2 e.g. curses
> 6.3 natural language text search
> 6.3.1 keyword searching
> 6.3.2 "like"
> 6.3.3 e.g. search "Dürst" should return "Duerst" as well (in German)
> 6.4 Human-Readable Text in Web Services
> 6.4.1 structuring records
> 6.4.2 enumerated values and object naming
> 6.4.2.1 use of default English-like names
> 6.4.2.2 allowing for "display names" vs. internal names vs. aliases
> 6.5.2 Selecting Locale or Language
> 6.5.2.1 Metadata
> 6.5.2.2 Separate Bindings per Language
> 6.5.2.3 Separate Services per Language
> 6.5.2.4 Separate Servers per Language
> 6.5.2.5 Language Preference in Service Signature
> 6.5.2.6 Guess (there's an elaborate example that follows this but 
> I don'tsee
> how it relates exactly)
> 6.6 Data Structures
> 6.6.1 Times and Time Zones
> 6.6.3 Holidays, Work Rules and Locale-Specific Date Values
> 6.7 Regimes
> 6.7.1 tax, customs, legal, and other considerations
> 6.9 Transports
> 6.9.1 HTTP Accept-Language
> 6.9.2 FTP
> 6.9.3 SMTP
> 6.9.3.1 MIME tags
> 8 complex scenarios? choreography/BPEL/layering/etc.
> 
> Mike has volunteered for 6.3.  In looking at the blank sections, 
> I'm a little
> confused as to the intention of several of them, and whether 
> existing scenarios
> will be moved there.
> 
> Would it be possible for Addison and Tex to provide some input on what is
> intended for the major section numbers?
> 
> Andrea
> 
> 
> Addison Phillips [wM] wrote:
> 
> > 
> > ACTION LIST
> > ===========
> > 1. AP: Incorporate Mark Davis's example for I-022 [NOT DONE]
> > 2. AP: incorporate AV's calendric time examples [PENDING]
> > 3. AP: incorporate DB's 'unfinished' usage scenarios between 7 
> and 16. [PENDING]
> > 4. MM: updating discovery scenarios. [pending]
> > 5. AP: Ping new WSCG chair: plan to liase as our requirements 
> emerge. [pending]
> > 
> > AGENDA
> > ======
> > 1. Action Item review.
> > 2. Review work on USWD: Need to gauge our progress and see what 
> we can do to get a draft out soon.
> > 3. Other business.
> > 
> > FTF Review: FIX the dates [Done]
> > Location: hotels? etc... [Addison to provide details on lodging 
> near webMethods ASAP. Tex to follow up]
> > 
> > ---
> > 
> > Discussion of Service Determined example (4.1.2.1). Leave for 
> now. Remove the booze from the example. Use noodles? Noodles it is. [Done]
> > 
> > Leave or remove WSDL/SOAP sections in locale patterns section? 
> Move to bottom. Discussion of tactics..
> > 
> > Tex/AP: edit session to move further through document.
> > Others: sign up for missing sections of text and write that 
> text by next meeting (2 weeks)
> > 
> > New target date: 1 March 2004 for WD pub.
> > 
> > MM: will take section 6.3
> > 
> > Requirements doc: need to finalize with links to US.
> > FTF: work on chartering activity, finalize US and REQ.
> > 
> > 
> > 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- )
> 
> 
> 
> -- 
> 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 Friday, 6 February 2004 20:14:17 UTC