From jwagener@trc.amoco.com Mon Mar 23 18:37:53 1992 Received: from noc.msc.edu by dkuug.dk via EUnet with SMTP (5.64+/8+bit/IDA-1.2.8) id AA13694; Mon, 23 Mar 92 18:37:53 +0100 Received: from uc.msc.edu by noc.msc.edu (5.65/MSC/v3.0(901107)) id AA28141; Mon, 23 Mar 92 11:37:46 -0600 Received: from [129.230.11.2] by uc.msc.edu (5.65/MSC/v3.0z(901212)) id AA11356; Mon, 23 Mar 92 11:37:32 -0600 Received: from trc.amoco.com (apctrc.trc.amoco.com) by netserv2 (4.1/SMI-4.0) id AA22969; Mon, 23 Mar 92 11:37:27 CST Received: from crmac1 (crmac1.trc.amoco.com) by trc.amoco.com (4.1/SMI-4.1) id AA01677; Mon, 23 Mar 92 11:37:24 CST Date: Mon, 23 Mar 92 11:37:24 CST Message-Id: <9203231737.AA01677@trc.amoco.com> From: Jerrold L. Wagener To: SC22WG5@dkuug.dk Cc: jwagener@trc.amoco.com Subject: interim interpretation processing procedures X-Charset: ASCII X-Char-Esc: 29 To X3J3 - As promised in an earlier note, here is X3J3-121-JLW-2, interim procedures for interpretation processing. Jerry X3J3-121-JLW-2 March 23, 1992 Subject: Interim Procedures for Interpretation Processing From: Jerry Wagener For those issues not adequately resolved in the email informal forum, X3J3 must make formal interpretations. Also, it is important that insight derived from the informal interchange, even if it doesn't result in a request for formal interpretation, be captured for posterity. Formal interpretations require registration with X3 and inviting the requester to an X3J3 meeting. A request for interpretation gets registered in one of two ways: (1) if the request is sent directly to the X3 secretariat, the secretariat registers it and sends it to the committee for processing, and (2) if the request is sent to the committee, it is the chair's responsibility to register it with the secretariat. Therefore, I need to know what of the interpretation-related email traffic the chair needs to register with X3. To encourage the informal forum to resolve many of these issues/questions, I propose the following interim process, to be discussed and refined at the next X3J3 meeting. 1. Questions of interpretation should continue to be vigorously worked on the network, as they have been. 2. After such informal exchange, if someone believes a formal interprtation is needed, a request is prepared (see 4 below) and distributed on the X3J3+WG5 email network. 3. Such requests distributed via email by the distribution cut-off date (April 20, 1992, for meeting 121) will be included in the premeeting distribution, considered at the next X3J3 meeting, and the requestor will be invited via email to that meeting. 4. The request should be in the form of an X3J3 document (e.g., with an identification of the form X3J3-121-JLW-2) with a subject of: Request for Interpretation: Since X3J3 has a specified format for interpretations (see, for example, X3J3-121-ADT-3), it would be helpful if the request was in that format as much as possible. (Roughly this format has four parts - a succinct question representing the request, the interpretation response, a discussion section, and a reference section.) In any event, it will be the twin conditions of it being an X3J3 document with a "Request for Interpretation" subject that will trigger registration and consideration as a formal interpretation. 5. Every reasonable effort will be made to act on a request for interpretation at the next X3J3 meeting. After the meeting the resulting draft response will be distributed on the X3J3+WG5 network and/or made available from a central electronic repository. Comments on the draft action can be made in the form of X3J3 documents (electronic or otherwise) before the distribution cut-off of the subsequent meeting. 6. Every reasonable effort will be made to consider comments on a draft interpretation action and to take final action on the interpretation at the subsequent X3J3 meeting. This process should help identify which interpretations X3J3 must be concerned with, expedite the processing of such requests, and ensure wide participation in and high quality of interpretation decisions. For those email interchanges that don't result in a request for a formal interpretation, but do provide clarifications, it will be important to capture those for the 1995 "maintenance revision". It appears that this revision, if it materializes, will be devoted primarily, if not exclusively, to corrections, clarifications, and interpretations. We can process such clarifications as if they were interpretations (i.e., use the same mechanisms within X3J3), except they wouldn't need registration or inviting the author. Such clarifications could be in the form of an X3J3 document as described in item 4 above with "Request for Interpretation" changed to "Clarification".