WSDL 1.2: Updated draft (June 30)
service name as local part of a qname
RE: Freshly updated draft of part1 (was: Re: Overloading [was RE: Minutes, 27 June 2002 Web Service Description Telcon])
Re: Overloading [was RE: Minutes, 27 June 2002 Web Service Description Telcon]
RE: issue 43: Does order matter for the child elements of "defini tions"?
Resolved issues, 27 June 2002
*。。連鎖超商邀你加盟。。*
Overloading [was RE: Minutes, 27 June 2002 Web Service Description Telcon]
- Re: Overloading [was RE: Minutes, 27 June 2002 Web Service Description Telcon]
- Freshly updated draft of part1 (was: Re: Overloading [was RE: Minutes, 27 June 2002 Web Service Description Telcon])
- Re: Freshly updated draft of part1 (was: Re: Overloading [was RE: Minutes, 27 June 2002 Web Service Description Telcon])
- Re: issue-intra-port-relationship (was ..Freshly updated draft of part1 (was: Re: Overloading [was RE: Minutes, 27 June 2002 Web Service Description Telcon]))
- Re: issue-intra-port-relationship (was ..Freshly updated draft of part1 (was: Re: Overloading [was RE: Minutes, 27 June 2002 Web Service Description Telcon]))
- Re: issue-intra-port-relationship (was ..Freshly updated draft of part1 (was: Re: Overloading [was RE: Minutes, 27 June 2002 Web Service Description Telcon]))
- Re: issue-intra-port-relationship (was ..Freshly updated draft of part1 (was: Re: Overloading [was RE: Minutes, 27 June 2002 Web Service Description Telcon]))
- Re: issue-intra-port-relationship (was ..Freshly updated draft of part1 (was: Re: Overloading [was RE: Minutes, 27 June 2002 Web Service Description Telcon]))
- Freshly updated draft of part1 (was: Re: Overloading [was RE: Minutes, 27 June 2002 Web Service Description Telcon])
- Re: Overloading [was RE: Minutes, 27 June 2002 Web Service Description Telcon]
ACTION: All wg members to review part 1 and part 2 by July 4
ACTION: All wg members to review editorial issues by July 11
Minutes, 27 June 2002 Web Service Description Telcon
updated draft of WSDL 1.2 (Part 1) ready for review
updated draft
elementFormDefault="qualified" in WSDL Schema..
- RE: elementFormDefault="qualified" in WSDL Schema..
- RE: elementFormDefault="qualified" in WSDL Schema..
- RE: elementFormDefault="qualified" in WSDL Schema..
RE: Draft agenda: 24 June TAG teleconference (Arch document, WSA update)
WSDL SOAP Binding schema does not reflect the spec
Agenda for 27 June 2002 WS Description WG
Minutes, Wed Afternoon 12 June 2002 FTF
Inteaction between message and binding ( was RE: Issue 4: Use of namespace attribute on soap:body )
- Re: Inteaction between message and binding ( was RE: Issue 4: Use of namespace attribute on soap:body )
- RE: Inteaction between message and binding ( was RE: Issue 4: Use of namespace attribute on soap:body )
- RE: Inteaction between message and binding ( was RE: Issue 4: Use of namespace attribute on soap:body )
- Re: Inteaction between message and binding ( was RE: Issue 4: Use of namespace attribute on soap:body )
Issue 17: support for SOAP role attribute
- RE: Issue 17: support for SOAP role attribute
- RE: Issue 17: support for SOAP role attribute
- Re: Issue 17: support for SOAP role attribute
- RE: Issue 17: support for SOAP role attribute
- RE: Issue 17: support for SOAP role attribute
- RE: Issue 17: support for SOAP role attribute
- Re: Issue 17: support for SOAP role attribute
- Re: Issue 17: support for SOAP role attribute
Issue 25: Interaction between W3C XML Schema and SOAP Data Model
Proposal to Resolve encodingStyle Issues #5 and #30
- Re: Proposal to Resolve encodingStyle Issues #5 and #30
- Re: Proposal to Resolve encodingStyle Issues #5 and #30
- Re: Proposal to Resolve encodingStyle Issues #5 and #30
- RE: Proposal to Resolve encodingStyle Issues #5 and #30
issue: optional "name" attribute of <definition>
- Re: issue: optional "name" attribute of <definition>
- Re: issue: optional "name" attribute of <definition>
- Re: issue: optional "name" attribute of <definition>
- Re: issue: optional "name" attribute of <definition>
- RE: issue: optional "name" attribute of <definition>
Minutes 20 June 2002 WS Desc telcon
Issue 4: Use of namespace attribute on soap:body
Target namespace in WSDL
- Re: Target namespace in WSDL
- Re: Target namespace in WSDL
- Re: Target namespace in WSDL
- RE: Target namespace in WSDL
- RE: Target namespace in WSDL
- RE: Target namespace in WSDL
- RE: Target namespace in WSDL
- RE: Target namespace in WSDL
Ports, Names, Symbol Spaces and targetNamespace
Fw: Draft agenda: 24 June TAG teleconference (Arch document, WSA update)
updated editor's copy of WSDL 1.2 Part 2: Bindings
ACTION: All WG members to review redundancy issues by next week
late regrets
Issues 35, 36, 37
RE: issue 38: Clarify the what kinds of extensibility elements go where
- RE: issue 38: Clarify the what kinds of extensibility elements go where
- Re: issue 38: Clarify the what kinds of extensibility elements go where
RE: issue 43: Does order matter for the child elements of "defini tions"?
- RE: issue 43: Does order matter for the child elements of "defini tions"?
- RE: issue 43: Does order matter for the child elements of "defini tions"?
- RE: issue 43: Does order matter for the child elements of "defini tions"?
issue 42: Shall "element" attribute of "part" only refer to elements defined in schema?
issue "issue-clarify elements"
updated editor's copy of WSDL 1.2 spec
- Re: updated editor's copy of WSDL 1.2 spec
- RE: updated editor's copy of WSDL 1.2 spec
- RE: updated editor's copy of WSDL 1.2 spec
- RE: updated editor's copy of WSDL 1.2 spec
- RE: updated editor's copy of WSDL 1.2 spec
issue 26: transmission primitives
issue 34: Should portTypes be extensible?
issues 35 & 36
issue 37: Should we remove parameter order?
issue 38: Clarify the what kinds of extensibility elements go where
issue 43: Does order matter for the child elements of "definitions"?
issue 57: Should Operations permit alternate and multiple responses?
- RE: issue 57: Should Operations permit alternate and multiple responses?
- Re: issue 57: Should Operations permit alternate and multiple responses?
- Re: issue 57: Should Operations permit alternate and multiple responses?
- Re: issue 57: Should Operations permit alternate and multiple responses?
issue 60: Text in the WSDL spec inconsistency about optional parts
- RE: issue 60: Text in the WSDL spec inconsistency about optional parts
- Re: issue 60: Text in the WSDL spec inconsistency about optional parts
Proposal for dealing with solicit/response and notification
Agenda for 20 June 2002 WS Description WG
WSDL Version 1.2 Part 2: Bindings, date 2002/4/11
- RE: WSDL Version 1.2 Part 2: Bindings, date 2002/4/11
- Re: WSDL Version 1.2 Part 2: Bindings, date 2002/4/11
Regrets for 6-20 call
RE: W3C WSDL WG Issues: Non-SOAP HTTP Binding
Raw Minutes from 6-11 AM
Rationale to close the operation overloading issue
- Re: Rationale to close the operation overloading issue
- Re: Rationale to close the operation overloading issue
- Re: Rationale to close the operation overloading issue
- Re: Rationale to close the operation overloading issue
- RE: Rationale to close the operation overloading issue
- RE: Rationale to close the operation overloading issue
- RE: Rationale to close the operation overloading issue
- RE: Rationale to close the operation overloading issue
- RE: Rationale to close the operation overloading issue
- Re: Rationale to close the operation overloading issue
- RE: Rationale to close the operation overloading issue
- RE: Rationale to close the operation overloading issue
- RE: Rationale to close the operation overloading issue
- Re: Rationale to close the operation overloading issue
- RE: Rationale to close the operation overloading issue
Regrets
operation overloading issue
I will not be able to attend the today's conference call
MEP and Operations
Architecture WG Requirements vis-a-vis WSDL WG Requirements
Raw minutes for Tuesday afternoon
Fwd: Analysis of WSD Requirements by WS Arch
Analysis of WSD Requirements by WS Arch
Notes on the flip chart
an image processing use case for wsdl
- Re: an image processing use case for wsdl
- RE: an image processing use case for wsdl
- RE: an image processing use case for wsdl
RE: Second draft June FTF Agenda - issues to be discussed
Draft primer outline
raw minutes from Monday AM
raw minutes from 2002-06-10 afternoon
Text for extensibility section
- Re: Text for extensibility section
- RE: Text for extensibility section
- RE: Text for extensibility section
- RE: Text for extensibility section
- RE: Text for extensibility section
- RE: Text for extensibility section
- RE: Text for extensibility section
- RE: Text for extensibility section
Fw: [soapbuilders] NMTokens, NCNames, PortTypes, and Bindings.
SOAP Binding Faults
Second draft June FTF Agenda
Minutes, 6 June 2002 WS Description telcon
Extensibility proposal from today
RE: Editorial issue - Terminology for Operation types
RE: FTF meeting questions food
RE: ISSUE : Extensible message exchange patterns
SOAP Binding: Is body/@use required?
RE: Reminder: WS Desc telcon Thursday 6 June 2002
Agenda for 6 June 2002 WS Description WG
WS Desc WG Usage Scenarios published
[amtf] my view of what the Abstract model should do and why
Issue: Text in the WSDL spec inconsistency about optional parts
Issue: SOAP binding violates separation of abstract definitions concrete bindings
- Re: Issue: SOAP binding violates separation of abstract definitions concrete bindings
- Re: Issue: SOAP binding violates separation of abstract definitions concrete bindings
RE: New issue: Representing safe operations (was: [TAG] how to use GET to make resources addressable)
Re: New issue: Representing safe operations (was: [TAG] how to use GET to make resources addressable)
Fw: issue: service type
- RE: issue: service type
- Re: Fw: issue: service type
- proposal for resolving service type issues
- Re: Fw: issue: service type