OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsrp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Groups - WSRP TC call modified



WSRP TC call has been modified by Schaeck Thomas (SCHAECK@de.ibm.com).

Event description:
USA Toll Free Number: 877-718-0936
USA Toll Number: +1-712-923-6878
PARTICIPANT PASSCODE: 402957

Agenda:
Review Agenda for F2F Meeting next week
---------------------------------------

Statements about successful use of the WSRP TC Spec 
---------------------------------------------------

Errata
------

Here is the current list of errata requests we need to deal with: 

#1. 4/24/03 (Atul Batra) 
If it's not too late, could you please include my name in Appendix D.2 of the specification titled "WSRP Committee Members" 

Document: Spec 
Section: D.2 

New Text:  Atul Batra*, Sun Microsystems 


#2. 4/24/03 (Rich Thompson) 
Version coming out of the public review period should be our 1.0 

Document: Spec & wsdl 
Section: Property (shows in header and page 1). Also in wsdl and xsd file comments. 

Old Text: 0.95 
New Text: 1.0 


#3. 4/24/03 (Claus Von Riegen) 
Our WSDL uses qualified names to reference portType fault operations from soap:fault elements. Taking the following WSDL fragment (that is part of a wsdl:operation, which in turn is part of a wsdl:binding) as an example, 
 
   
 
The "intf:" prefix makes the WSDL document invalid against the WSDL 1.1 
schema, since the soap:fault name attribute is of type NCName. Removing all occurrences of the "intf:" prefix should resolve the issue.

Document: wsrp_v1_bindings.wsdl
Section: throughout 
Old Text:  ) 
I just noticed in 0.95 of the WSRP spec pg 64, ln 20, an URL rewriting example is given as: 

wsrp-rewrite?wsrp-urlType=blockingAction&wsrp-secureURL=true&wsrp-navigationalState=a8h4K5JD9&interactionState=fg4h923mdk/wsrp-rewrite 

I think it should be: 
wsrp-rewrite?wsrp-urlType=blockingAction&wsrp-secureURL=true&wsrp-navigationalState=a8h4K5JD9&wsrp-interactionState=fg4h923mdk/wsrp-rewrite 

Document: Spec 
Section: 10.2.1.8 (example 3) 
Old Text: wsrp-rewrite?wsrp-urlType=blockingAction&wsrp-secureURL=true&wsrp-navigationalState=a8h4K5JD9&interactionState=fg4h923mdk/wsrp-rewrite 

New Text: wsrp-rewrite?wsrp-urlType=blockingAction&wsrp-secureURL=true&wsrp-navigationalState=a8h4K5JD9&wsrp-interactionState=fg4h923mdk/wsrp-rewrite 


#13. 4/30/03 (Yossi Tamari) 
Change definition of the Extension type: 

Document: Spec 
Section: 5.1.1 
Old Text: [O] Object                 any[] 
New Text: [O] Object                 any 

Reason: The definition here is of a single Extension field, not of the array. Anywhere else in the spec we use an array of Extension ([O] Extension extensions[]). This also matches our wsrp_v1_types.xsd better. 


#14. 4/30/03 (Rich Thompson) 
Change definition of the any field for the Extension type. Several developers from various companies have emailed me about the requirement that the extensions come from a non-WSRP namespace. The question centers on how to then reuse the types defined within the WSRP namespace. I suggest adding the following sentence: 

Document: Spec 
Section: 5.1.1 

New Text: While the element definitions for these extensions are required to be in a namespace other than WSRP, the reuse of the types defined within the WSRP namespace by those definitions is encouraged as this increases the likelihood of the receiving partner being able to deserialize the extension in a useful manner. 


#15. 5/5/03 (Rich Thompson) 
This conformance statement refers to the registrationPropertiesDescription field as required, but the IDL and WSDL both say it is optional. 

Document: Spec 
Section:  5.2
Old Text: The minimum information a Producer MUST return from getServiceDescription() is that which declares what is required for a Consumer to register (i.e. the requiresRegistration flag and the registrationPropertyDescription field) with the Producer [R300][R301][R303]. 

