[sv-cc] Meeting minutes for 04/11/2007

Minutes of 04/11/2007 SV-CC Meeting.

ATTENDEES
00000000000000000
77777777666666666
00000000111110000
43322111221009988
12121310200212131
18484173068517306
xxxxx-xxxxxxxxxxx Charles Dawson
xx-xxxxxxx-x-xxxx Ralph Duncan
xxxxxxxxxxxxxxxxx Jim Vellenga
xxxxxxx-xxx-x-xxx Andrzej Litwiniuk
xxx-xxxxx-xxxxxxx Abigail Moorhouse
xx-xxxx--xxxxxx-x Michael Rohleder
xxx-xxxxxxxxxxxxx Chuck Berking
xxxxxxxxxxx-xxxxx Bassam Tabbara
x-xx-xx-x-xxxxxxx Francoise Martinolle
xxxxx-xxxxxxxxxx- Ghassan Khoory
----xx----------- Steve Dovich
-x--xxxx----xx-xx Amit Kohli
-x--------------- Stu Sutherland

1.  Reviewed Patent information.

   - Chas reviewed the patent information.


2.  Reviewed minutes of the 03/28/2007 Meeting.
     - Ralph/Chuck.  ACCEPTED


3.  Liaisons
   - Francoise was on vacation, so missed the last week's SV-BC meeting.

   - Champions to vote on Item 890 next week.  Michael has some comments
     about this which he sent to SV-CC this morning.  There are several
     PLI regions which are not defined at all.  It is possible to create
     a new active event prior for the pre-NBA region.  Should that event
     be handled prior to entering the NBA region?  The way Michael reads
     the spec, this is not the intended functionality.  Same question goes
     for the observed region.  Should all of the NBA regions be completed
     before entering the active region again? Francoise will write up
     Michael's question and pose it to the SV-EC committee.

   - No other meetings to report on.


4.  New business

   - Gord's tf_nodeinfo() question
     No one got messages.  Chas forwarded.  Debate postponed until next meeting.

   - Chuck's compatibility issues (Item 1385)
     Abi believes that 1800-2005 should trump the 1364-2005 functionality.
     Should have a "latest" mode as the default.  Need to make sure that
     we differentiate when an application will need to re-compile and when
     it will just work with the default mode.   Discussion on error handling,
     and how we should deal with that in the LRM.  Michael wants a "here is
     the minimum amount that the vendor must support in order to be compliant"
     statement.

     Abi stated that the fundamental problem is caused by an old application
     being applied to a new design.  Since both the application and the design
     are beyond the control of the tool vendor, this is inherently a problem
     that must be dealt with by the user.  The tool should try to give the
     developer a clue as to where the problem is.  Michael suggests bracketing the
     VPI functions with a signal handler and trap nulls.

   - Chas reminded everyone to let him know if they would be able to make the
     next face to face meeting.  Chas will produce an agenda prior to our next
     next meeting, and requested help coming up with appropriate topics.

Motion to adjourn.  Ralph/Chuck.  Meeting ended at 1:05pm.

5.  Reviewed items with proposals.

6.  Reviewed SV-CC items with proposals (Straw poll only).

7.  Old Business

8.  Action items

   - Ongoing review of Michael and Abi's compatibility proposal.
   - Francoise and Bassam to continue work on assignment patterns.
   - Francoise to champion adding support for typed parameters to the
     typespec diagrams.
   - Abi to champion adding support for parameterized classes.
   - Abi/JimV to champion improving the ability to compare objects.
   - Steve Dovich to determine best way to deal with issues between
     versions of the IEEE specs.
   - SV-CC to review proposal for Item 0890.
   - Michael to compose response to the Clean Scheduling Proposal.
   - All to verify their Acknowledged Mantis Items.
   - Steve to send out exact text on referring to a prior version.
   - Chas to gather a list of all SV-CC approved mantis items which have
     not been incorporated into draft 2.
   - Chas to formulate an agenda for the next SV-CC face to face meeting.

9.  Items for consideration at the next meeting (they already have proposals):

   - Item 1726 Clarify meaning of vpiConstantSelect

10. Next meeting
    The next SV-CC meeting will be on 04/25/2007.
    The next P1800 meeting will be on 04/24/2007.


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.