tag message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Action Items !!
- From: "Durand, Jacques R." <JDurand@us.fujitsu.com>
- To: "TAG TC" <tag@lists.oasis-open.org>
- Date: Thu, 3 Apr 2008 18:49:25 -0700
Summary of Action
Items from last F2F: (we need to show progress on these by Wed Apr 16th
meeting)
---------------------------------------------------------
Youngkon
Lee:
- refine the use
case illustrating possible use of a fourth value for the new "perscription
level" TA element, besides the three basic values: mandatory / preferred /
permitted.
(develop on what YL
called "regulation" in his example that uses a MAY statement for a set of
alternatives: that in fact is also an implicit MUST NOT use anything outside
these alternatives. Can we define more generally this normative
pattern?)
Patrick
Curran:
- propose a wording
for explaining that the value of a predicate has always a more definite meaning
when "false" than when "true" (requirement violation can always be certain with
"false", while requirement fulfillment with "true" has only value as an
indication of conformance)
- propose a split in
Glossary between central notions ("in scope") and peripheral notions (out of
scope). Any other glossary update?
Paul
Rank:
- propose the right
level way to introduce succinctly the other "optional" TA elements in new
Section 2.
- also propose a
definition for the new essential TA element: "prescription
level"
- propose a write-up
for "specification version" new section 3.6.
- draft the new
section 3.3 Various
Normative Sources
Stephen
Greene:
- among other edits,
move the "Prerequisites" section under Advanced Features (as
3.2).
- investigate
"Negative testing" cases, and see if we can justify cases where TA predicate =
"true" means : requirement violation.
- reorganize the
guideline structure along recommendations from F2F (see previous email titled:
"Summary of new Guideline structure")
-
propose an update
for "Grouping" - see i025. Grouping case(s) that does not use
tags?
Jacques
Durand:
- propose how TA
Prerequisites can support new section 3.4.2- Specifications depending on each other. (extension to
content of Prerequisite element?)
- draft subsection 3.5.1 on "TA Target classes",
investigate external work on this.
- attempt at a more convincing case for issue 020
(subprime TA predicates)
Serm Kulvatunyou:
- Update a propose mark-up draft (XML schema and
example) from the latest TA structure.
Possible external contribution
:-)
- 3.7 Variables and Target Properties (use of variables inside a TA,
use cases)
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]