Re: [eppext] [apps-discuss] D-BRIEF 00

["Hollenbeck, Scott" <[e-mail]>]

One more comment regarding this statement below:

"Unfortunately I’m not able to release the UI editor or the actual engine code that operates the framework due to IP concerns; however I will attempt again in a few weeks to release at least the engine code."

I'd very much like to see an IPR statement included with the document. This will help ensure that anyone attempting to implement the framework is fully informed of the IP concerns.

Scott

> -----Original Message-----
> From: EppExt [mailto:[e-mail]] On Behalf Of Barry Leiba
> Sent: Thursday, June 25, 2015 1:32 PM
> To: Mike O'Connell; [e-mail]
> Subject: Re: [eppext] [apps-discuss] D-BRIEF 00
> 
> I'm sending this along to the eppext folks, who seem like an
> appropriate gang to ask for review here.  Mike is planning to send
> this to the Independent Stream Editor (ISE) after he gets some
> feedback.  What he's hoping for here is some review and comment to
> improve the document before he does that.  If you have some time and
> comments, please make them in the message thread on the apps-discuss
> list (and to Mike).  Thanks.
> 
> Barry
> 
> On Tue, Jun 23, 2015 at 8:59 AM, Mike O'Connell <[e-mail]>
> wrote:
> > Hi Apps,
> >
> > Thanks to Barry Leiba for guiding me along the process to submit this
> draft.
> >
> > I’ve submitted a draft for Dynamic Business-Rules Implementation and
> > Execution Framework (D-BRIEF).
> >
> > Summary:
> >
> > D-BRIEF is an XML framework built to contain a scriptable language
> which
> > operates on business objects within a real-time system.
> >
> >
> > Ideology:
> >
> > The foundation concepts include:
> >
> > Object -> Event mappings
> > Scriptable language container for running “micro" commands on a
> request
> > based system
> > In real-time refresh of business rules, rapid turn-around time
> > UI Editable
> > Unix style “micro” commands
> > By utilising a “cron” style system one can implement an asynchronous
> > interface that executes Object -> Events at a later stage.
> >
> >
> > Within the referenced libraries we wrote additional meta style calls
> which
> > allowed us to manipulate the session as follows:
> >
> > Invoke another Object -> Event synchronously which simplifies the
> layout of
> > the business policy, we use it for derivative objects.
> > Exit execution at any point
> > Queue a task for asynchronous processing
> >
> >
> >
> > Unfortunately I’m not able to release the UI editor or the actual
> engine
> > code that operates the framework due to IP concerns; however I will
> attempt
> > again in a few weeks to release at least the engine code.
> >
> > The framework is defined in:
> > https://datatracker.ietf.org/doc/draft-oconnell-dbrief/
> >
> > Thank you for your time.
> >
> > Sincerely,
> >
> > --
> >
> > Mike O'Connell
> > Domain Name Services (Pty) Ltd
> > [phone]
> >
> >
> > _______________________________________________
> > apps-discuss mailing list
> > [e-mail]
> > https://www.ietf.org/mailman/listinfo/apps-discuss
> >
> 
> _______________________________________________
> EppExt mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/eppext