<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
	>
<channel>
	<title>Comments on: ISO/IEC JTC1 Revises Directives, Addresses OOXML Abuses</title>
	<atom:link href="http://www.robweir.com/blog/2010/07/iso-iec-jtc1-revises-directives.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.robweir.com/blog/2010/07/iso-iec-jtc1-revises-directives.html?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=iso-iec-jtc1-revises-directives</link>
	<description>Thinking the unthinkable, pondering the imponderable, effing the ineffable and scruting the inscrutable</description>
	<lastBuildDate>Tue, 07 Feb 2012 11:20:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Rob</title>
		<link>http://www.robweir.com/blog/2010/07/iso-iec-jtc1-revises-directives.html#comment-3396</link>
		<dc:creator>Rob</dc:creator>
		<pubDate>Thu, 08 Jul 2010 17:05:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/?p=1071#comment-3396</guid>
		<description>The new JTC1 procedures consist of ISO/IEC Directives, Part 1 plus the JTC1 Supplement.  The idea was to put the procedures common to ISO, IEC and JTC1 into a common document and then in the Supplement to express any peculiar JTC1 rules.

There is a transition period, until July 1st, 2011, where some in progress work can continue to follow the old rules, while new projects start under the new procedures.  So I would not say the old Directives are dead, but they are only used for the in-progress work, and only for the next 12 months.  That&#039;s my read of it.

It is quite possible that things were lost in the move to the new documents.  You mention the interop annex.  I just noticed also that they lost the clause on how an organization can become a Category A Liaison like Ecma.  They define the rights of such a liaison, but never talk about how one applies for or is approved to have that status.

