Re: [wsrp] Producer writing - clarification

[Richard Jacob <richard.jacob@de.ibm.com>]

agreed

Mit freundlichen Gruessen / best regards,

        Richard Jacob
______________________________________________________
IBM Lab Boeblingen, Germany
Dept.8288, WebSphere Portal Server Development
WSRP Team Lead & Technical Lead
WSRP Standardization
Phone: ++49 7031 16-3469  -  Fax: ++49 7031 16-4888
Email: mailto:richard.jacob@de.ibm.com


                                                                           
             Subbu Allamaraju                                              
             <subbu@bea.com>                                               
                                                                        To 
             01/18/06 04:37 PM         Rich Thompson <richt2@us.ibm.com>   
                                                                        cc 
                                       OASIS WSRP TC                       
                                       <wsrp@lists.oasis-open.org>         
                                                                   Subject 
                                       Re: [wsrp] Producer writing -       
                                       clarification                       
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           




Rich Thompson wrote:
>
> I see ... I miss understood the request. To recap, we currently have:
>
> 1. The Producer replaces spec-defined tokens (including enclosing curly
> braces) with appropriate values, using the empty string if the Producer
> has no value.
>
> The proposal is to add:
>
> 2. The Producer treats any content between curly braces which do not
> match spec-defined tokens as constants (much like the text outside the
> braces).
>
> Question: Wouldn't this limit the ability for an extension to define
> additional tokens? Would it suffice to relax the request to "unknown
> tokens" rather than "spec-defined tokens"? Or would that open too many
> holes ...

Good catch. I agree. Unknown is enough.

Subbu


>
> *Subbu Allamaraju <subbu@bea.com>*
>
> 01/18/06 09:10 AM
>
>
> To
>            OASIS WSRP TC <wsrp@lists.oasis-open.org>
> cc
>
> Subject
>            Re: [wsrp] Producer writing - clarification
>
>
>
>
>
>
>
>
> I noted that. The new statement talks about replacing unknown but
> spec-specified tokens with "". I'm referring to braces that may contain
> arbitrary characters. Such content should be treated as constants since
> they may contain instructions for the consumer or user-agent to process.
>
> Subbu
>
> Rich Thompson wrote:
>  >
>  > We already had that discussion and added the following conformance
>  > statement to v2 (section 10.2.2; line 3879 in draft 13 - two sentences
>  > before the conformance statement you quote):
>  >
>  > These tokens are enclosed in curly braces (i.e. “{” and “}”) and
contain
>  > the name of the portlet URL parameter which the Producer MUST replace
>  > (using "" for those parameters where the Producer has no value).
>  >
>  >
>  > Rich
>  >
>  >
>  > *Subbu Allamaraju <subbu@bea.com>*
>  >
>  > 01/17/06 01:06 PM
>  >
>  >
>  > To
>  >                  OASIS WSRP TC <wsrp@lists.oasis-open.org>
>  > cc
>  >
>  > Subject
>  >                  [wsrp] Producer writing - clarification
>  >
>  >
>  >
>  >
>  >
>  >
>  >
>  >
>  > Currently, we have a conformance statement in page 93 of draft 13
which
>  > reads as
>  >
>  > "All content outside the {} pairs MUST be treated by the
>  > Producer/Portlet as constants the Consumer needs to receive when the
>  > portlet URL is activated."
>  >
>  > I would like to suggest additional wording to say that if content
within
>  > a {} pair does not match spec defined replacement tokens, the Producer
>  > should treat such content similar to the content outside {} pairs.
>  >
>  > Such a statement would go the extra mile in clarifying that consumers
>  > might use braces in templates in ways not defined in the spec.
>  >
>  > Subbu
>  >
>  > ---------------------------------------------------------------------
>  > To unsubscribe from this mail list, you must leave the OASIS TC that
>  > generates this mail.  You may a link to this group and all your TCs
> in OASIS
>  > at:
>  > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>  >
>  >
>  > ---------------------------------------------------------------------
To
>  > unsubscribe from this mail list, you must leave the OASIS TC that
>  > generates this mail. You may a link to this group and all your TCs in
>  > OASIS at:
>  > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>  >
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  You may a link to this group and all your TCs in
OASIS
> at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>
>
> --------------------------------------------------------------------- To
> unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail. You may a link to this group and all your TCs in
> OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php


---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  You may a link to this group and all your TCs in
OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php