info-gnuts
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Info-gnuts] trunks


From: Edna Finch
Subject: [Info-gnuts] trunks
Date: Tue, 17 Oct 2006 18:13:37 +0100
User-agent: Thunderbird 1.5.0.7 (Windows/20060909)


We will use the Wiki to collect issues from people about identified HTTP implementation problems using the Web Architecture document as a framework for collecting issues. Although finding a design company that will construct a standards compliant site is more difficult than just finding a web designer, the benefits speak for themselves.
In some cases, for instance on shared computers or "internet kiosks", the user is not even allowed to change the settings of the Web browser. The public output has been in the forms of interviews.
The document defines a minimal set of metadata elements that can usefully be applied to tests that are intended for publication within a test suite. We have to make very clear that it's not a way to collect issues about Web architecture document itself.
The framework will have to give hints on strategies for change.
It is definitely clear that is not the job of the QA IG to fix this document, but XML Core WG role. The WASP is now interested in developing a kind of curriculum framework to help lecturers into their teaching.
Now people have understood that this is just a tool. In some cases, for instance on shared computers or "internet kiosks", the user is not even allowed to change the settings of the Web browser. It has been mentionned that would be possible only if the document is publicly available. They highlight some common implementation issues in user agents and HTTP-based softwares. Her time is too limited. Or maybe you would like to give the price of a product with values in two currencies?
Some Web Standards User groups are forming at key Universities and Colleges to provide and advocate a method for change - WaSP Edu is providing interviews with these as they find out about them. We have to make very clear that it's not a way to collect issues about Web architecture document itself.
When you are dealing with a supplier, a provider, you need absolutely to get a product of quality.
The Markup validator mailing list has several hundred subscribers. Mobile Best Practices might be one canditate, and ERT WG with EARL might be another possible implementation of this language.
It provides a list of simple requirements that you could add to your Web site requirements document when negociating with Web agencies.
We may receive an email or read a news which raises an interesting question to be develop in a longer post.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]