It would be good to have a comprehensive list of the &quot;documents which provide further guidance&quot;.  Surely one must be ISO Directives, Part 2, which provides the drafting guidelines for standards.  Another one must be the PAS Management Guide.  There may be others.</description>
		<content:encoded><![CDATA[<p>The new JTC1 procedures consist of ISO/IEC Directives, Part 1 plus the JTC1 Supplement.  The idea was to put the procedures common to ISO, IEC and JTC1 into a common document and then in the Supplement to express any peculiar JTC1 rules.</p>
<p>There is a transition period, until July 1st, 2011, where some in progress work can continue to follow the old rules, while new projects start under the new procedures.  So I would not say the old Directives are dead, but they are only used for the in-progress work, and only for the next 12 months.  That&#8217;s my read of it.</p>
<p>It is quite possible that things were lost in the move to the new documents.  You mention the interop annex.  I just noticed also that they lost the clause on how an organization can become a Category A Liaison like Ecma.  They define the rights of such a liaison, but never talk about how one applies for or is approved to have that status.</p>
<p>It would be good to have a comprehensive list of the &#8220;documents which provide further guidance&#8221;.  Surely one must be ISO Directives, Part 2, which provides the drafting guidelines for standards.  Another one must be the PAS Management Guide.  There may be others.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul E. (Marbux) Merrell, J.D.</title>
		<link>http://www.robweir.com/blog/2010/07/iso-iec-jtc1-revises-directives.html#comment-3395</link>
		<dc:creator>Paul E. (Marbux) Merrell, J.D.</dc:creator>
		<pubDate>Thu, 08 Jul 2010 16:36:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/?p=1071#comment-3395</guid>
		<description>I&#039;d appreciate any clarification you might offer regarding the relationship between the new JTC 1 Supplement and ISO/IEC JTC 1 Directives, 5th ed., rev. 3. The new supplement seems to speak to many of the same topics, but less than all. E.g., there is but a single mention of interoperability in the Supplement whilst the Directives supplied an entire annex of guidance on the topic. 

It is not clear to me that the Supplement is intended to replace the Directives. The Supplement states at lines 117-120:

&quot;Part 1 of the ISO/IEC Directives, together with this Supplement, provides procedural rules to be followed by ISO/IEC JTC 1. There are, however, other documents which provide further guidance, such as JTC 1 Standing Documents. Forms unique to JTC 1 are found in the Templates at 
http://isotc.iso.org/livelink/livelink?func=ll&amp;objId=8913214&amp;objAction=browse&amp;sort=name [.]&quot;

The linked page includes a download link for ISO/IEC JTC 1 Directives, 5th ed., rev. 3. I&#039;ve found no language in the Supplement thus far indicating that it supercedes the JTC 1 Directives. That&#039;s an important issue to resolve because JTC 1 Directives provide in relevant part:

&quot;This document replaces the ISO/IEC Directives, Part 1 - Procedures for the technical work, but has been developed to be consistent with them.  Any differences between this document and the ISO/IEC Directives, Part 1 are dictated by the nature of information technology work and have been authorised by the ISO Secretary-General and IEC General-Secretary ( Secretaries-General) and Councils of IEC and ISO.  Where differences between this document and the ISO/IEC Directives exist, the provisions of this document shall govern.&quot;

Any enlightenment to offer here? Did I miss something in the Supplement?</description>
		<content:encoded><![CDATA[<p>I&#8217;d appreciate any clarification you might offer regarding the relationship between the new JTC 1 Supplement and ISO/IEC JTC 1 Directives, 5th ed., rev. 3. The new supplement seems to speak to many of the same topics, but less than all. E.g., there is but a single mention of interoperability in the Supplement whilst the Directives supplied an entire annex of guidance on the topic. </p>
<p>It is not clear to me that the Supplement is intended to replace the Directives. The Supplement states at lines 117-120:</p>
<p>&#8220;Part 1 of the ISO/IEC Directives, together with this Supplement, provides procedural rules to be followed by ISO/IEC JTC 1. There are, however, other documents which provide further guidance, such as JTC 1 Standing Documents. Forms unique to JTC 1 are found in the Templates at<br />
<a href="http://isotc.iso.org/livelink/livelink?func=ll&#038;objId=8913214&#038;objAction=browse&#038;sort=name" rel="nofollow">http://isotc.iso.org/livelink/livelink?func=ll&#038;objId=8913214&#038;objAction=browse&#038;sort=name</a> [.]&#8221;</p>
<p>The linked page includes a download link for ISO/IEC JTC 1 Directives, 5th ed., rev. 3. I&#8217;ve found no language in the Supplement thus far indicating that it supercedes the JTC 1 Directives. That&#8217;s an important issue to resolve because JTC 1 Directives provide in relevant part:</p>
<p>&#8220;This document replaces the ISO/IEC Directives, Part 1 &#8211; Procedures for the technical work, but has been developed to be consistent with them.  Any differences between this document and the ISO/IEC Directives, Part 1 are dictated by the nature of information technology work and have been authorised by the ISO Secretary-General and IEC General-Secretary ( Secretaries-General) and Councils of IEC and ISO.  Where differences between this document and the ISO/IEC Directives exist, the provisions of this document shall govern.&#8221;</p>
<p>Any enlightenment to offer here? Did I miss something in the Supplement?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob</title>
		<link>http://www.robweir.com/blog/2010/07/iso-iec-jtc1-revises-directives.html#comment-3394</link>
		<dc:creator>Rob</dc:creator>
		<pubDate>Thu, 08 Jul 2010 12:43:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/?p=1071#comment-3394</guid>
		<description>Jesper, remember, a DIS ballot is not a ballot of technical committees or subcommittees.  So this is not the preferred time for deep technical analysis of the draft.  

If you look at &quot;normal&quot; progression (not Fast Track) you see a similar pattern.  Committee Stage (CD) is &quot;the principal stage at which comments from national bodies are taken into consideration, with a view to reaching consensus on the technical content. National bodies shall therefore carefully study the texts of committee drafts and submit all pertinent comments at this stage&quot; (2.5.1).  But at higher stages, for example when when JTC1 votes on the FDIS, you have the same restriction as a DIS, that you cannot submit conditional Yes votes (2.7.2).

I think the logic of the voting rules is clear.  &quot;No with comments&quot;, means you wish the DIS to be defeated.  &quot;Yes with (or without) comments&quot; means you want it to pass.  If more than 25% vote disapproval, then there is no second chance for the proposal.  It essentially &quot;goes back to committee&quot;, in the DIS case back to the submittor of the Fast Track.  But this is no different than for a home-grown JTC1 draft, right?  If you get too many disapproval votes in an FDIS ballot, you do not go to a BRM.  It also reverts back to the subcommittee.

So what do you do in your hypothetical Denmark situation, where you see a DIS that you &quot;kind of like&quot; but have some technical issues?  Well, what would you do for a non-Fast Track draft at that stage?  I don&#039;t think the intent of Fast Track and PAS is to have a different set of criteria for the technical contents of the drafts.</description>
		<content:encoded><![CDATA[<p>Jesper, remember, a DIS ballot is not a ballot of technical committees or subcommittees.  So this is not the preferred time for deep technical analysis of the draft.  </p>
<p>If you look at &#8220;normal&#8221; progression (not Fast Track) you see a similar pattern.  Committee Stage (CD) is &#8220;the principal stage at which comments from national bodies are taken into consideration, with a view to reaching consensus on the technical content. National bodies shall therefore carefully study the texts of committee drafts and submit all pertinent comments at this stage&#8221; (2.5.1).  But at higher stages, for example when when JTC1 votes on the FDIS, you have the same restriction as a DIS, that you cannot submit conditional Yes votes (2.7.2).</p>
<p>I think the logic of the voting rules is clear.  &#8220;No with comments&#8221;, means you wish the DIS to be defeated.  &#8220;Yes with (or without) comments&#8221; means you want it to pass.  If more than 25% vote disapproval, then there is no second chance for the proposal.  It essentially &#8220;goes back to committee&#8221;, in the DIS case back to the submittor of the Fast Track.  But this is no different than for a home-grown JTC1 draft, right?  If you get too many disapproval votes in an FDIS ballot, you do not go to a BRM.  It also reverts back to the subcommittee.</p>
<p>So what do you do in your hypothetical Denmark situation, where you see a DIS that you &#8220;kind of like&#8221; but have some technical issues?  Well, what would you do for a non-Fast Track draft at that stage?  I don&#8217;t think the intent of Fast Track and PAS is to have a different set of criteria for the technical contents of the drafts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dead fish &#187; Blog Archive &#187; Better late than never</title>
		<link>http://www.robweir.com/blog/2010/07/iso-iec-jtc1-revises-directives.html#comment-3393</link>
		<dc:creator>dead fish &#187; Blog Archive &#187; Better late than never</dc:creator>
		<pubDate>Thu, 08 Jul 2010 07:36:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/?p=1071#comment-3393</guid>
		<description>[...] blockquote&gt; (Source) [...]</description>
		<content:encoded><![CDATA[<p>[...] blockquote&gt; (Source) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jesper Lund Stocholm</title>
		<link>http://www.robweir.com/blog/2010/07/iso-iec-jtc1-revises-directives.html#comment-3392</link>
		<dc:creator>Jesper Lund Stocholm</dc:creator>
		<pubDate>Thu, 08 Jul 2010 05:42:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/?p=1071#comment-3392</guid>
		<description>Hi Rob,

Thanks for the narrative of these complicated documents.

I think the clarification on when to vote &quot;no with comments&quot; is good - Denmark has consistantly been using this check-box when we wanted to apply maximum pressure to get things changes after a ballot.

However - I do think that the possibility of having the DIS die at this point might have contradictory consequences. Denmark has repeatedly been voting &quot;no with comments&quot; to proposals where we kindof liked it - but that there were things we would like to have changed before voting yes. With the changed rules, we might end up not having a second vote if enough feel like we do.

Any thoughts on this?</description>
		<content:encoded><![CDATA[<p>Hi Rob,</p>
<p>Thanks for the narrative of these complicated documents.</p>
<p>I think the clarification on when to vote &#8220;no with comments&#8221; is good &#8211; Denmark has consistantly been using this check-box when we wanted to apply maximum pressure to get things changes after a ballot.</p>
<p>However &#8211; I do think that the possibility of having the DIS die at this point might have contradictory consequences. Denmark has repeatedly been voting &#8220;no with comments&#8221; to proposals where we kindof liked it &#8211; but that there were things we would like to have changed before voting yes. With the changed rules, we might end up not having a second vote if enough feel like we do.</p>
<p>Any thoughts on this?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.586 seconds -->

