[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [oic] Test Assertions and Test Cases
Rob, 1. I think there is some level of activity at the TAG TC. It is a small TC, but the latest documents are this year. I think liaison and piloting is a good idea. 2. I think SHOULD (in the IETF sense) and MAY end up with the "preferred" and "permitted" prescription levels, respectively. 3. That's an interesting idea about normative source. This would impact the identification of target too. We should hold that thought. I've given the TAG cd3 a quick once-over and need to take a closer look next. - Dennis -----Original Message----- From: robert_weir@us.ibm.com [mailto:robert_weir@us.ibm.com] http://lists.oasis-open.org/archives/oic/200904/msg00007.html Sent: Tuesday, April 07, 2009 13:01 To: oic@lists.oasis-open.org Subject: RE: [oic] Test Assertions and Test Cases "Dennis E. Hamilton" <dennis.hamilton@acm.org> wrote on 04/07/2009 03:33:12 PM: [ ... ] I was thinking that would just be a difference in "Normative Source". So something that is a "shall" according to the ODF standard would have prescription level "mandatory" and would reference the ODF standard as the Normative Source. But something that was a recommendation of the ODF Accessibility Guidelines would have prescription level "preferred" with "ODF Accessibility Guidelines" as the normative source. In other words, the prescription level is relative to the normative source. That way we can filter the complete set of test assertions. Ones where the normative source are the ODF standard and the prescription level is mandatory would comprise the conformance test. Note also the importance to TAG of the "prerequisite" item. The name lead me astray at first. I thought it referred to test setup procedures. But it is really an indication of when the test is relevant. So you can define a TA so that it applies in only certain situations. This is important for ODF because most elements are optional. But where they are used they may have stated syntactic or behavioral constraints. So the TAG framework allows us to express this. Do you get the impression that the Test Assertion Guidelines TC is actively working? If so it might be worth while establishing a liaison, or at least closely observing their work. We might be able to pilot some of their work and give feedback. -Rob --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]