OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebsoa message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: ebSOA Abstract draft 0.02


As promised, here is an abstract paragraph for a placeholder for now.

<caveat type="sleep_deprivation"/>

Abstract:

"This architecture extends a set of generalized service oriented 
architecture patterns to address the unique requirements of electronic 
business. Those requirements are captured within an updated document 
call the name_of_updated_requirements_here

WORK ITEM: UPDATE ebXML Requirements v 1.06 abstracting from ebXML 
specificity. Reference that document above.

This architecture takes into account work done in several standards 
development organizations including OASIS (Organization for the 
Advancement of Structured Information Systems), the W3C (World Wide Web 
Consortium), ISO (International Standards Organization, UN/CEFACT 
(United Nations Centre for Facilitation of Commerce and Trade) and 
others. It is meant to be illustrative and not prescriptive in nature.

The goal of this electronic business service oriented architecture 
specification is to describe a high level architecture blueprint and a 
set of accompanying patterns to describe an infrastructure to facilitate 
electronic business on a global scale in a secure, reliable and 
consistent manner. This shall be done in a manner that is not dependent 
on either ebXML or Web Services [NOTE: or should we just say "any 
specific standards"] standards, yet may allow for each for be used in 
conjunction with one another for implementation. Rather than contain the 
level of detail sufficient for implementation, references to components 
are made within this architecture that fulfill the normative 
functionality of the architecture.

This architecture is expressed in a series of logical views of abstract 
architectural components in various phases.

Readers should note that the components names within this document are 
names of architectural components and not necessarily synonymous with 
those project teams."

/d

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





[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]