Rex,
As I was about to update the messages with realistic markup, I realized
that the Markup section does not include the following:
a. initCookie, its intent
b. Session life cycle and releaseSessions
c. Descriptions of various elements in getMarkup/pbia requests and response.
d. Markup rewriting, and some introduction to templates.
Are these topics in your list?
I was going to create a simple page that includes a simple href, an
image, and a form, so that this section can talk about markup rewriting,
interactions, and resources.
However, I don't feel comfortable adding just the markup since it still
leaves some holes in this section. What is your intent?
I have just uploaded a cleaner version of the current draft (this
includes clean up of service description, registration and portlet
management sections).
Regards,
Subbu
said the following on 02/09/2004 08:15 AM:
> The document wsrp-primer-1.0-draft-0.42.doc has been submitted by Rex
> Brooks () to the WSRP Primer SC document repository.
>
> Document Description:
> I reconciled Alan's v.41 with my previous v.41-s-r and filled out Modes
> and Window States in Markup Interface Section. We still need the
> message with Registration so that I can fill out that remaining section,
> and if we also have the messages for modes and window states, if we want
> to include that in the Primer (not sure it's not 'too much' for a
> primer), that would be good, too.
>
> However, I would like to go ahead and ask Subbu to go ahead and make the
> deletion of the excess wsrp-specific additions I made in the basic
> scenario so we can wrap that section up.
>
> I did change the TOC to reflect the change of Registration to follow
> Service Description.
>
> Ciao,
> Rex
>
> Download Document:
> http://www.oasis-open.org/apps/org/workgroup/wsrp-primer/download.php/5369/wsrp-primer-1.0-draft-0.42.doc
>
>
> View Document Details:
> http://www.oasis-open.org/apps/org/workgroup/wsrp-primer/document.php?document_id=5369
>
>
>
> PLEASE NOTE: If the above links do not work for you, your email
> application
> may be breaking the link into two pieces. You may be able to copy and
> paste
> the entire link address into the address field of your web browser.
>
>
