OASIS Open: Committees

Interest in "Client Rewritable URLs" extension

Should we create an extension to allow client-side rewriting of URLs. This allows for RIAs including dynamic module loading and interactive UI.

Please vote on which URL types you would like to see supported. After the ballot closes I'll compile the results and (assuming there is interest) create a new ballot that is more targeted to an actual proposal.

Amendment Posted on Tuesday, 13 January 2009:
Problem Statement:
Currently WSRP URLs are opaque to the client (browser). However, many Rich Internet (Web 2.0) technologies require manipulation of URLs, to add parameters and/or modify a portion of the path.

[ ]	No
[ ]	Abstain
[ ]	Yes: Proxied Resource (out-of-band)
[ ]	Yes: Get Resource (in-band)
[ ]	Yes: Render (GetMarkup)
[ ]	Yes: Blocking (PerformBlockingInteraction)

Opening:		Thursday, 8 January 2009 @ 12:00 am EST
Closing:		Wednesday, 14 January 2009 @ 12:00 am EST
Group:		WSRP Interfaces SC

Ballot has closed.

Voting Details

Voting Summary

Options with highest number of votes are bold

Option	# Votes	% of Total
No	0	0%
Abstain	0
Yes: Proxied Resource (out-of-band)	6	29%
Yes: Get Resource (in-band)	6	29%
Yes: Render (GetMarkup)	3	14%
Yes: Blocking (PerformBlockingInteraction)	6	29%

Eligible members who have voted:	6 of 9	67%
Eligible members who have abstained:	0 of 9	0%
Eligible members who have not voted:	3 of 9	33%

Voting Details

Voter	Company	Vote	Reference Document and/or Comment
Richard Jacob	IBM	--
Rich Thompson	IBM	Yes: Proxied Resource (out-of-band) Yes: Get Resource (in-band) Yes: Render (GetMarkup) Yes: Blocking (PerformBlockingInteraction)
Nader Oteifa	NetUnity Software	Yes: Proxied Resource (out-of-band) Yes: Get Resource (in-band) Yes: Render (GetMarkup) Yes: Blocking (PerformBlockingInteraction)
Dina Steeve	Oracle Corporation	Yes: Proxied Resource (out-of-band) Yes: Get Resource (in-band) Yes: Blocking (PerformBlockingInteraction)
Nathan Lipke	Oracle Corporation	Yes: Proxied Resource (out-of-band) Yes: Get Resource (in-band) Yes: Blocking (PerformBlockingInteraction)	Since the GetMarkup request does not contain parameters and it is idempotent getResource should be used instead.
Kevin Frender	Oracle Corporation	Yes: Proxied Resource (out-of-band) Yes: Get Resource (in-band) Yes: Blocking (PerformBlockingInteraction)	I'll vote yes for PBI, though I do believe that a restriction should be placed on redirect URLs emitted from a PBI, banning redirect URLs from being client-side rewritable.
Michael Freedman	Oracle Corporation	Yes: Proxied Resource (out-of-band) Yes: Get Resource (in-band) Yes: Render (GetMarkup) Yes: Blocking (PerformBlockingInteraction)	By way of clarification on render/getmarkup. Since we support public render parameters, my hope would be that such parameters are settable by the client and hence the need to support render/getmarkup
Rajesh T	Sun Microsystems	--
Satish Ramaswamy	Vignette Corporation	--