OASIS Web Services Interactive Applications TC

 View Only
Back to discussions
Expand all | Collapse all

Re: WSIA 5/21/2002: [wsia][wsia-requirements][R905 and 601]

  • 1.  Re: WSIA 5/21/2002: [wsia][wsia-requirements][R905 and 601]

    Posted 05-22-2002 10:23 
     MHonArc v2.5.2 -->


















    wsia message
    







    [Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [Elist Home]
    


    







    Subject: Re: WSIA 5/21/2002: [wsia][wsia-requirements][R905 and 601]
    







    



    
Not sure that I parsed your notes correctly, but I see the phrase
"Consumer with multiple Producers?  Need justification."  Doesn't
the simple portal scenario provide this?  If not, the "SmartBuyer"
scenario certainly does.

Suggested rewording:

Consumer's MUST be able to construct documents containing multiple
Presentation Fragments from one or more Producers.  The specification
MAY place restrictions on the supported markup types or Presentation
Fragments.


I don't think we need to say any more than this.  Other requirements
about the division of labor between Consumer and Producer will guide
the specific mechanisms provided to support this requirement.

Sean

At 05:43 PM 5/21/2002 -0700, Monica Martin wrote:
>Several ideas:
>
>Composition of presentation fragments onto a page
>
>Composition of different presentation fragments onto a page
>
>Composition of different presentation fragments generated by a producer
>(May be the same as above)
>
>Restrictiions on presentation fragments (or markup types)
>
>Guarantee uniqueness of tokens in a single document defined by the
>presentation format
>
>
>
>
>
>E905 and E601
>
>Notes: [mm1: Namespace entity rewriting Javascript; Consumer with
>multiple Producers? Need justification. Include with presentation
>fragments (Consumer passes Producer a key).]
>
>
>
>Suggested text:
>
>Different Presentation Fragments SHOULD be capable of being combined in
>a single document. Restructions MAY be specified on markup types or
>Presentation Fragments.  In particular, if a presentation format (such
>as HTML) mandate uniqueness of tokens in a single document, a page
>SHOULD be composed in a way that guarantees uniqueness. In particular,
>Presentation Fragments generated by the same Producer SHOULD be capable
>of being composed.
>
>
>
>Comments and arrows welcome.
>
>Thanks.
>Monica J. Martin
>
>Program Manager
>
>Drake Certivo, Inc.
>
>208.585.5946
>
>
>
>


Related Content