[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [wsrp-conformance] [AS198] Honoring requiresRewrite
How about the following: 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", and the resource MIME type is textual. The only catch here is that the consumer needs to determine whether a given MIME type is textual or not. Subbu Rich Thompson said the following on 11/05/2003 06:09 AM: > > If you could suggest a rewording .... > > It is more than XML that potentially needs to be rewritten. Javascript > and CSS styles are two that pop to mind. Perhaps it could be limited > to textual mime types .... > > Rich > > > *Subbu Allamaraju <subbu@bea.com>* > > 11/04/2003 08:50 PM > > > To > wsrp-conformance@lists.oasis-open.org > cc > > Subject > Re: [wsrp-conformance] [AS198] Honoring requiresRewrite > > > > > > > > > > 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". > > > > > To unsubscribe from this mailing list (and be removed from the roster > of the OASIS TC), go to > http://www.oasis-open.org/apps/org/workgroup/wsrp-conformance/members/leave_workgroup.php. > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]