<?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/"
		>
<channel>
	<title>Comments on: Model Portability in BPMN 2.0</title>
	<atom:link href="http://www.brsilver.com/wordpress/2008/09/21/model-portability-in-bpmn-20/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.brsilver.com/wordpress/2008/09/21/model-portability-in-bpmn-20/</link>
	<description>Bruce Silver's blog on business process management</description>
	<lastBuildDate>Sat, 27 Feb 2010 10:22:38 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Will BPMN 2.0 have &#8220;Model Portability&#8221;? &#171; Go Flow</title>
		<link>http://www.brsilver.com/wordpress/2008/09/21/model-portability-in-bpmn-20/comment-page-1/#comment-6851</link>
		<dc:creator>Will BPMN 2.0 have &#8220;Model Portability&#8221;? &#171; Go Flow</dc:creator>
		<pubDate>Tue, 30 Sep 2008 04:38:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.brsilver.com/wordpress/?p=367#comment-6851</guid>
		<description>[...] Silver asked the question, &#8220;What do you really need for model portability?&#8221; He points to four key [...]</description>
		<content:encoded><![CDATA[<p>[...] Silver asked the question, &#8220;What do you really need for model portability?&#8221; He points to four key [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2008-09-25 &#171; steinarcarlsen</title>
		<link>http://www.brsilver.com/wordpress/2008/09/21/model-portability-in-bpmn-20/comment-page-1/#comment-6844</link>
		<dc:creator>links for 2008-09-25 &#171; steinarcarlsen</dc:creator>
		<pubDate>Thu, 25 Sep 2008 21:22:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.brsilver.com/wordpress/?p=367#comment-6844</guid>
		<description>[...] Model Portability in BPMN 2.0 - BPMS Watch (tags: bpmn bpmn2.0) [...]</description>
		<content:encoded><![CDATA[<p>[...] Model Portability in BPMN 2.0 &#8211; BPMS Watch (tags: bpmn bpmn2.0) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bruce</title>
		<link>http://www.brsilver.com/wordpress/2008/09/21/model-portability-in-bpmn-20/comment-page-1/#comment-6843</link>
		<dc:creator>bruce</dc:creator>
		<pubDate>Tue, 23 Sep 2008 14:59:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.brsilver.com/wordpress/?p=367#comment-6843</guid>
		<description>Honestly, Phil, I did not expect we would have different perspectives on the need for model portability.  And I don&#039;t recall saying anything about human-readable XML in this piece, either.  I do have a preference for XML based on schemas and that works with regular XML tools, which would favor the IBM submission over BPDM.  Not sure what you mean by XML is the MS-DOS of whatever,  Is the issue that it has tags and is &quot;unfriendly&quot; to view in text format?  I guess then HTML is the MS-DOS of the web.</description>
		<content:encoded><![CDATA[<p>Honestly, Phil, I did not expect we would have different perspectives on the need for model portability.  And I don&#8217;t recall saying anything about human-readable XML in this piece, either.  I do have a preference for XML based on schemas and that works with regular XML tools, which would favor the IBM submission over BPDM.  Not sure what you mean by XML is the MS-DOS of whatever,  Is the issue that it has tags and is &#8220;unfriendly&#8221; to view in text format?  I guess then HTML is the MS-DOS of the web.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phil Gilbert</title>
		<link>http://www.brsilver.com/wordpress/2008/09/21/model-portability-in-bpmn-20/comment-page-1/#comment-6842</link>
		<dc:creator>Phil Gilbert</dc:creator>
		<pubDate>Tue, 23 Sep 2008 11:20:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.brsilver.com/wordpress/?p=367#comment-6842</guid>
		<description>Hi Bruce,

Good piece although, as you might expect, we have different perspectives on the requirements.  There is no need for &quot;human readable XML&quot; which, in any human-friendly world is an oxymoron.  What is required are, certainly, your #1 and #2 above, at a minimum.  Even the specification&#039;s statement that you quote puts the human in the graphical notation... not the XML.

We need to develop BPMN tools that are so good (and so interoperable, with deterministic interpretation of the diagrams) that humans-reading-XML isn&#039;t required.  That&#039;s a BPEL-like answer... we need to move forward in the power of graphical interfaces.  XML is the MS-DOS of model-driven computing.

Phil

ps - of course, there is disagreement on this within the BPMN spec-writing community at large.  Some vendors are quite happy to require that BPMS users be able to read XML.  I disagree.  We have the capability to make the notation rich enough... why don&#039;t we focus on that?  Could it be that there&#039;s corporate strategy involved... http://blog.lombardicto.com/2008/07/waiting-until-y.html</description>
		<content:encoded><![CDATA[<p>Hi Bruce,</p>
<p>Good piece although, as you might expect, we have different perspectives on the requirements.  There is no need for &#8220;human readable XML&#8221; which, in any human-friendly world is an oxymoron.  What is required are, certainly, your #1 and #2 above, at a minimum.  Even the specification&#8217;s statement that you quote puts the human in the graphical notation&#8230; not the XML.</p>
<p>We need to develop BPMN tools that are so good (and so interoperable, with deterministic interpretation of the diagrams) that humans-reading-XML isn&#8217;t required.  That&#8217;s a BPEL-like answer&#8230; we need to move forward in the power of graphical interfaces.  XML is the MS-DOS of model-driven computing.</p>
<p>Phil</p>
<p>ps &#8211; of course, there is disagreement on this within the BPMN spec-writing community at large.  Some vendors are quite happy to require that BPMS users be able to read XML.  I disagree.  We have the capability to make the notation rich enough&#8230; why don&#8217;t we focus on that?  Could it be that there&#8217;s corporate strategy involved&#8230; <a href="http://blog.lombardicto.com/2008/07/waiting-until-y.html" rel="nofollow">http://blog.lombardicto.com/20.....til-y.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Column 2 by Sandy Kemsley : Bookmarks for September 22nd</title>
		<link>http://www.brsilver.com/wordpress/2008/09/21/model-portability-in-bpmn-20/comment-page-1/#comment-6841</link>
		<dc:creator>Column 2 by Sandy Kemsley : Bookmarks for September 22nd</dc:creator>
		<pubDate>Mon, 22 Sep 2008 19:02:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.brsilver.com/wordpress/?p=367#comment-6841</guid>
		<description>[...] Model Portability in BPMN 2.0 - BPMS Watch - Bruce Silver&#039;s continuing commentary on the new BPMN 2.0 submission. Today: how portable are these models, anyway? [...]</description>
		<content:encoded><![CDATA[<p>[...] Model Portability in BPMN 2.0 &#8211; BPMS Watch &#8211; Bruce Silver&#39;s continuing commentary on the new BPMN 2.0 submission. Today: how portable are these models, anyway? [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: frenchdk</title>
		<link>http://www.brsilver.com/wordpress/2008/09/21/model-portability-in-bpmn-20/comment-page-1/#comment-6840</link>
		<dc:creator>frenchdk</dc:creator>
		<pubDate>Mon, 22 Sep 2008 05:55:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.brsilver.com/wordpress/?p=367#comment-6840</guid>
		<description>Great thoughts as always, Bruce.
Unfortunately BPMN will take some time to get to the specification standard of an old  language like FORTRAN but we can at least divide the tool builders into two camps ... those that care about compliance with the spec and portability and those that are simply ticking boxes on a tool purchaser&#039;s RFP. Even if the spec does not enumerate the rules, a tool builder can produce an explicit compliance list and over a few iterations of a few tools we (as users) might see a composite set of rules. Perhaps at BPMN 2.1 that composite set will be an annex to the spec.</description>
		<content:encoded><![CDATA[<p>Great thoughts as always, Bruce.<br />
Unfortunately BPMN will take some time to get to the specification standard of an old  language like FORTRAN but we can at least divide the tool builders into two camps &#8230; those that care about compliance with the spec and portability and those that are simply ticking boxes on a tool purchaser&#8217;s RFP. Even if the spec does not enumerate the rules, a tool builder can produce an explicit compliance list and over a few iterations of a few tools we (as users) might see a composite set of rules. Perhaps at BPMN 2.1 that composite set will be an annex to the spec.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
