OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

wsrp-primer message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [wsrp-primer] Groups - wsrp-primer-1.0-draft-0.42.doc uploaded

Hi Subbu,

I don't have a list. My intent was to work from the messages you 
supply for getMarkupResponse, with and without registration. Your 
list can be added if you think its important to a Primer. If it is 
included, then it should be in the messages. I will keep it as simple 
as I can.

I expected the portlet we show to have some simple css classes, one 
or more images and (not necessary) an interactive element, like a 
stock quote update request and/or a different view, such as a edit or 
help mode or a trade request form. Since you mention a form, go for 
it. I wouldn't get more complex than that, and I am not sure if we 
should have more than one interaction. My plan all along has been to 
write short descriptions of the elements that were included in the 
messages. Your simple page makes perfectly good sense. I think you 
are right, and we should include initCookie, lifecycle, 
releaseSessions, getMarkup/performBlockingInteraction, but if you 
think we should include Markup rewriting and some template, you 
should include them in the messages and the sample because I think we 
should show it if we talk about it. If you think we have holes in the 
section, you can either put in a placeholder with a note to me, or 
just describe it. Any writing you can do is going to be a big help 
for me with my tendinitis, which is getting worse. This could turn 
into a bigger problem.

BTW, shouldn't Message 16 Service Description Response (with 
Registration) be MarkupResponse (with registration? I would prefer 
you to include that in your v0.43.

Sorry for any extra work this is causing for you. The more I think 
about it, the more I wonder about getting so complex in a Primer. 
However, I leave it to your judgement, since that could be my 
tendinitis talking for me. This is really a nuisance.


At 9:49 AM -0700 2/16/04, Subbu Allamaraju wrote:
>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).
>rexb@starbourne.com 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 (rexb@starbourne.com) to the WSRP Primer SC document 
>>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.
>>Download Document: 
>>View Document Details:
>>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.

Rex Brooks
GeoAddress: 1361-A Addison, Berkeley, CA, 94702 USA, Earth
W3Address: http://www.starbourne.com
Email: rexb@starbourne.com
Tel: 510-849-2309
Fax: By Request

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]