Re: [wsrp-interfaces] Multi-section rendering (Renamed)

[Stefan Hepper <sthepper@hursley.ibm.com>]

Hi Nate,
not sure if these questions have been asked already, but if so I don't 
remember the answer ;-) :
- what would the consumer expect to receive in the body section? Is this 
what the producer would normally return from a gM call?
- why are base and title tags excluded? There may be use cases for the 
title tag, e.g. you have one main portlet on the page that takes up 80% 
of the space and want to allow this portlet to set the overall page title

Stefan

Nathan Lipke wrote:
> Attached is the latest (mostly just incorporating Rich’s changes and 
> comments). I would like to focus tomorrow’s discussion on resource sharing.
> 
>  
> 
> Thanks,
> 
>  
> 
> Nate
> 
>  
> 
> ------------------------------------------------------------------------
> 
> *From:* Rich Thompson [mailto:richt2@us.ibm.com]
> *Sent:* Thursday, November 15, 2007 12:28 PM
> *To:* wsrp-interfaces@lists.oasis-open.org
> *Subject:* RE: [wsrp-interfaces] Multi-section rendering (Renamed)
> 
>  
> 
> 
> I turned on track changes to suggest a bunch of editorial level changes.
> 
> I haven't had time to dig into the type definitions yet, but will try to 
> get to them in a separate pass.
> 
> My biggest concern is with section 11.3.2.4 as it sets up sharing at a 
> section level while providing an example of sharing at a resource level. 
> This seems like a mismatch that we ought to address though I do not have 
> a suggestion on how to address it at the moment. Perhaps a variant on 
> Mike's earlier proposal would make sense.
> 
> 
> 
> Rich
> 
> From:
> 
> 	
> 
> "Nathan Lipke" <nlipke@bea.com>
> 
> To:
> 
> 	
> 
> <wsrp-interfaces@lists.oasis-open.org>
> 
> Date:
> 
> 	
> 
> 11/14/2007 10:46 PM
> 
> Subject:
> 
> 	
> 
> RE: [wsrp-interfaces] Multi-section rendering (Renamed)
> 
>  
> 
> ------------------------------------------------------------------------
> 
> 
> 
> 
> Here’s my latest crack at it.
>  
> Nate
> 
> 
> 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.[attachment 
> "multiSectionRendering-singleRequest.doc" deleted by Rich 
> Thompson/Watson/IBM] 
> ---------------------------------------------------------------------
> 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