c2m-project
[Top][All Lists]
Advanced

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

[C2m-project] phenomenally


From: Flossie Gay
Subject: [C2m-project] phenomenally
Date: Sun, 1 Oct 2006 10:35:45 +0200
User-agent: Thunderbird 1.5.0.7 (Windows/20060909)


It is definitely clear that is not the job of the QA IG to fix this document, but XML Core WG role. The framework will have to give hints on strategies for change. The format is quite interesting and gathering the knowledge about one particular topic of Web architecture. The comments being open, it also gives an opportunity to add information to the post. He made a few points in his message which will be certainly discussed by the Web communities in the following days.
Software is developed upon technologies that are freely accessible and implementable on a royalty free basis.
It is definitely clear that is not the job of the QA IG to fix this document, but XML Core WG role.
The article contained a simple RDF schema for this model. The WASP is now interested in developing a kind of curriculum framework to help lecturers into their teaching.
The format of the package has not yet been decided, but it has to be international then we need to understand how universities function around the world. There are rules, driving the development of specifications.
When implementations of the same feature differ, it can mean that the specification is ambiguous, that the test is wrong, or that one or more implementations are incorrect.
We have to make very clear that it's not a way to collect issues about Web architecture document itself.
it helps harmonization of vocabulary accross specifications and maintains regularity.
As always we have much more work to do than we have people to do it, so we would very much welcome assistance from people in the conformance testing community.
If a test case for a particular feature is difficult to conceive, it often means that the feature is too complex, or that the prose describing the feature is too ambiguous.
He has, for example, just accepted a role as invited expert within the CSS working group.
There are rules, driving the development of specifications.
When there will be issues which seems more difficult to overcome, we will explain the solution we have found and adopted to solve them. The framework will have to give hints on strategies for change.
Certification is a legal process between two parties. After discussion in the QA Team, we thought about developing a Weblog for the QA home page.
People can voice their disagreement, pushing their issues. A simple guide to write test assertions has then been a requirement. As always we have much more work to do than we have people to do it, so we would very much welcome assistance from people in the conformance testing community. It remains a closed, a one-way system. The document could end up as a FAQ to write test assertions. It is definitely clear that is not the job of the QA IG to fix this document, but XML Core WG role.
We may receive an email or read a news which raises an interesting question to be develop in a longer post.
People can voice their disagreement, pushing their issues. We have to make very clear that it's not a way to collect issues about Web architecture document itself.


reply via email to

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