[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: [wsrp][markup] Minutes for 6/06 conference call
Second try.
|
Sub-Committee Lead Chris Braun
Attending Members: Alejandro Abdelnur Jeff Broberg Jane Dynin Gino Filicetti Michael Freedman David Taib Rich Thompson
A. URL Rewriting Scenarios:
Discussion: Scenario’s #2 & #4 can refer to as scenarios of choice.
Action: Review Main Document rev .3, members should provide input, especially URL rewriting, list pros/cons of scenarios. Especially for scenarios 2 and 4.
B. URL Types:
It is worthwhile to break down the process into four steps. For each step lets try to identify how the URLs are handled and how these translate on both ends of the equation.
Flow using “URL Rewriting Scenario 2”
Rich will send out an email to get the discussion started on possible approaches to each.
Proxy Resource Links: Dynamic content may be proxied. In this case the content may be session based. How is the session information passed from consumer to the dynamic resource provider? Also, may want a way for portlets to indicate that resources should be cached and when a resource has been updated.
Actions to Other WSRP: If you had multiple portlets it would be nice to utilize one. Example: contacts – email portlet. Ability to send email that activated other portlets. Response sent back to portlet. Contacts portlet would have exposed an item and request routed to contacts portlet – self activated. Needs more thought. We should discuss this further.
C. CSS Classes:
Nix ‘Table’ section and move it into ‘Section’ area.
Assume trail is analogous to paragraph.
No modifications.
We added some menu classes such as background. Need some clarification as to weather cascading menus can be removed assuming that the menu classes can take the cascade menus place.
We decided that there is no need for general portlet css classes and that section classes can be used to represent a portlet’s content. Might be worthwhile to identify possible use cases in which a portlet may need its own classes that are different from the section.
This is a valid problem however CSS may not be powerful enough to solve it. Let’s come up with a list of use cases and a possible prototype where CSS might be able to help solve this issue. If this does not seem viable we can try to address this in a later spec version.
7. Other
· Position · Media Properties · Background properties · Margins · Spacing
General consensus was that these areas can be addressed by using the other classes. Would like more information on these before we remove them to make sure this is the case.
|
Attachment:
Minutes-June-5.doc
Description: MS-Word document
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC