From: "Vesey, Scott R" Your experience in the areas covered by the Workshop scope (W3C technologies testing, etc) I am currently responsible for testing, evaluating, and making recommendations regarding Windows web browser technology for the Boeing Company. In this capacity, I create sample code and test suites to demonstrate interoperable techniques and test browser conformance. I am frequently called upon to analyze why web applications fail. I have a particular pet peeve about "Best if viewed by .." web sites. What are the needs of your company/organization in the field of Web/W3C QA. One of the most problematic parts of using the web is ensuring accessibility and interoperability. The Boeing Web team views one of the primary benefits of the web to be the ability to place a single document or application in a single location and allow virtually anyone to access it. For a huge company with millions of internal web pages and applications, interoperability becomes mandatory. We believe that one of the best ways to ensure long term interoperability is to base our efforts on W3C standards. Our team has spent significant effort defining Boeing Web interoperability guidelines. These guidelines are intended to provide a rough framework for approaching developing web content and applications to be interoperable. We believe, and our chief architects have affirmed, that designing for interoperability today will allow applications to function in the future with less conversion effort as the environment, tools, and techniques change. What are your general expectations on the final outputs of the workshop? I would like to see additional emphasis on test suites and examples in the specification process. I believe that there are a number of ways that this could be accomplished. Lacking test suites and examples that are part of the specification will continue to drive inconsistencies in practical implementations. While there are many third-party test suites I believe that there should be an authoritative test suite that has the approval of the W3C. This type of test will not entirely eliminate the problems that can occur, but I believe that it could improve the situation. What are your potential contributions to the discussion, related ideas, and suggested solutions? A well-defined technical contribution may accompany the position paper as an appendix. In my role at Boeing I get many questions about HTML and CSS syntax. Specifically, people frequently send be questions about why some HTML or CSS code does not work correctly. Rather than create individual samples for each of these requests I created a pair of tools called the HTML 4.0 generator and the CSS 1 generator. These tools dynamically create tests and if results have been recorded, the tools display which browsers are known to support the specific elements and attributes being tested. The HTML 4.0 generator allows you to select any HTML element and list all of the valid attributes for that specific element. Then you can select specific attributes and values for the attributes and generate a sample that is rendered by the web browser. Additionally, the database records tests and lists the capabilities of the browsers that have been tested. The CSS generator allows you to select appropriate HTML elements and list all the valid CSS attributes. This tool is not as complete as the HTML generator but has the ability to record browser capability. IT would be possible to demonstrate these tools at the workshop, if there is an interest.