[$ieee-1850] Minutes of the LRM Subcommittee Meeting - 8 Feb 2005

Minutes of the LRM Subcommittee Meeting - 8 Feb 2005

Participants:
  Erich, Harry, Joseph, Cindy, Avigail, Johan M., Tom, Lyes

This meeting of the LRM Subcommittee begins the process of merging change proposals into the LRM. Email regarding this topic should be posted to the ieee-1850-lrm reflector. All of the above are now on the LRM reflector. If you want to particpate in this effort, please send email to Harry or Erich requesting that you be added to the LRM reflector. (This is the last email about this topic that will be sent to the full working group reflector.)

Current Status
===========

Following are links to all of the changes being considered for the June release of the LRM:

 - Email summary of 31 Jan 05:
      http://www.eda.org/ieee-1850/ieee-1850-extensions/hm/0164.html
 - Group L (LRM corrections):
      http://www.eda.org/ieee-1850/Issues/Group-L.html

It should be noted also that there is still some discussion going on regarding the portability proposal, but hopefully that will be resolved shortly.

Next Steps
========

To produce the LRM, we need to integrate the various change proposals into specific changes for each chapter. To that end, we divided up the chapters among the following owners:

1-3 Erich
4 Tom
5 Johan M.
6 Cindy, Avigail
7 Erich
8 Harry

For each chapter, the owner will create a text file containing all changes for that chapter ("chapter changes"), as follows:

for each change proposal,
- copy each change that affects this chapter into the chapter changes document
- identify any sentence, paragraph, example, or BNF with conflicting changes
    - propose a resolution, if possible; otherwise report it as a problem
- identify any incomplete change specification
    - propose an elaboration to make it complete, if possible; otherwise report it
- identify any sections that seem to need attention in order to implement some change
    - sections that should have been addressed in the change proposal, but were not

The result should be a list of specific changes (e.g., "section K, paragraph L, sentence M, change ... to ..."), in order as they occur from beginning to end of the chapter, so that the LRM updates can proceed mechanically driven by each chapter's list. The chapter change lists will also serve as a basis for proofreading the updated LRM to ensure that all changes were correctly applied.

Issues that remain to be resolved, or elaborated, or holes that need to be addressed, will be handed off to the original proposer(s) for resolution.

Appendix B
=========

We also need to find a way to make Appendix B more readable (i.e., less fuzzy). This may involve setting appropriate options during the flow from LaTeX to Postscript to PDF to Frame. Johan M. has sent out a link to a web page with some information about this. Note also that there are some text changes required in the formal semantic definition.

Schedule
=======

By
Feb 15 - post (to LRM reflector) first draft chapter changes for each chapter
Feb 22 - resolve all remaining conflicts, etc.
Mar 1 - merge all changes into the LRM
Mar 8 - complete review of the LRM and identify any issues
Mar 15 - complete final LRM

There will be no meeting on 15 Feb, during DVCon.
Received on Tue Feb 8 12:47:46 2005