Attendees:
	Charles Dawson
	Shalom Bresticker
	Karen Pieper
	Steve Sharp
	Mark Hartoog
	Tom Fitzpatrick
	Francoise Martinolle
	Neil Korpusik
	Cliff Cummings

Motion that patent policy be considered read.
Seconded, approved

BTF 387 - Approved change was not implemented properly. Karen said
    that it can be assigned directly to V-LRM in the Mantis
    item. Shalom mentioned that it needs to be included in the ballot
    recirculation package.  
AI - Shalom to send Tom the information to record this issue into Mantis. (See below)

680 - Configuration Proposal to change "configuration" keyword to
    beginconfig. Both "config" and "configuration" appear in Cadence's
    customer suite. There also seems to be some consensus to change
    "cell" to "cellname". 

   Discussion: Can there be more than one top-level config? If there
    are multiple configs, how do we know which is top-level? Steve was
    unable to find language that dealt with configs being included in
    the Verilog source stream, so this needs to be part of the
    proposal.

    Straw Poll:
   Straw poll: config keyword
      Stu, Steven - prefer beginconfig
      Karen       - Ok with either configuration or beginconfig
      Mark, Doug, Tom, Cliff, Neil   - prefers configuration for consistency
		    with other existing language constructs (don't need begin)

   Straw poll: cell keyword
      Steven, Cliff - change cell to cellname
      Stu           - prefers context sensitive keywords, but now ok with 
		      cellname

   Straw poll: library map files
      Cliff - likes idea of lib.map in current directory and -l for others.
     Steven - current LRM says noting about a command line option.
	    - wants to keep library map file as is.
     Tom    - current LRM "in a pre-defined file" prior to reading source files
	    - if allow command-line option they would need to be the first file.
              This creates a file ordering dependency.

   Straw poll: configs in library map file 
      Steve - leave it alone 
	    - there is a mapping issue if compiling into separate libraries.
	    - Jay thought that there was a use-model for allowing them in one 
	      file.
      Cliff - prefers to clean this up and not allow this 
      Mark  - 13.5.5 - mapping to an instance in a library
	      configs viewed as cells and could be in libraries. 
	      Could have same name in multiple libraries.

   Straw poll:
      - Normative notes in VPI section
      - Change "notes" to "details"

     Stu  - It could be ambiguous if the phrase "note that" is used.
	    Even though it is not a violation of IEEE rules.
   Shalom - concerned about some normative text being treated like a note.
	  - There are a few cases where he has comments.

AI - Cliff to submit proposal by tomorrow (5/3)
AI - Steven to check with Jay if we need to allow configs in library map files.

       Guidance for Cliff's proposal:
	  a. choice of keywords
	     config --> configuration - more consistent with rest of language
	     cell   --> cellname
          b. configurations will be allowed in Verilog input stream - agreed
	  c. library mapping must be explicitly in a separate file
	  d. allow configs in library map file? - yes
	  e. `keywords
              2005 - both sets of keywords will be reserved
	      2001 - only has the existing set of 2001 keywords

658: Straw Poll, for VPI diagrams, should the "notes" be changed to
     "clarifying details," "informative details" or just "details"
     Consensus: "details"

667: Shalom submitted email proposing friendly amendment to Steve's
     proposal (which was posted to Mantis on 4/29/05). Steve accepts
     these amendments.
     Motion: Steve (as ammended)
     Second: Shalom
     Passed unanimously

BTF387 / Mantis 716
     Motion: Steve
     Second: Chas
     Passed unanimously

705: 
   Shalom - not many people have given input.
	  - opposed to last minute quick changes being made to the LRM in a 
	    rushed ballot response process. This is prone to making errors.
          - There are several viable options.
	  - This flag was intended to have an additional effect. 
	  - The LRM is misleading and has caused Yonghao to misunderstand it. 
	  - Would like to get guidance from the ballot entities to achieve 
	    consensus. Mentor may have an implementation for this. 
   Steven - has been hoping that others who know this better will resolve it.
	  - Cadence agrees that there is an issue that should be resolved.
	  - Can we say that it is undefined if this flag is set to true.
	    Then we could figure it out at a later point in time.
   Cliff  - ASIC library vendors specified most of this originally.
   Dave   - wasn't sure what this flag was for.
   Tom    - only Shalom, Ted, Yonghao seem to be fully up to speed.

   $timeskew - changes ok? [Tom]
	     - we have apparently approved a change that is inconsistent with 
	       Ted's proposal.  

   Shalom - Ted has given feedback.
	  - we could possibly have two different flags for the two. 

   Yonghao - knows this stuff the best but he wasn't available. 

AI/Tom     - get Mentor feedback by next P1800 meeting (May 5th).
AI/Charles - get Cadence feedback. Yonghao will be on a conference call with 
	     Shalom and Charles to decide which approach to take.

6. keyword proposal - Mantis 687

   Stu sent out information this morning. 

We will conduct email votes on:
      687 - Stu's compatability proposal
      658 - Tom's "notes" proposal
      Results to be received by Wednesday

Next meeting: Friday 5/6
     Key issues for discussion: 705 ($fullskew), 680 (configs)

     Noon EDT (9am PDT)
     Dial-in: 888-742-8686 
     Int'l: 303-928-2600 
     Passcode: 8179393