Re: [ebsoa] Sample Pattern: Receptionist as a Hub

[Duane Nickull <dnickull@adobe.com>]

I would say we had consensus on this issue.

Duane

Matthew MacKenzie wrote:

>You should have stuck around during the last meeting and debated this.
>We've pretty much agreed on using some kind of pattern language.
>
>Patterns can be expressed in a fashion that appeals not only to programmers,
>but the other interested folks...although a little programmer-centric focus
>would be good for 'eb' at this point.
>
>
>-----Original Message-----
>From: David RR Webber [mailto:david@drrw.info] 
>Sent: Sunday, May 09, 2004 6:27 PM
>To: Chiusano Joseph; Matthew MacKenzie
>Cc: ebSOA
>Subject: Re: [ebsoa] Sample Pattern: Receptionist as a Hub
>
>Joe / Matt,
>
>I'm not a big fan of picking a pattern language - as
>that tends to immediately lock you down into
>programmer land.
>
>Since we are 'eb' focused - the BCM approach is
>saying that there are 'eb' patterns out there that
>work for specific domains and CoI.  So - go there - makes
>those available to the community - and tailor them so they
>drive your solution stack.
>
>Some patterns can work great as office documents, others
>require agent tools, other form guides.  We should not
>limit ourselves - but rather describe the capabilities the
>pattern technology needs to enable.
>
>The users of the patterns should be able to leverage:
>context, linking and switching, XML, and scripting, to
>drive the implementation layer from the logical and
>conceptual 'eb' layers.
>
>This allows the solution providers to work with
>patterns and technology they know and trust
>with their CoI, while leveraging the OASIS
>ebSOA stack as the delivery layer.
>
>DW
>
>----- Original Message ----- 
>From: "Chiusano Joseph" <chiusano_joseph@bah.com>
>To: "Matthew MacKenzie" <mattm@adobe.com>
>Cc: "ebSOA" <ebsoa@lists.oasis-open.org>
>Sent: Sunday, May 09, 2004 1:44 PM
>Subject: Re: [ebsoa] Sample Pattern: Receptionist as a Hub
>
>
>  
>
>>Thanks Matt. Applying this to technology and integration, I believe the
>>rough equivalent would be an integration broker.
>>
>>If folks agree, what would be the next step given our charter? To show
>>how an integration broker can be used within an architecture to
>>communicate between (for example) 2 ebXML-based* systems, or perhaps
>>from a non-ebXML-based system to one that is?
>>
>>Just trying to get an early sense of where this patterns path could take
>>us, before we go too far with it.
>>
>>Joe
>>
>>*we would need to define what "ebXML-based" means, of course
>>
>>Matthew MacKenzie wrote:
>>    
>>
>>>Here is an example of a "Pattern". Patterns can be defined for all kinds
>>>      
>>>
>of processes, not just software development. We may have to do a bit of
>research on what an appropriate pattern language would be for our work, but
>this is a good example.
>  
>
>>>      
>>>
>http://www.comp.lancs.ac.uk/computing/research/cseg/projects/pointer/pattern
>s/receptionistAsAHub/receptionistAsAHub.html
>  
>
>>>___________________________
>>>Matthew MacKenzie
>>>Senior Architect
>>>IDBU Server Solutions
>>>Adobe Systems Canada Inc.
>>>http://www.adobe.com/products/server/
>>>mattm@adobe.com
>>>+1 (506) 871.5409
>>>      
>>>
>>-- 
>>Kind Regards,
>>Joseph Chiusano
>>Associate
>>Booz | Allen | Hamilton
>>
>>    
>>
>
>
>  
>

-- 
Senior Standards Strategist
Adobe Systems, Inc.
http://www.adobe.com