New Text: The minimum information a Producer MUST return from getServiceDescription() is that which declares what is required for a Consumer to register with the Producer (i.e. the requiresRegistration flag and whenever additional data is required, the optional registrationPropertyDescription field) [R300][R301][R303]. 


Date:  Thursday, 08 May 2003
Time:  11:00am - 12:00pm Eastern Time

This event is one in a list of recurring events.
Other upcoming dates include:

Thursday, 20 February 2003, 12:00pm to 01:00pm Eastern Time
Thursday, 27 February 2003, 12:00pm to 01:00pm Eastern Time
Thursday, 06 March 2003, 12:00pm to 01:00pm Eastern Time
Thursday, 13 March 2003, 11:00am to 01:00pm Eastern Time
Thursday, 20 March 2003, 11:00am to 01:00pm Eastern Time
Thursday, 27 March 2003, 11:00am to 01:00pm Eastern Time
Thursday, 03 April 2003, 11:00am to 01:00pm Eastern Time
Thursday, 10 April 2003, 11:00am to 12:00pm Eastern Time
Thursday, 17 April 2003, 11:00am to 12:00pm Eastern Time
Thursday, 24 April 2003, 11:00am to 12:00pm Eastern Time
Thursday, 01 May 2003, 11:00am to 12:00pm Eastern Time
Thursday, 15 May 2003, 11:00am to 12:00pm Eastern Time
Thursday, 22 May 2003, 11:00am to 12:00pm Eastern Time
Thursday, 29 May 2003, 11:00am to 12:00pm Eastern Time
Thursday, 05 June 2003, 11:00am to 12:00pm Eastern Time
Thursday, 12 June 2003, 11:00am to 12:00pm Eastern Time
Thursday, 19 June 2003, 11:00am to 12:00pm Eastern Time
Thursday, 26 June 2003, 11:00am to 12:00pm Eastern Time
Thursday, 03 July 2003, 11:00am to 12:00pm Eastern Time
Thursday, 10 July 2003, 11:00am to 12:00pm Eastern Time
Thursday, 17 July 2003, 11:00am to 12:00pm Eastern Time
Thursday, 24 July 2003, 11:00am to 12:00pm Eastern Time
Thursday, 31 July 2003, 11:00am to 12:00pm Eastern Time
Thursday, 07 August 2003, 11:00am to 12:00pm Eastern Time
Thursday, 14 August 2003, 11:00am to 12:00pm Eastern Time
Thursday, 21 August 2003, 11:00am to 12:00pm Eastern Time
Thursday, 28 August 2003, 11:00am to 12:00pm Eastern Time
Thursday, 04 September 2003, 11:00am to 12:00pm Eastern Time
Thursday, 11 September 2003, 11:00am to 12:00pm Eastern Time
Thursday, 18 September 2003, 11:00am to 12:00pm Eastern Time
Thursday, 25 September 2003, 11:00am to 12:00pm Eastern Time
Thursday, 02 October 2003, 11:00am to 12:00pm Eastern Time
Thursday, 09 October 2003, 11:00am to 12:00pm Eastern Time
Thursday, 16 October 2003, 11:00am to 12:00pm Eastern Time
Thursday, 23 October 2003, 11:00am to 12:00pm Eastern Time
Thursday, 30 October 2003, 11:00am to 12:00pm Eastern Time
Thursday, 06 November 2003, 11:00am to 12:00pm Eastern Time
Thursday, 13 November 2003, 11:00am to 12:00pm Eastern Time
Thursday, 20 November 2003, 11:00am to 12:00pm Eastern Time
Thursday, 27 November 2003, 11:00am to 12:00pm Eastern Time
Thursday, 04 December 2003, 11:00am to 12:00pm Eastern Time
Thursday, 11 December 2003, 11:00am to 12:00pm Eastern Time
Thursday, 18 December 2003, 11:00am to 12:00pm Eastern Time
Thursday, 25 December 2003, 11:00am to 12:00pm Eastern Time


View event details:
http://www.oasis-open.org/apps/org/workgroup/wsrp/event.php?event_id=112

PLEASE NOTE:  If the above link does not work for you, your email
application may be breaking the link into two pieces.  You may be able to
copy and paste the entire link address into the address field of your web
browser.




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]