Comments on: The Business Process Analytics Format (BPAF)

By: Elias Krzynowek

Elias Krzynowek — Fri, 05 Mar 2010 05:17:18 +0000

I will be away on business can they deliver to a P.O. Box?

By: Standardizing event logs — Flux Capacitor

Standardizing event logs — Flux Capacitor — Wed, 08 Jul 2009 00:30:00 +0000

[...] the standardization process of the new Business Process Analytics Format (BPAF) for quite a while. Read his post to see what the new format will look like, and to join the [...]

By: Far Flung Analytics - BPAF « Go Flow

Far Flung Analytics - BPAF « Go Flow — Tue, 24 Feb 2009 04:10:39 +0000

[...] 23, 2009 Filed under: Uncategorized | Michael zur Muehlen has written a short article on “The Business Process Analytics Format (BPAF)“. This is a portable format that will allow the history events from multiple BPM servers to [...]

By: Michael zur Muehlen

Michael zur Muehlen — Mon, 23 Feb 2009 20:26:08 +0000

Chris, thank you very much for the suggestion – that is exactly the kind of feedback we were hoping for. I will look at this change and post an updated version later today.

By: Process for the Enterprise » Blog Archive » Business Process Visualization

Mon, 23 Feb 2009 20:10:21 +0000

[...] brings me to an article on The Business Process Analytics Format (BPAF). Good read, and a good reminder that there are folks out there trying to put standardized [...]

By: Chris Han

Chris Han — Mon, 23 Feb 2009 18:05:40 +0000

Great! Just one thing: I think it’s better to move bpaf:DataElement node under an additional node called bpaf:DataElements – an explicit collection-type node. This way, we will be able to map this schema to a object model elegantly. You can easily model a class hierarchy representing that an Event class has a collection-type memeber called DataElements which consists of DataElement-type items. You can’t directly model an Event class that has an ambiguous number of DataElement described by maxOccurs=”unbounded” attribute. I believe this will ease the adoption of this standard in practice.