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

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsrp-markup message

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


Subject: [wsrp-markup] [wsrp][markup] Conf Call Agenda Today


Added more information to the agenda.
 
Agenda:
 
1. URL Rewriting - Semantics and Syntax
2. Visual Themes CSS Classes - Review
 
Items to be covered:
1. URL Rewriting  - Review Rich's suggestions regarding possible rewriting scheme.
 
    1.1 Action URLs
        1.1.1    Consumer Rewriting (Scenario 2)
 
            -  Should the prefix be a static token or be set via a property?
            -  Should we specify how the tokens should be parsed?
            -  How are parameters passed?
            -  Is ActionName a well known property or is it just a parameter?
        
 
        1.1.2    Producer Rewriting (Scenario 4)
            -  How does the producer decipher how to write the URL when including parameters.  Some consumers may use query params, some may
                use path information. 
            -  Define property names for URL pieces.
 
        1.1.3  How Consumer Determines Which scenario to use
            Proposal:
            - Producer property set includes predefined names if it is willing to use option #4.
            - Consumer metadata indicates whether it is prepared to do URL rewriting (option #2)
            - Compliant Consumers MUST either set template properties OR indicate a willingness to rewrite URLs.
            - Producer options when defining the template properties then become:
                  - If Consumer set template properties AND indicated it is willing to rewrite URLS, Producer may choose either option.
                  - If Consumer set template properties AND indicated it will not rewrite URLs, Producer must use option #4
                  - If Consumer did not set template properties AND indicated it is will to rewrite URLs, Producer must use option #2
                  - If Consumer did not set template properties AND indicated it will not rewrite URLs => non-compliant Consumer.
                  - Producers not defining the template properties require that their Consumers support URL rewriting & use option #2

 
 
    1.2 Proxy and Relative URLs
         - Base URL must be provided in producer meta data.
         - Should be able to specify if the resource can be cached
         - Should be able to specify if the Consumer should rewrite URLs embedded in the resource.  For example: a JavaScript file.
 
        1.2.1    Consumer Rewriting (Scenario 2)
           
        1.2.2    Producer Rewriting (Scenario 4)
            - Need well know query parameter so that producer can indicate if caching should be turned on.
 
    1.3 Relative URLs
 

2.  CSS Classes

 

    Review All - Please Review the Latest CSS document with Carsten's comments.

 



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


Powered by eList eXpress LLC