[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [wsrp-webservice] [wsrp-wsia] web services call
Since only Rich and I called in we mainly used the time to go over some minor editorials I found in 0.92. I will recommend that the best practice for sending XML fragments for now is as a markupString or as markupBinary if charset matters. Rich (or Richard with Web Master userCategory) will put the 0.92 wsdl on the Oasis Web site. Chris, David, did you find any issues for your Web stacks? regards, Andre -----Original Message----- From: Andre Kramer Sent: 11 March 2003 12:35 To: 'Rich Thompson' Cc: 'wsrp-webservice@lists.oasis-open.org' Subject: RE: [wsrp-wsia] Spec v0.92 Looks fine on first test (except version numbers in wsdl are wrong). Should we have a wsdl sub group call tomorrow? Wednesdays, 7 am PST / 10 am EST / 4 pm CET, 1 hour US dial in #: 1.888.481.3032 International Dial in #: 1.617.801.9600 Participant Passcode: 28614774 (you will be asked for your name) UK 0800 904 7961 D 0800 1813856 Some wsdl related comments below. regards, Andre -----Original Message----- From: Rich Thompson [mailto:richt2@us.ibm.com] Sent: 10 March 2003 18:31 To: wsrp-wsia@lists.oasis-open.org; wsia@lists.oasis-open.org; wsrp@lists.oasis-open.org Subject: [wsrp-wsia] Spec v0.92 I have reflected the change request resolutions to-date into the spec to produce this version. I think the following are all the open items still needing resolution: Left open at the Jan F2F: - Sasha to propose language for 1.2.4 about what the protocol enables End-Users to do. - WSDL subgroup to explore a more "natural" way to carry xml markup. (current best is in the markupBinary field) <ak> I sent the attached to the email list after the last f2f partly to address this issue, but we did not discusss it yet.</ak> - Desire to rename the MarkupType Type. Suggestions have included MarkupSupport and MarkupFormat. Any others? <ak> UploadContext uses mimeType. http uses ContentType. </ak> Open Change Requests: - 138 – How does info get to proxied resources - 141 – Add previous windowState and mode? - 207 – PortletDescription dependent on UserContext? - 213 – Require modes, windowstates & userAuthentication are URIs (This was in the set that was blanket adopted and is reflected in v0.92, but is enough different from the discussion of the blanket adopted set that I am calling it out here.) - 215 – Delete statement about “private conversational state” - 230 – Setting navState - 234 – Delete section B.1 The "marked" version has had all of the formatting changes accepted so that it is easier to see the insertions and deletions. The second copy has had all changes accepted for those who find the change marks distracting. An item that has been discussed in the WSDL subgroup that also merits calling out is that we define two types in our WSDL (StringArray and NamedStringArray) that we do not use. They have been left in the definition for possible use by extensions. <ak> We are going to call out NamedStringArray for UserProfile extension using name / value pairs? Then it should be in the spec doc as well as in wsdl. </ak> Rich Thompson
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]