RE: [wsrp][markup]Markup document (updated revision)

[Gino Filicetti <gfilicetti@bowstreet.com>]

David...

We need to include all 4 of the URL rewriting scenarios that are now on the
table in this doc under section 5.2.. They currently are:

Scenarios:
1. Aggregator sends a prefix w/ request and portlet must use it to do the
URL boundary demarcation. The aggregator then parses the markup looking for
the prefix it provided.

2. All portlets use a predefined prefix which is part of the spec to
demarcate URL boundaries. The aggregator then parses the markup looking for
the well known prefix.

3. The aggregator automatically parses markup and heuristically determines
URL boundaries and does the necessary rewriting automatically.

4. The aggregator sends the remote portlet the URL information that it needs
and
the remote portlet rewrites all the necessary URLs itself. The markup it
sends 
back will then be ready for immediate inclusion in the page, no parsing
necessary

Also, we should list out the pros and cons for each scenario that were
discussed last week and are captured in last week's minutes. And we should
make specific reference to the consensus that a combination of scenarios 2
and 4 seems to be the way to go.

Other than that the document looks great!

G

> -----Original Message-----
> From: David Taieb/Cambridge/IBM [mailto:david_taieb@us.ibm.com]
> Sent: Friday, May 10, 2002 3:36 PM
> To: wsrp@lists.oasis-open.org
> Subject: [wsrp][markup]Markup document (updated revision)
> 
> 
> Hi All,
>       Here are the latest version of the Markup master 
> document based on
> the latest concall
> Regards,
> (See attached file: WSRP Markup.doc)(See attached file: WSRP 
> Markup.htm)
> David Taieb
> Advisory Software Engineer
> Lotus Software, IBM Software group
> One Rogers Street
> Cambridge, MA 02142
> Tel : (617) 693 5819
> Fax : (617) 693 5542
>