ALF conference call, Dec. 5, 2001

Peter Christiansen	Magma
Joe Daniels		Accellera
Wolfgang Roethig	NEC

Review of chapter 9.1 through 9.5
---------------------------------
p.47
legend for figures 8 ff. required
13.. a generic object defined as a child of another object
p.48
2 .. singular objects can only be declared once.
3 .. for example (instead of for instance)
20.. an object of type function
26 .. an object of type test
47-49.. remove
p.49
LIBRARY, SUBLIBRARY etc all need textual description
syntax box 43 defines "sublibrary"
INFORMATION rewrite subsection
remove syntax box 44, just say that INFORMATION is annotation_container.
p.50
2.. can be defined as independent objects.
3.. must be defined in context of other objects.
5.. INFORMATION statement
need purpose of CELL statement
rewrite NON_SCAN_CELL chapter
37 .. Syntax of non_scan_cell shall be defined as follows:
51 .. this statement is used
need to say that context of non_scan_cell is a CELL with scan functionality
p.52
redo the example
eliminate NOTES
p.53
7.. Celltype is a single_value_annotation
19.. "combinational" should be "combinatorial" (!)
21.. "multiplexor" should be "multiplexer" (?)
make ALIAS for backward compatibility.
27.. "complex" should be "compound"
30.. ditto
table 11: ram, rom, cam in lowercase for consistency
p.54
change "complex" to "compound"
write alu, pll, dsp, cpu, gpu in lowercase
p.55
25 .. SWAP_CLASS is one_level_annotation, i.e. 
      single_value_annotation or mlti_value_annotation
40 .. RESTRICT_CLASS ditto
      need to rewrite this paragraph (refer to work doc)
p.56
20 .. make example more meaningful
p.60
remove syntax box 47, make presentation consistent with other annotations
p.61
rewrite SITE reference chapter
need purpose and context of PIN statement
syntax box 48: enumerate cases with and w/o index_range
53.. change "row" into "word"
p.62
13.. shall be zero-extended to the left
15.. shall be truncated from the left
30.. two-dimensional
p.63
chapter 9.4.2.2 title should match syntax box
should pin_instantiation be renamed to subpin_statement?
48.. between zero and 2**N-1
should mathematical formulae be used for index range interpretation?
explain the purpose of non-contiguos bits being invalid
p.64
PIN_GROUP: member pins must be within the same cell as the pin_group statement
Define MEMBERS as multi_value_annotation
Define which annotations from member pins can be inherited by pin_group
Explain how PIN and PIN_GROUP can be used to map buses into scalar pins
and vice-versa.
p.68
paragraph after table 24 is misplaced. should be under CELLTYPE.
40 .. the construction scheme
p.68
put figure 13 after the tables as informational item.
p.72
1.. certain fundamental signaltype values
2.. the rule also applies to composite signaltype values
25.. mention that synchronous is wrt to signal w signaltype=clock
Write: Polarity applies only for input pin or bidirectional pin in input mode
Missing: mode-specific POLARITY for CONTROL signals
p.74
remove syntax box 52, make presentation consistent w other annotations
(see work doc)
p.75
Signal_class needs better explanation (see work doc)
get rid of Note
Supply_class needs better explanation (see work doc)
p.76
driver cell and pin needs better explanation
drivetype needs better explanation
p.79
example for differential would be helpful
p.80
CONNECT_CLASS needs better explanation (see work doc)
remove syntax box 53, 54, 55, make explanation consistent w other annotations
p.81
need purpose and context of wire statement
interconnect analysis model is 3rd item here
p.82
13.. specifies directive for tool to reduce arbitrary network into particular
     interconnect model.
19.. for estimating
p.83
31 .. 4 receivers, 1 driver
p.85 ff.
see COMPONENT proposal in work doc.
p.90
2.. divide into two sentences: source and driver in same device.
    receiver and sink in same device.

Suggestion: introduce WIRETYPE or PURPOSE statement:
statistical, parasitics, reduction, analysis