Conference call Jan. 14 2003

Alex Zamfirescu		ASC
Srinivas Madaboosi	Fujitsu
Balchandra Thatte	Sequence

10.1 canonical - replace by compact
10.1 behavior, statetable
Purpose is to specify the logic state space and the change in logic state
as a response to a given stimulus.
10.2 rewrite, put reference to 10.3 upfront
10.3 The variables ... are pin variables
according to table 73
eliminate "following" - ask Joe Daniels
rewrite this paragraph
Virtual means part of test environment
Figure 13: non-controlled * by the test algo
10.4 o.k.
10.5 explain: no reverse engineering of behavior from netlist
10.6 interpration of statetable: completeness, consistency
to be checked by application, if required
10.7 example o.k - is there any thing overlapping in STYLE (P1500)
10.8 use other symbols than LSB, MSB, here they are indices, not bits
10.9 make ref to paragraphs where operators, operations are explained
10.10.1 should reduced set be 0, 1, x, z?
10.10.2 remove table 75 and 76
use other symbol than LSB, MSB, use "right" and "left"
make it consistent with 10.8
substitute S with s(B-1)
10.10.3 o.k.
10.11.1 xor, xnor without "e"
put the rules instead of a reference
10.11.2 define "bitwise"
10.11.3 introduce ? as then_operator, : as else_operator in syntax 72
10.11.4 result of operation is value of operation applied to the value of operands
exceptions (overflow etc) are application-specific or user-defined

Conference call continued Jan. 15 2003

10.11.5 remove "in the rage between zero and the bitwidth"
reformulate: N bits of the LHS operand, starting from the right, shall be replaced...
10.11.6 introduce "integer" and "based literal" as well-defined for comparison.
.. by applying the mathematical operation to the values associated with the operand
19-21 If the value is not well-defined, the eval result shall be determined by the application.
23-25 Put conversion from based-literal to integer and consequence of not well-defined result
in leading paragraph.
46-48 Remove "Note", replace "can" with "shall"
Table 84: replace title: implication of drive strength within equal comparison
Table 84: replace "arbitrary" with "any"
Table 85: replace title: ditto
Table 85: replace "arbitrary" with "any"
A.I. look into "greater" operator - Alex

10.11.7: change "priority" into "precedence"
A.I. check for compatibility of precedence rules with Verilog - Joe Daniels

10.12 the purpose of a vector expression "is" to specify ...
remove "static" and "dynamic", replace "proposed" and "monitored" by "actually realized"
add sentence: details are explained in ...

10.13 add sentence: An event can occur only when at least one variable within the scope of
concern changes its value.

10.13.1 specify "the pattern of" a single event.
use the word "value" consistently, not "state".
Table 86: make all lines the same thickness.
17 reformulate the sentence, sounds like a paradox.

continued Jan.20

p.138, line 19: "arbitrary" need ref to row 3 in table 86
line 24: change to "while the state of operand is random".
Work on a more precise formulation of monitor-on and monitor-off,
especially the triggering event.

*check for rule "next state" in preceding event = "prev. state" in next event on variable

line 50 remove "A single event can happen instantaneously"

10.13.2
page 139 line 8 remove "thus establishing an event sequence"
line 10: change "as follows" to "according to the following rules [a) and b)]"

*check whether the term "pin variable" is defined

line 15 remove "either". Specify that MONITOR annotation takes precedence.
line 25 one "be" too much

paragraph b) better formulation needed:
for instance "The monitor shall be sensitive to the boolean expression, not to each single
operand within the boolean expression."

line 30: put "according to rule a)"
line 31: put "according to rule b)"
make a rule c): "a) and b) shall define the set of relevant events for eval of any vector expression"
p.139 put a figure name
p.139 mark end of example on line 25
line 26: plural "events"
line 31 change "causing" to "determining"
line 33 remove "corresponding"
line 35 change "trigger an advancement in time" to "not be considered simultaneous"
"effect" later than "cause"
line 37 "control statement" needs reference to syntax 67.
concatenate c) and d)
A.I. Joe Daniels to check "co-incidence" umlaut needed?
line 47 ff make reference to the rules in the example

make a statement:
eval of vector expression in BEHAVIOR follows causality,
eval of vector expression in VECTOR follows measured time

10.13.3
line 20 remove "either"
line 23 change "occurs immediately before" to "is immediately followed by"

line 36 Reformulate the rule, considering the restriction to "immediately followed by"

need definition of nomenclature (index, superscript) in math formulae