[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [wsrp-primer] Markup interface
Some comments from Rex during last week's call: a. It is good idea to set the motivation. b. But it is inconsistent to emphasize the motivation with sub-headings c. Should discussion on nav state belong the markup section? I'm posting these comments to the list to seek some comments/suggestions. Personally, I do think that we should set the motivation before getting into details. I also agree with Rex that it may be inconsistent to draw out subheadings for setting the motivation. Given this, how about saying the same points without over emphasizing with headings? I think we can still achieve the same objective without. On the third point, based on the questions from portlet developers, navigational state is an often confusing concept for non-portal web developers. I personally think that the markup section motivate the reason behind navigational state, and then show how can be used. The messages I posted already illustrate navigational state. Regards, Subbu Rich Thompson wrote: > > Based on questions I receive, it would be good to add a section > describing usage of the CSS classes ... presuming someone will volunteer > to author it of course. > > Rich > > > *Subbu Allamaraju <subbu@bea.com>* > > 06/10/2004 09:30 AM > > > To > wsrp-primer@lists.oasis-open.org > cc > > Subject > [wsrp-primer] Markup interface > > > > > > > > > Based on the review comments we have had so far, I took a stab at > refactoring(?) the markup section. The outline is attached (includes > updated messages). I would like to hear your comments. Based on your > comments, we can pull the content from the current draft and expand. > > Regards, > > Subbu >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]