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


Help: OASIS Mailing Lists Help | MarkMail Help

fwsi message

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

Subject: OASIS FWSI TC - Potential Liasing with OASIS Electronic Business Service Oriented Architecture (ebSOA) TC

Hello to all

	After going through the ebSOA Technical Architecture, we found some relevance / possible USAGE of SOME (Notification Engine, LogUtility, SecureSOAP FEs) of our Functional Elements Specification and hence would like to bring up an AGENDA Item in your forthcoming TC Meeting for potential liasing with FWSI Functional Elements Specification.

	I have given breif overview of those functional elements like Notification Engine FE, LogUtility FE, SecureSOAP FE, etc.

Notification Engine FE

	In an increasingly mobile world, people want access to the information they need regardless of their location.  A large number of organisations with commercial web sites and customer-facing applications are working to develop notification services that provide data subscription and delivery functionalities.  These services enable organisations to provide their customers and employees with the relevant information when required so that timely and informed decisions can be made.
Key Features

Sends schedule and unscheduled notification through multiple channels.  Current supported channels are:
Short Messaging Service (SMS)
Alphanumeric Paging
Supports both APIs and web service invocations. 

Log Utility FE

	Preparing disparate data stores for logging application information is often a tedious and time consuming task.  This is deemed as non-ideal.  It would be more efficient if data source could be set up dynamically through the client, saving precious time of the data source administrator.  In addition, simple interfaces should be made available for logging information into the desired data source.
Key Features

Prepares disparate data sources for logging programmatically.  Current supported data sources/outputs includes: Relational Database, XML File, Flat File & Console
Analyses the data sources for statistical variances.
Backups the data source.
Allows viewing of information stored in the data sources.
Allows client to write into the respective data sources.
Supports both APIs and web service invocations.


	Security is of utmost importance in the proliferation of web services.  Without it, communication among various parties would be restricted to trivial and unimportant information exchange.  This is the challenge of the Secure Soap Management Core Service. 
Key Features

Secure SOAP Management Core Service secure the SOAP message based on the following standards:
XML Encryption Syntax and Processing (www.w3.org/TR/xmlenc-core/)
XML Signature Syntax and Processing (www.w3.org/TR/xmldsig-core/) 
Provides functionality to digitally sign a SOAP message
Encrypts a complete SOAP message or part of the SOAP message
Decrypts the encrypted SOAP message
Validates the signed SOAP message
Check the security status (signed or encrypted) of the SOAP message
Supports both APIs and web service invocation  

For more information, please download the Functional Elements Committee Specification Document from OASIS FWSI TC website.


FWSI TC - FESC Member,

-----Original Message-----
From: John Hardin [mailto:john@maphin.net]
Sent: Thursday, July 21, 2005 8:42 PM
To: Ramasamy S/O Valliappan; ebsoa@lists.oasis-open.org;
Subject: Re: OASIS Electronic Business Service Oriented Architecture
(ebSOA) TC document - ENQUIRY

Hello to all on the FWSI TC -

Note: ebSOA members, we are liaison'ed to the FWSI TC which has many of 
it's members in Singapore, India and eastern countries. They are 
defining some similar items to ours and the SOA-RM group. We are 
"cross-pollinating" each others' groups.

Vasco, Goran or Dale - please send FERA presentation and anything else 
that you deem necessary to not only the ebSOA group but also the FWSI TC.

Ramasamy -

There is not any draft of the Tech Arch 2.0 document. We have just 
gotten past the IPR statements on material that was donated from 
ebXMLsoft.com and CPD Associates. The material is the abstract model 
from FERA and detail related. FERA = Federated Enterprise Reference 

We are now working on the outline, and will for probably the next week 
or two, then we will begin editing. This version 2.0 of the Technical 
Architecture document will incorporate Service Oriented Architecture 
concepts and methods. This will be in addition to the ebXML technical 
usage that exists in the v.1.04 document. We will also be updating the 
ebMS, CPPA and reg/rep information.

You can view the Technical Architecture v1.04 here:


john c hardin
606.813.4316 cell

"The new electronic interdependence recreates the world in the image of 
a global village."

     Marshall McLuhan, "Gutenberg Galaxy", 1962

Ramasamy S/O Valliappan wrote:
> Hi John
> 	We are members of OASIS Framework for Web Service Implementation (FWSI). We are looking for your architecture and implementation document as stated in your charter. 
> 	We have already got the document named "Outline for Tech Arch 2.0 draft updated 7/14/05 (TA_Outline_v2.0_14_july_2005.doc)". We would like to know are there any working drafts of the architecture and implementation that you can pass to us ? 
> 	Thank you.
> From
> V. RAM
> SIMTech.

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