Re: [ebxml-bp] [ebBP] 7/21/2004: Guiding Principles

["David RR Webber" <david@drrw.info>]

Monica,

One more design principle:

o Can be used to implement internationally compliant business patterns.

DW.

----- Original Message ----- 
From: "David RR Webber" <david@drrw.info>
To: "Monica J. Martin" <Monica.Martin@Sun.COM>; "ebXML BP"
<ebxml-bp@lists.oasis-open.org>
Sent: Wednesday, July 21, 2004 7:37 PM
Subject: Re: [ebxml-bp] [ebBP] 7/21/2004: Guiding Principles


> Monica,
>
> I would add to this:
>
> o Business-centric, allowing access to BPM technology for business users
> o Supports context-driven approach - where generic business templates
>    can be adapted using context parameters
> o Layered approach - where BPSS is designed to manage process and
>    provide facilitation details and context to components in layers
>    below it and directed by linkage to business layer details above
> o Transport neutral approach - does not mandate specific transport
>     technology - instead defines characteristics and behaviours of
transport
>     layer.
> o  Uses a deterministic approach - so each part of a BPSS is deterministic
>     with known outcomes and results.
> o  Payload abstraction - provides logical models of business exchanges
>     that can be mapped to physical transaction instances and rules.
> o  Extensible rules model - rather than tieing to a specific execution
> engine
>     and syntax - allows rules to be defined at a business knowledge layer
>     that are then implemented as required by the implementation layer
>     components.
> o  Integrates into OASIS specification components such as ebMS, CPA,
>     CAM, CCTS and others.
> o  Uses XSD schema as the representation for XML instances derived
>     from BPSS - but otherwise is not solely reliant on XML as the only
>     means of implementation.
> o  Designed to provide means to define business processes for a SOA
>     and ebSOA deployment environment.
>
> Thanks, DW
>
> ----- Original Message ----- 
> From: "Monica J. Martin" <Monica.Martin@Sun.COM>
> To: "ebXML BP" <ebxml-bp@lists.oasis-open.org>
> Sent: Wednesday, July 21, 2004 7:20 PM
> Subject: [ebxml-bp] [ebBP] 7/21/2004: Guiding Principles
>
>
> > In the editors' F2F and during our June meetings [1], we discussed what
> > we may cite as our v2.0 "guiding principles". Those identified include
> > portions of:
> >
> >     * ebBP v2.0
> >           o UN/CEFACT modeling methodology
> >           o Unified Modeling Language (tm)
> >           o Possibly BPMN [2]
> >     * ebBP v3.0: Potentially referenced were: [3]
> >           o Petri nets
> >           o Event calculus
> >
> > I had an action to send these to the list and solicit comments. Note, no
> > requirement has been established that these are mandatory or represent
> > compliance criteria (note: 'guiding').  The v2.0 ones could be included
> > in the technical specification. Feedback DESIRED! Thanks.
> >
> > [1] Meeting minutes attached to meeting notice:
> > http://www.oasis-open.org/archives/ebxml-bp/200406/msg00165.html
> > [2] Pending from a proposal from JJ Dubray
> > [3] For further analysis
> >
> >
> >
> >
> >
>
>