Re: [wsrp] Public review comment: Remove markup restrictions forgetResource

[Rich Thompson <richt2@us.ibm.com>]

Are there Producers (or Consumers) who
attempt to force the restrictions of section 10.4? If so, they would need
some means of the Portlet telling them whether this particular resource
is or is not going to be aggregated into the Consumer's page. Actually,
even if they do attempt to force the restrictions on gM() responses, wouldn't
the proposal (a cautionary statement to the Portlet referencing 10.4, but
not a MUST conformance statement) tell them not to impose the restrictions
on gR() requests?

Rich

Richard Jacob <richard.jacob@de.ibm.com>

07/27/2006 07:40 AM

To	Stefan Hepper <sthepper@hursley.ibm.com>
cc	Subbu Allamaraju <subbu@bea.com>, WSRP TC <wsrp@lists.oasis-open.org>
Subject	Re: [wsrp] Public review comment: Remove markup restrictions for getResource

but how can the producer decide??
It can't tell whether the output of gR() is aggregated or not.
Wouldn't we need a hint then (like solo/aggregated) in the request params
to gR()?

Mit freundlichen Gruessen / best regards,

        Richard Jacob
______________________________________________________
IBM Lab Boeblingen, Germany
Dept.8288, WebSphere Portal Server Development
WSRP Technical Lead
WSRP Standardization
Phone: ++49 7031 16-3469  -  Fax: ++49 7031 16-4888
Email: mailto:richard.jacob@de.ibm.com


                    
                     
                     
          
             Stefan Hepper    
                     
                     
             <sthepper@hursley  
                     
                    
             .ibm.com>      
                     
                     To
                    
                  Subbu Allamaraju
<subbu@bea.com>    
             07/25/06 05:00 PM    
                     
               cc 
                    
                  WSRP TC
<wsrp@lists.oasis-open.org> 
                    
                     
                     
  Subject 
                    
                  Re: [wsrp]
Public review comment:   
                    
                  Remove markup
restrictions for      
                    
                  getResource
                     
  
                    
                     
                     
          
                    
                     
                     
          
                    
                     
                     
          
                    
                     
                     
          
                    
                     
                     
          
                    
                     
                     
          




yes, this would be fine with me.

Stefan

Subbu Allamaraju wrote:
> Rich Thompson wrote:
>>
>> It is not always true that the restrictions from 10.4 do not apply
as
>> the use the portlet's markup will make of the returned resource
>> matters. If it is inserting it into the aggregated page, the
>> restrictions apply. If it is inserting it into an IFrame or separate
>> window, then they would not. Would adding a statement into section
6.3
>> to this effect be appropriate?
>
> I agree. We could make this subjective and base it on how the
> markup/resource is being presented to the client.
>
> Subbu
>
>>
>> Rich
>>
>>
>> *Stefan Hepper <sthepper@hursley.ibm.com>*
>>
>> 07/25/2006 03:38 AM
>>
>>
>> To
>>     WSRP TC <wsrp@lists.oasis-open.org>
>> cc
>>
>> Subject
>>     [wsrp] Public review comment: Remove markup restrictions
for
>> getResource
>>
>>
>>
>>
>>
>>
>>
>>
>> Currently the WSRP spec does not distinguish in the section 10.4
between
>> getMarkup calls and getResource calls.
>> Given that the response from getResource will not be aggregated
I think
>> the restrictions mentioned in 10.4 should only apply to getMarkup
calls.
>>
>> Stefan
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this mail list, you must leave the OASIS TC
that
>> generates this mail.  You may a link to this group and all
your TCs in
>> OASIS
>> at:
>> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>>
>>
>
> _______________________________________________________________________
> Notice:  This email message, together with any attachments, may
contain
> information  of  BEA Systems,  Inc.,  its subsidiaries
 and  affiliated
> entities,  that may be confidential,  proprietary,  copyrighted
 and/or
> legally privileged, and is intended solely for the use of the individual
> or entity named in this message. If you are not the intended recipient,
> and have received this message in error, please immediately return
this
> by email and then delete it.
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  You may a link to this group and all your
TCs in
> OASIS
> at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>
>



---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  You may a link to this group and all your TCs
in
OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php




---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  You may a link to this group and all your TCs
in OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php