From robert_weir@us.ibm.com Mon May 28 09:49:17 2007
MIME-Version: 1.0
Content-type: multipart/alternative;
 boundary="Boundary_(ID_cSksY9sDvIafhYxUsugiqw)"
Date: Mon, 28 May 2007 12:49:18 -0400
From: robert_weir@us.ibm.com
Subject: Re: Rob Weir's Comments: Page 01, Comment 02-07,
 "Electronc Annexes in a humanly readable, lined-numbered format"
In-reply-to: <003001c7a04c$7ba10fa0$72e32ee0$@com>
To: Rex Jaeschke <rex@RexJaeschke.com>
Cc: "'Dave Welsh'" <dave.welsh@microsoft.com>,
        "'Doug Mahugh'" <Doug.Mahugh@microsoft.com>,
        "'Frank Farance'" <frank@farance.com>,
        "'Jerry Smith'" <jerry.smith@disa.mil>,
        "'Jon Bosak'" <jon.bosak@sun.com>,
        "'Kevin Trainor'" <ktrainor@ligent.net>,
        "'Levine, Leonard F CIV DISA GES-E'" <Leonard.Levine@disa.mil>,
        "'Lynne A. Price'" <lprice@txstruct.com>,
        "'Mason, James David (MXM)'" <masonjd@y12.doe.gov>,
        "'Norm Walsh'" <ndw@nwalsh.com>, patrick@durusau.net,
        "'Richard Barber'" <Richard.Barber@mindjet.com>,
        "'Steve Carton'" <steve.carton@retrievalsystems.com>,
        "'Tim Schoechle'" <timothy@schoechle.org>
X-MIMETrack: Serialize by Router on WTFMAIL03/WTF/M/Lotus(Release
 6.5.6FP1|April 24, 2007) at 05/28/2007 12:49:19 PM,
	Serialize complete at 05/28/2007 12:49:19 PM
X-PMX-Version: 5.2.0.264296

This is a multipart message in MIME format.

--Boundary_(ID_cSksY9sDvIafhYxUsugiqw)
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT

Rex,

I'm thinking ahead to publication.  How will these electronic annexes be 
published?  Is there such thing as an "electronic annex" in an ISO 
Standard?  Or won't everything get flattened into a PDF?

Since these XM documents do not limit themselves to a reasonable line 
length, different text editors will wrap the lines differently, making 
citation difficult.

So essentially I'm just trying to preseve a reasonable interpretation of 
ISO Directives, Part 2, where a standard is definde as, "document, 
established by consensus and approved by a recognized body...".   I'd like 
to see these annexes behave more like a document.

As you say, we may end up flattening these comments into one comment.

-Rob

___________________________

Rob Weir
Software Architect
Workplace, Portal and Collaboration Software
IBM Software Group

email: robert_weir@us.ibm.com
phone: 1-978-399-7122
blog: http://www.robweir.com/blog/

"Rex Jaeschke" <rex@RexJaeschke.com> wrote on 05/27/2007 06:47:47 AM:

> In the "Proposed change by the MB" column, Rob proposes, "The annex 
should
> be provided in a humanly readable, lined-numbered format so it can be
> referenced and cited. Additionally, an electronic machine readable 
version
> can be provided according to Annex H"
> 
> Certainly, the contents of the electronic annexes could be replicated
> in-line in the text. However, as Rob proposed, once there, for them to 
be
> usable, they'd need to have some mechanism so they can "be referenced 
and
> cited". Unfortunately, the editing guidelines for an IS do not allow it 
to
> contain line numbers. (I added line numbers to the DIS to make it easier 
to
> refer to lines under discussion. However, in the final standard, these 
will
> all be removed.) If anyone has a suggestion about how one might make 
such
> referencing possible, I'm "all ears".
> 
> 
> Separately, if we choose to forward these comments, I suggest we combine
> them into one general comment. My concern here is that at the Ballot
> Resolution Meeting (BRM), each separate comment discussed will take a
> certain amount of time for administrative overhead, plus time to address 
the
> specific comment. As such, I think if six related comments can be 
resolved
> as one, that would be welcomed by BRM attendees.
> 
> Rex
> 
> 
> 

--Boundary_(ID_cSksY9sDvIafhYxUsugiqw)
Content-type: text/html; charset=US-ASCII
Content-transfer-encoding: 7BIT


<br><font size=2 face="sans-serif">Rex,</font>
<br>
<br><font size=2 face="sans-serif">I'm thinking ahead to publication. &nbsp;How
will these electronic annexes be published? &nbsp;Is there such thing as
an &quot;electronic annex&quot; in an ISO Standard? &nbsp;Or won't everything
get flattened into a PDF?</font>
<br>
<br><font size=2 face="sans-serif">Since these XM documents do not limit
themselves to a reasonable line length, different text editors will wrap
the lines differently, making citation difficult.</font>
<br>
<br><font size=2 face="sans-serif">So essentially I'm just trying to preseve
a reasonable interpretation of ISO Directives, Part 2, where a standard
is definde as, &quot;</font><font size=2 face="Arial">document, established
by consensus and approved by a recognized body...&quot;. &nbsp; I'd like
to see these annexes behave more like a document.</font>
<br>
<br><font size=2 face="Arial">As you say, we may end up flattening these
comments into one comment.</font>
<br>
<br><font size=2 face="Arial">-Rob</font>
<br>
<br><font size=2 face="sans-serif">___________________________<br>
<br>
Rob Weir<br>
Software Architect<br>
Workplace, Portal and Collaboration Software<br>
IBM Software Group<br>
<br>
email: robert_weir@us.ibm.com<br>
phone: 1-978-399-7122<br>
blog: http://www.robweir.com/blog/</font>
<br>
<br><tt><font size=2>&quot;Rex Jaeschke&quot; &lt;rex@RexJaeschke.com&gt;
wrote on 05/27/2007 06:47:47 AM:<br>
<br>
&gt; In the &quot;Proposed change by the MB&quot; column, Rob proposes,
&quot;The annex should<br>
&gt; be provided in a humanly readable, lined-numbered format so it can
be<br>
&gt; referenced and cited. Additionally, an electronic machine readable
version<br>
&gt; can be provided according to Annex H&quot;<br>
&gt; <br>
&gt; Certainly, the contents of the electronic annexes could be replicated<br>
&gt; in-line in the text. However, as Rob proposed, once there, for them
to be<br>
&gt; usable, they'd need to have some mechanism so they can &quot;be referenced
and<br>
&gt; cited&quot;. Unfortunately, the editing guidelines for an IS do not
allow it to<br>
&gt; contain line numbers. (I added line numbers to the DIS to make it
easier to<br>
&gt; refer to lines under discussion. However, in the final standard, these
will<br>
&gt; all be removed.) If anyone has a suggestion about how one might make
such<br>
&gt; referencing possible, I'm &quot;all ears&quot;.<br>
&gt; <br>
&gt; <br>
&gt; Separately, if we choose to forward these comments, I suggest we combine<br>
&gt; them into one general comment. My concern here is that at the Ballot<br>
&gt; Resolution Meeting (BRM), each separate comment discussed will take
a<br>
&gt; certain amount of time for administrative overhead, plus time to address
the<br>
&gt; specific comment. As such, I think if six related comments can be
resolved<br>
&gt; as one, that would be welcomed by BRM attendees.<br>
&gt; <br>
&gt; Rex<br>
&gt; <br>
&gt; <br>
&gt; <br>
</font></tt>

--Boundary_(ID_cSksY9sDvIafhYxUsugiqw)--

