<?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: OOXML, Macros and Security</title>
	<atom:link href="http://www.robweir.com/blog/2008/03/ooxml-macros-and-security.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.robweir.com/blog/2008/03/ooxml-macros-and-security.html?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=ooxml-macros-and-security</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: James</title>
		<link>http://www.robweir.com/blog/2008/03/ooxml-macros-and-security.html#comment-1580</link>
		<dc:creator>James</dc:creator>
		<pubDate>Thu, 06 Mar 2008 14:05:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/2008/03/ooxml-macros-and-security.html#comment-1580</guid>
		<description>I really wish I could have been a fly on the wall last week then... or at least the meetings could have been recorded for archive later...&lt;br/&gt;&lt;br/&gt;The most frustrating thing being the results of this will directly affect me in my professional life (Linux Systems Administrator) as well as my private life but there is very little that seems possible outside of hoping that the UK NB sticks by the No vote and that more NBs see the sense of the matter....&lt;br/&gt;&lt;br/&gt;Incidentally over at Brian Jones&#039; blog there are dispersions being cast over your macro comments and the state of ISO 26300 unsurprisingly.</description>
		<content:encoded><![CDATA[<p>I really wish I could have been a fly on the wall last week then&#8230; or at least the meetings could have been recorded for archive later&#8230;</p>
<p>The most frustrating thing being the results of this will directly affect me in my professional life (Linux Systems Administrator) as well as my private life but there is very little that seems possible outside of hoping that the UK NB sticks by the No vote and that more NBs see the sense of the matter&#8230;.</p>
<p>Incidentally over at Brian Jones&#8217; blog there are dispersions being cast over your macro comments and the state of ISO 26300 unsurprisingly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob</title>
		<link>http://www.robweir.com/blog/2008/03/ooxml-macros-and-security.html#comment-1578</link>
		<dc:creator>Rob</dc:creator>
		<pubDate>Thu, 06 Mar 2008 13:25:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/2008/03/ooxml-macros-and-security.html#comment-1578</guid>
		<description>James, those appear to be edited versions of the notes which were taken during the meeting.  In particular, the &quot;resolutions&quot; document appears to be a list of the resolutions that were approved, stripping out the ones that either positively failed or died for lack of time to bring them to a vote.&lt;br/&gt;&lt;br/&gt;There were a mix of NB views expressed.  I&#039;m not sure the meeting notes give a good flavor of that.  For example, some NB&#039;s did not raise any points and just said &quot;We are delighted with DIS 29500&quot; when it was their turn.  Since they did not propose any text changes, their view was not recorded in the resolutions.  Similarly, those NB&#039;s who, in the view of the Convenor, had proposals that were not achievable within the time constraints of the BRM, these could not be brought up for discussion.  So you won&#039;t see them in the meeting notes or resolutions.  The net result is the resolutions are a slice of the more moderate opinions in the room.  But the atmosphere was far more charged than these notes would suggest.</description>
		<content:encoded><![CDATA[<p>James, those appear to be edited versions of the notes which were taken during the meeting.  In particular, the &#8220;resolutions&#8221; document appears to be a list of the resolutions that were approved, stripping out the ones that either positively failed or died for lack of time to bring them to a vote.</p>
<p>There were a mix of NB views expressed.  I&#8217;m not sure the meeting notes give a good flavor of that.  For example, some NB&#8217;s did not raise any points and just said &#8220;We are delighted with DIS 29500&#8243; when it was their turn.  Since they did not propose any text changes, their view was not recorded in the resolutions.  Similarly, those NB&#8217;s who, in the view of the Convenor, had proposals that were not achievable within the time constraints of the BRM, these could not be brought up for discussion.  So you won&#8217;t see them in the meeting notes or resolutions.  The net result is the resolutions are a slice of the more moderate opinions in the room.  But the atmosphere was far more charged than these notes would suggest.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James</title>
		<link>http://www.robweir.com/blog/2008/03/ooxml-macros-and-security.html#comment-1577</link>
		<dc:creator>James</dc:creator>
		<pubDate>Thu, 06 Mar 2008 10:23:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/2008/03/ooxml-macros-and-security.html#comment-1577</guid>
		<description>Rob,&lt;br/&gt;&lt;br/&gt;Further to my previous comment (and having now read the meeting notes and resolutions accepted) I am of the distinct impression the prevailing attitude seems to have been:&lt;br/&gt;&lt;br/&gt;NB1: &quot;Gah this is awful... It should have been done this way in the first place as it is the &#039;proper&#039; way to do it&quot;&lt;br/&gt;&lt;br/&gt;NB2:&quot;I agree it would be a &#039;better&#039; spec if we do it that way&quot;&lt;br/&gt;&lt;br/&gt;Rest:&quot;Agreed - The editor is instructed to incorporate resolution X&quot;&lt;br/&gt;&lt;br/&gt;So the end result is that yes the spec was improved but only to the extent that those who deal with standards creation often feel the original was awful and near enough &#039;any&#039; change had to be an improvement. Thus to deny a resolution would be to leave the text as was and as professionals they felt an obligation to at least get an improved text out - even if the result was the final text still wouldn&#039;t be up to scratch for a standard.&lt;br/&gt;&lt;br/&gt;Consequently most of the time at the BRM (including in the evening out of session) seems to have been spent getting it into a shape where it could &#039;start&#039; being discussed as opposed to final polish - this, of course, resulting in no time to actually work on &#039;worthwhile&#039; changes to polish it up and make it worthy of an ISO stamp....&lt;br/&gt;&lt;br/&gt;Your comments?</description>
		<content:encoded><![CDATA[<p>Rob,</p>
<p>Further to my previous comment (and having now read the meeting notes and resolutions accepted) I am of the distinct impression the prevailing attitude seems to have been:</p>
<p>NB1: &#8220;Gah this is awful&#8230; It should have been done this way in the first place as it is the &#8216;proper&#8217; way to do it&#8221;</p>
<p>NB2:&#8221;I agree it would be a &#8216;better&#8217; spec if we do it that way&#8221;</p>
<p>Rest:&#8221;Agreed &#8211; The editor is instructed to incorporate resolution X&#8221;</p>
<p>So the end result is that yes the spec was improved but only to the extent that those who deal with standards creation often feel the original was awful and near enough &#8216;any&#8217; change had to be an improvement. Thus to deny a resolution would be to leave the text as was and as professionals they felt an obligation to at least get an improved text out &#8211; even if the result was the final text still wouldn&#8217;t be up to scratch for a standard.</p>
<p>Consequently most of the time at the BRM (including in the evening out of session) seems to have been spent getting it into a shape where it could &#8216;start&#8217; being discussed as opposed to final polish &#8211; this, of course, resulting in no time to actually work on &#8216;worthwhile&#8217; changes to polish it up and make it worthy of an ISO stamp&#8230;.</p>
<p>Your comments?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James</title>
		<link>http://www.robweir.com/blog/2008/03/ooxml-macros-and-security.html#comment-1576</link>
		<dc:creator>James</dc:creator>
		<pubDate>Thu, 06 Mar 2008 10:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/2008/03/ooxml-macros-and-security.html#comment-1576</guid>
		<description>Rob it appears some secrecy has been mini-lifted (or the JP delegation is fed up with things?)...&lt;br/&gt;&lt;br/&gt;&lt;a HREF=&quot;http://www.itscj.ipsj.or.jp/sc34/open/0989.pdf&quot; REL=&quot;nofollow&quot; rel=&quot;nofollow&quot;&gt;Resolutions of the meeting&lt;/a&gt;&lt;br/&gt;&lt;br/&gt;&lt;a HREF=&quot;http://www.itscj.ipsj.or.jp/sc34/open/0990.pdf&quot; REL=&quot;nofollow&quot; rel=&quot;nofollow&quot;&gt;Editied notes of the meeting.&lt;/a&gt;&lt;br/&gt;&lt;br/&gt;Can you say if these link up with your experiances last week?</description>
		<content:encoded><![CDATA[<p>Rob it appears some secrecy has been mini-lifted (or the JP delegation is fed up with things?)&#8230;</p>
<p><a HREF="http://www.itscj.ipsj.or.jp/sc34/open/0989.pdf" REL="nofollow" rel="nofollow">Resolutions of the meeting</a></p>
<p><a HREF="http://www.itscj.ipsj.or.jp/sc34/open/0990.pdf" REL="nofollow" rel="nofollow">Editied notes of the meeting.</a></p>
<p>Can you say if these link up with your experiances last week?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ed</title>
		<link>http://www.robweir.com/blog/2008/03/ooxml-macros-and-security.html#comment-1574</link>
		<dc:creator>Ed</dc:creator>
		<pubDate>Thu, 06 Mar 2008 02:16:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/2008/03/ooxml-macros-and-security.html#comment-1574</guid>
		<description>Hi Rob,&lt;br/&gt;&lt;br/&gt;Thank you for posting this comment about OOXML not documenting macros and its impact on interoperability - especially with MS documents that are free to use MS&#039; closed and proprietary scripting languages.&lt;br/&gt;&lt;br/&gt;I don&#039;t think that&#039;s been brought up anywhere as a natural consequence of the MACROBUTTON comment to the DIS.  It certainly opened my eyes.&lt;br/&gt;&lt;br/&gt;I agree with your statement that it appears that ISO is making up the rules as it goes along and that nothing would surprise me at this point.&lt;br/&gt;&lt;br/&gt;...Well - almost nothing.  I think I&#039;d be very surprised of MS/ECMA pulled the DIS from consideration for ISO standardization. -- but I don&#039;t think I&#039;d be surprised by anything less....</description>
		<content:encoded><![CDATA[<p>Hi Rob,</p>
<p>Thank you for posting this comment about OOXML not documenting macros and its impact on interoperability &#8211; especially with MS documents that are free to use MS&#8217; closed and proprietary scripting languages.</p>
<p>I don&#8217;t think that&#8217;s been brought up anywhere as a natural consequence of the MACROBUTTON comment to the DIS.  It certainly opened my eyes.</p>
<p>I agree with your statement that it appears that ISO is making up the rules as it goes along and that nothing would surprise me at this point.</p>
<p>&#8230;Well &#8211; almost nothing.  I think I&#8217;d be very surprised of MS/ECMA pulled the DIS from consideration for ISO standardization. &#8212; but I don&#8217;t think I&#8217;d be surprised by anything less&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob</title>
		<link>http://www.robweir.com/blog/2008/03/ooxml-macros-and-security.html#comment-1572</link>
		<dc:creator>Rob</dc:creator>
		<pubDate>Thu, 06 Mar 2008 00:19:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/2008/03/ooxml-macros-and-security.html#comment-1572</guid>
		<description>Hi James, ISO is improvising the process as they go.  Nothing you could tell me would surprise me at this point.</description>
		<content:encoded><![CDATA[<p>Hi James, ISO is improvising the process as they go.  Nothing you could tell me would surprise me at this point.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James</title>
		<link>http://www.robweir.com/blog/2008/03/ooxml-macros-and-security.html#comment-1571</link>
		<dc:creator>James</dc:creator>
		<pubDate>Wed, 05 Mar 2008 22:17:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/2008/03/ooxml-macros-and-security.html#comment-1571</guid>
		<description>Haha I thought that was the case but thank you for confirming it Rob.&lt;br/&gt;&lt;br/&gt;Some countries seem to be breaking silence where they can about the BRM... hopefully the NBs will get the message the DIS 29500 spec is not ready to be an ISO standard.&lt;br/&gt;&lt;br/&gt;Incidentally on groklaw there is a very interesting discussion about the ISO press release. Read one way it sounds like no or abstain votes can be changed to yes but it doesn&#039;t comment on yes to no votes. Any comments on that Rob? AFAIK countries are free to change their vote any way they want for the next 30 days? If a country changes to yes and others don&#039;t realise they can change to no (such as the US) it could still lead to the spec being railroaded through...</description>
		<content:encoded><![CDATA[<p>Haha I thought that was the case but thank you for confirming it Rob.</p>
<p>Some countries seem to be breaking silence where they can about the BRM&#8230; hopefully the NBs will get the message the DIS 29500 spec is not ready to be an ISO standard.</p>
<p>Incidentally on groklaw there is a very interesting discussion about the ISO press release. Read one way it sounds like no or abstain votes can be changed to yes but it doesn&#8217;t comment on yes to no votes. Any comments on that Rob? AFAIK countries are free to change their vote any way they want for the next 30 days? If a country changes to yes and others don&#8217;t realise they can change to no (such as the US) it could still lead to the spec being railroaded through&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob</title>
		<link>http://www.robweir.com/blog/2008/03/ooxml-macros-and-security.html#comment-1566</link>
		<dc:creator>Rob</dc:creator>
		<pubDate>Wed, 05 Mar 2008 14:34:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/2008/03/ooxml-macros-and-security.html#comment-1566</guid>
		<description>ODF has a &lt;office:script&gt; element that can either store the script inline or  use XLink to locate the script.  For an event model we use the W3C&#039;s XML Events Recommendation.&lt;br/&gt;&lt;br/&gt;ODF does not mandate any particular scripting language.  You can mix scripting languages within the same document if you want, though each &lt;script&gt; will need to declare what language it uses.&lt;br/&gt;&lt;br/&gt;API is the DOM representation of the document, or is implementation defined.&lt;br/&gt;&lt;br/&gt;So we&#039;ve gone far beyond the nothing that OOXML offers on this topic.</description>
		<content:encoded><![CDATA[<p>ODF has a &lt;office:script&gt; element that can either store the script inline or  use XLink to locate the script.  For an event model we use the W3C&#8217;s XML Events Recommendation.</p>
<p>ODF does not mandate any particular scripting language.  You can mix scripting languages within the same document if you want, though each &lt;script&gt; will need to declare what language it uses.</p>
<p>API is the DOM representation of the document, or is implementation defined.</p>
<p>So we&#8217;ve gone far beyond the nothing that OOXML offers on this topic.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James</title>
		<link>http://www.robweir.com/blog/2008/03/ooxml-macros-and-security.html#comment-1564</link>
		<dc:creator>James</dc:creator>
		<pubDate>Wed, 05 Mar 2008 13:49:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.robweir.com/blog/2008/03/ooxml-macros-and-security.html#comment-1564</guid>
		<description>Hi Rob,&lt;br/&gt;&lt;br/&gt;Please forgive my laziness for not looking it up myself in ISO 26300 but do you happen to know how macros are defined in that?&lt;br/&gt;&lt;br/&gt;Also thanks for the commentry on the BRM last week - it was a very interesting insight especially when combined with other blogs.&lt;br/&gt;&lt;br/&gt;I am looking forward to seeing the final votes at the end of the month - and given the US HoD&#039;s comments I hope the US changes it&#039;s position from yes to no!</description>
		<content:encoded><![CDATA[<p>Hi Rob,</p>
<p>Please forgive my laziness for not looking it up myself in ISO 26300 but do you happen to know how macros are defined in that?</p>
<p>Also thanks for the commentry on the BRM last week &#8211; it was a very interesting insight especially when combined with other blogs.</p>
<p>I am looking forward to seeing the final votes at the end of the month &#8211; and given the US HoD&#8217;s comments I hope the US changes it&#8217;s position from yes to no!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

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

