Re: [wsrp-conformance] [AS198] Honoring requiresRewrite

[Subbu Allamaraju <subbu@bea.com>]

It just occurred to me that this assertion implies that the consumer 
will have to parse non-XML content type as well. How about relaxing this 
assertion to just include XML-type resources? Although it would be 
incorrect/useless to specify requireRewrite=true for, say, for 
application/pdf type resources, the consumer can skip rewriting such 
resources and save some cycles.

Subbu

Rich Thompson wrote:

>
> AS137 requires the two parameters be specified when the urlType is 
> resource.
>
> This is a good clarification ... with update:
> The Consumer shall parse the stream fetched from a resource for URL 
> rewriting and namespacing when the resource was requested by a URL 
> with wsrp-urlType="resource" and wsrp-requiresRewrite="true".
>
> Rich
>
>
> *Andre Kramer <andre.kramer@eu.citrix.com>*
>
> 10/03/2003 04:40 AM
>
> 	
> To
> 	Rich Thompson/Watson/IBM@IBMUS
> cc
> 	
> Subject
> 	RE: [wsrp-conformance] [AS198] Honoring requiresRewrite
>
>
>
> 	
>
>
>
>
>
> encapuslating markup - when the resource was requested by an resource 
> url with parameter wsrp-requiresRewrite set. [do we assert that url 
> and requiresRewrite are required params?]
> -----Original Message-----*
> From:* Rich Thompson [mailto:richt2@us.ibm.com]*
> Sent:* 02 October 2003 19:33*
> To:* wsrp-conformance@lists.oasis-open.org*
> Subject:* [wsrp-conformance] [AS198] Honoring requiresRewrite
>
>
> Draft I was asked to circulate:
>
> The Consumer shall parse the stream fetched from a resource for URL 
> rewriting and namespacing when the encapsulating markup specified 
> wsrp-requiresRewrite="true".