Re: here you go

Review Assignments - Usage Scenarios
11 Usage Scenarios
    11.1 Data Integrity and Interoperability (Andrea)
        11.1.1 I-001: Data Integrity using an Unicode-based Encoding
        11.1.2 I-002: Data Integrity using a Legacy Encoding
    11.2 Language (Locale) Negotiation for SOAP Fault Messages (Deb)
        11.2.1 I-007: Language Preference for Chained Services
        11.2.2 I-008: Locale Sensitive Formated Data in SOAP Fault Messages
        11.2.3 I-010: Language Preference for Multiple SOAP Bindings
        11.2.4 I-011: HeaderFault vs. Fault
        11.2.5 I-012: Interaction of Language Negotiation and Caching
    11.3 Locale Neutral vs. Locale Sensitive Data Exchange (Deb/Mike)
        11.3.1 Background
        11.3.2 I-016: Locale Neutral Formated Data (Deb)
        11.3.3 I-017: Data with Additional 'Attributes' (Mike)
        11.3.4 I-018: Data with Default 'Attribute' (Mike)
        11.3.5 I-019: Locale Dependent Datatypes (Mike)
        11.3.6 I-020: Correlation of Data among Services in Different Languages (Mike)
    11.4 Locale Sensitive Presentation (Takao)
        11.4.1 I-021: Data Formatting for End User on Receiver Side
        11.4.2 I-022: Data Formatting on Sender Side
        11.4.3 I-023: Data Formatting on Receiver Side according to Sender
    11.5 Locale Sensitive Data Processing (Takao)
        11.5.1 I-024: Locale Sensitive Processing by Provider (Receiver)
            11.5.1.1 Transport Layer (HTTP, SMTP/MIME, etc.)
            11.5.1.2 Service Provider Layer
            11.5.1.3 Service Layer
        11.5.2 I-025: Opaque Identifier to Identify a Locale
    11.6 Finding Services (Mike)
        11.6.1 I-026: Searching for Web Services
        11.6.2 I-027: Fall-Back for Internationalized Web Services
    11.7 Services for Internationalization Functionality (Andrea)
        11.7.1 I-028: Outsourcing Locale-Related Services
        11.7.2 I-029: Propagating Updates related to Locales
    11.8 Development of Internationalized Web Services (Addison)
        11.8.1 I-030: Internationalizing an Existing Web Service
        11.8.2 I-031: Communicating Available Options


"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
>     - user(caller) influenced
>     - data driven (Martin)
>   - 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)
>   - Providing support for locale patterns (use case) (Addison)
>   * soap-header requirement?
>   * standard for locale-pattern communication in WSDL requirement?
>   - Faults and the Reason Text Element (use cases)(extant)
>   - UDDI search and multilingual text (use case) (Mike) (placeholder)
>   - 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
>   - 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)
>       - 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)
>   - 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)