Sect. 3.1 "Optimization of data transfer" You need to give a little more information. WAP includes _replacements_ for HTTP and TCP that are specifically designed for the wireless environment, right? It also includes some security features. 3.2.1 List WML tags and give a brief explanation of them. Assume reader has a basic familiarity with HTML, so you can explain relative to that. 3.2.2 Provide more detail about WMLScript capabilities/functionality. Probably list the elements of the language (at least the most important one). Do NOT assume reader knows JavaScript -- I want to assume we have someone with only th emost basic familiarity with the web (mainly HTML). 3.2.3 Describe in more detail the capabilities and features of the standard user agent. I think you talked about "Services and Formats" mostly in the preceeding sections, right? I don't think you need to mention them here, but you might have a short section just to tie up loose ends (i.e. brief description of the bitmap format and any other formats that are codified in the WAP documents). 3.3 I'm more interested in the layers that replace HTTP and handle security. As far as bearers go, I think it is sufficient to say that WAP essentially works on top of all bearers currently in use throughout the world. I think such a statement can be put in 3.1 instead of in a separate section. Sections 4, 5, 6: In section 3 you should have provided a basic description of the features/capabilities/limitations of WAP. Now we want to compare these with their counterparts in the "fixed internet" world. The point here is that if we were to design a complicated software system in the fixed internet world, we'd use XML, HTML, JavaScript, Java, etc. So we want to understand how the tools provided by WAP compare in order to better understand if we can build our big complex software system to work with WAP or not. Section 5: I'm primarily interested here in a comparison of the HTTP-level transport protocols and security features. Does WAP have the equivalent of SSL? What does it offer in terms of user authentication (as HTTP offers "basic" authentication via htaccess and htpasswd, and in special (non-standard) cases more sophisticated things like Kerberos)? Is WAP's transport protocol (I don't know the name) like HTTP 1.0? 1.1? What capabilities does the WAP side not offer, or what additional features are provided? Section 6 is meant to provide a place to say how others (primarily PDAs) are providing web access. If I have a WinCE machine with Internet Explorer, presumably I'm browsing the web directly. That means no special markup, no attempt to compress data (unless it is done at lower levels), and I have a browser that has some or all of the capabilities I would find on desktop IE (Java? JavaScript?). I believe on the Palm, off-line readers predominate. There are also Palm VII PQA. I would focus on trying to fill in the sections pretty much in order, because it should build logically & you should not have to repeat yourself much this way. I am happy to help you at any point along the way. I think you probably should be able to do 3 on your own, and shouldn't require much more than guidance frmo me on 4-6. 7 and 8 we can discuss in more detail after you get up through 6 in good shape. Its a good start, and I'm excited that it will turn out to be a very nice report. Thanks, David -- David E. Bernholdt | Email: bernhold@npac.syr.edu Northeast Parallel Architectures Center | Phone: +1 315 443 3857 111 College Place, Syracuse University | Fax: +1 315 443 1973 Syracuse, NY 13244-4100 | URL: http://www.npac.syr.edu