- From: Karl Dubost <karl@w3.org>
- Date: Sun, 14 Nov 2004 15:46:33 -0500
- To: lsr@nist.gov
- Cc: www-qa-wg@w3.org
- Message-Id: <44C681FC-367E-11D9-AB55-000A95718F82@w3.org>
Hi Lynne, do you remember this point, You have rewritten the techniques with Mark which is great. I have an action item to redraft… though I'm not sure what's the meaning of redrafting. For the Ruby Diagram I think it's ok. I will follow the techniques you have written ;) big test. Le 29 oct. 2004, à 08:31, lsr@nist.gov a écrit : > 1.1B > Need much work to draft. > Identify in the spec, what are the different parts that may vary (e.g., > profile, module, level). Things that have an effect on conformance > model > Perhaps start with a technique for handling the simple case > 1. – List the classes of products – what it is that would conform > 2. – List the types of flavors of conformance > 2. – List the different ways to subset the technology > 4.– define the mapping between subsets and flavors of conformance > 4a draw a diagram to show the mapping – this will help to show the > relationships and understand > 4b write it down > 4c. bonus: include the diagram if it helps > need an example that shows all these steps > ACTION: Karl to redraft and draw the diagram for Ruby
Received on Monday, 15 November 2004 00:58:40 UTC