OASIS Web Services Interactive Applications TC

RE: [wsia][wsia-requirements][E905]

  • 1.  RE: [wsia][wsia-requirements][E905]

    Posted 05-06-2002 14:30
     MHonArc v2.5.2 -->
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    

    wsia message

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


    Subject: RE: [wsia][wsia-requirements][E905]


    Title: Message
    I also support the usage of must in this case.
     
    The question of fragments generated by the same Producer (= WSIA Web Service) relates to the "harder" case where you need to place two services of the same service on the same page (e.g., two stock quotes):
    - The reason why this "harder" is because one can't assume a "static" unique token (such as a namespace or a prefix) to ensure uniqueness.
    - The need for this requirement is clear; its importance is not completely obvious; there seems to be a strong sentiment in this committee (including myself) that it's important enough to consider.
     
    How about the following: emphasizing that there could also be multiple services, but also a single one:

    This specification MUST provide a mechanism that ensures that different presentation fragments (generated either by multiple WSIA
    Web Services or by a single one)
    can be "safely" combined to a single document. In particular, if a presentation format (such as HTML) mandates uniqueness of tokens in a single document, it MUST be possible to compose a page in a way that guarantees uniqueness.