<?xml version="1.0" encoding="UTF-8"?> <rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:wfw="http://wellformedweb.org/CommentAPI/"
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:slash="http://purl.org/rss/1.0/modules/slash/"
><channel><title>SAPERION Blog &#187; SAPERION</title> <atom:link href="http://www.saperionblog.com/lang/en/tag/saperion/feed/" rel="self" type="application/rss+xml" /><link>http://www.saperionblog.com</link> <description>ECM - BPM - COMPLIANCE - JCR - CMIS - SCRUM</description> <lastBuildDate>Wed, 28 Jul 2010 10:07:18 +0000</lastBuildDate> <generator>http://wordpress.org/?v=abc</generator> <language>en</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <item><title>SAPERION meets BPMN</title><link>http://www.saperionblog.com/lang/en/saperion-meets-bpmn/653</link> <comments>http://www.saperionblog.com/lang/en/saperion-meets-bpmn/653#comments</comments> <pubDate>Wed, 11 Nov 2009 14:41:10 +0000</pubDate> <dc:creator>Björn Meyer-Caspari</dc:creator> <category><![CDATA[deutsch]]></category> <category><![CDATA[general]]></category> <category><![CDATA[BPMN]]></category> <category><![CDATA[Business Process Modeling Notation]]></category> <category><![CDATA[SAPERION]]></category> <category><![CDATA[Workflow]]></category><guid
isPermaLink="false">http://www.saperionblog.com/?p=653</guid> <description><![CDATA[Autor: Björn Meyer-Caspari, zu seiner Masterarbeit betreut von Dr. Martin BartonitzDie Business Process Modeling Notation (BPMN) ist  - auch aktuellen Umfragen zufolge &#8211; als Standard für die Geschäftsprozessmodellierung stark auf dem Vormarsch. Vieles deutet daraufhin, dass die Verbreitung der seit 2002 entwickelten Notation auch mit dem – voraussichtlich Mitte des nächsten Jahres &#8211; anstehenden Versionsupdate [...]]]></description> <wfw:commentRss>http://www.saperionblog.com/lang/en/saperion-meets-bpmn/653/feed</wfw:commentRss> <slash:comments>2</slash:comments> </item> <item><title>SAPERION meets Rule Engine</title><link>http://www.saperionblog.com/lang/en/saperion-meets-rule-engine/584</link> <comments>http://www.saperionblog.com/lang/en/saperion-meets-rule-engine/584#comments</comments> <pubDate>Thu, 22 Oct 2009 11:28:53 +0000</pubDate> <dc:creator>Alexander Groenewold</dc:creator> <category><![CDATA[english]]></category> <category><![CDATA[general]]></category> <category><![CDATA[Drools]]></category> <category><![CDATA[ILOG]]></category> <category><![CDATA[Rule Engine]]></category> <category><![CDATA[SAPERION]]></category> <category><![CDATA[Workflow]]></category><guid
isPermaLink="false">http://www.saperionblog.com/?p=584</guid> <description><![CDATA[Authors: Alexander Groenewold, Jan Schwarz, Dr. Martin Bartonitz
Almost every company has its own set of business rules and processes. This could make even the simple and common task of determining the next receiver of a workflow a complex and in-transparent decision. A frequent occurrence of this problem is for example during invoice processing, where several [...]]]></description> <wfw:commentRss>http://www.saperionblog.com/lang/en/saperion-meets-rule-engine/584/feed</wfw:commentRss> <slash:comments>1</slash:comments> </item> <item><title>CMIS, Chemistry and SAPERION Content Repository</title><link>http://www.saperionblog.com/lang/en/cmis-chemistry-and-saperion-content-repository/517</link> <comments>http://www.saperionblog.com/lang/en/cmis-chemistry-and-saperion-content-repository/517#comments</comments> <pubDate>Fri, 25 Sep 2009 14:22:03 +0000</pubDate> <dc:creator>Michael Mertins</dc:creator> <category><![CDATA[english]]></category> <category><![CDATA[products]]></category> <category><![CDATA[CEVAs]]></category> <category><![CDATA[Chemistry]]></category> <category><![CDATA[CMIS]]></category> <category><![CDATA[SAPERION]]></category> <category><![CDATA[SCR]]></category><guid
isPermaLink="false">http://www.saperionblog.com/?p=517</guid> <description><![CDATA[Content Management Interoperability Services (CMIS) is an upcoming standard for exposing web services     (primarily REST) on top of various types of content repositories. Among them: SAPERION Content Repository (SCR).
While CMIS is in the making, Apache Chemistry is a readily available implementation that delivers most of what is needed to make CMIS work on top of [...]]]></description> <wfw:commentRss>http://www.saperionblog.com/lang/en/cmis-chemistry-and-saperion-content-repository/517/feed</wfw:commentRss> <slash:comments>2</slash:comments> </item> </channel> </rss>
<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk
Page Caching using disk (user agent is rejected)
Database Caching 22/46 queries in 0.237 seconds using disk

Served from: www.saperionblog.com @ 2010-07-30 21:45:32 -->