Re: FtF outline 2 (again)

Here are my changes, comments - I-017, I-018, I-019, I-020, I-026, I-027

I've indicated below where these sections may be applicable in the new outline.

Cheers,

Mike____

"Addison Phillips [wM]" wrote:

> new activity: provide GEO information to GEO.
> what is purpose of this document?
> what do we accomplish here?
>  x New Outline
>    What's in
>    What's out
>  x What's by reference (info)
>    New Use Cases (use case)
>    Reorder from existing doc to new sections.
>
> 1. Intro to document.
> 2. Intro to Web Services
>   - basic framework (description of process)
>   - pointers to WS core documents
>   - definition of a Web Service
>   - overview of SOAP, WSDL, UDDI, SOAP Features, MEPs, etc.
> 3. Intro to Internationalization (definitions for WS discussion)
>   - what is internationalization
>   - why internationalization (two audiences)
>     - why not ad hoc (need for interoperability discussion)
>   - what is human language
>   - what is a locale/international preferences
>   - XML Schema (locale independence) vs. locale dependent data
>     -
>   - mention RFC2277 ;-)
> 4. WS internationalization issues
>   - locale patterns in Web services
>     - locale neutral
>     - service determined

        I-018

>
>     - user(caller) influenced
>     - data driven (Martin)

        I-017, I-018

>
>   - legacy issues
>     - encoding handling
>       - application/soap+xml and charset parameter (info)
>       - XML document declaration (info)
>       - what if ultimate application has encoding limitations (use case)
>       - attachments (use case)
>     - Pandora's box: non-internationalized data structures (later)(placeholders)
>
> 5. For Implementers of WS Providers, Tools, and Servers
>   - Providing locale negotiation (info)

        I-020

>
>   - Providing support for locale patterns (use case) (Addison)
>   * soap-header requirement?

>
>   * standard for locale-pattern communication in WSDL requirement?

>        I-018, I-019

>
>   - Faults and the Reason Text Element (use cases)(extant)
>   - UDDI search and multilingual text (use case) (Mike) (placeholder)

        I-026

>
>   - introspection of actual "method" to produce WSDL representation (JSR-101? Deb placeholder)
>     - for example java.util.Locale -> lang/region/variant strings?
> 6. For Implementers of a Web Service
>   - use locale neutral data structures

        I-017

>
>   - sorting/collation (use case - curses)
>     - e.g. curses
>     - JIS sort vs. U+ sort
>   - natural language text search (use case)
>     - keyword searching
>     - "like"
>     - e.g. search "Dürst" should return "Duerst" as well (in German)
>   - how to handle human-readable text in WS
>     - structuring records (info)
>     - enumerated values and object naming
>       - use of default English-like names (info)
>       - allowing for "display names" vs. internal names (Mike - placeholder)

        I-026

>
>       - etc. (info)
>     - exchanging language preferences (or assuming it?)
>       - use metadata
>       - use separate bindings or services/servers (use case)
>       - ask for the language
>       - guess (use case - language default)

        I-020

>
>   - other i18n-like things: where does this service apply to?
>     - timezones and time
>     - calendar
>       - holiday, and work rules (use case - short example)
>     - regimes: tax, customs, legal, and other considerations
>   - other transports (later)
>     - HTTP accept-language does not exist
>     - FTP
>     - SMTP
>       - MIME tags
> 7. Message Exchange Patterns and Scenarios (WS-Arch reviews?)
>     - there are 33 of these (assign 6 to each and review Tuesday)
> 8. complex scenarios? choreography/BPEL/layering/etc. (Later)
>   * not done here.
>
>
> Notes:
> - use cases inline?
> - change identifying letter of our scenarios to "I" from "S"
>
> ===============
> data driven examples.
>
> VAT example (source/target location, what commodity is)
> unit of measure example (customary vs. SI or maybe currency)