Re: chartering - external related work

There is no XKMS WG active at this time.  But, *if* there needs to be a update to the spec, it will be probably via XML Security WG - by possibly modification of the charter or something like that as this was done under W3C.  It is very much possible that there is no need to update the same at this time.

Thanks

/Shivaram
--
Strong Authentication, SOA, Web Services, PKI, Software Architecture, Product Strategy and Management Consultants:
http://www.TrustStix.com/ 



----- Original Message ----
From: Frederick Hirsch <frederick.hirsch@nokia.com>
To: ext Sean Mullan <Sean.Mullan@Sun.COM>
Cc: Frederick Hirsch <frederick.hirsch@nokia.com>; XMLSec XMLSec <public-xmlsec-maintwg@w3.org>
Sent: Monday, February 25, 2008 6:25:13 AM
Subject: Re: chartering - external related work


Sean

I left off WSS because the TC is closed (and there is no WSS  
maintenance TC). Much of that community is in other groups like WS-SX.

XAdES seems a reasonable addition.

Again I don't think there is a current XKMS W3C WG.

My apologies on the delayed reply, thought I'd already sent this.

regards, Frederick

Frederick Hirsch
Nokia



On Feb 19, 2008, at 2:14 PM, ext Sean Mullan wrote:

> Frederick Hirsch wrote:
>> We will need to update the draft charter for the upcoming XML  
>> Security WG to include dependencies on internal and external  
>> groups, similar to what is in the current WG charter.
>> I suggest we list OASIS dependencies as follows:
>> OASIS:
>> The Working Group should coordinate with the following relevant  
>> OASIS Technical Committees (TCs) that are direct users of XML  
>> Security:
>> * OASIS Digital Signature Services eXtended (DSS-X) TC - Advancing  
>> digital signature services standards for XML
>> * OASIS Election and Voter Services TC - Enabling the exchange of  
>> data for public and private election services
>> * OASIS eXtensible Access Control Markup Language (XACML) TC -  
>> Developing authorization and entitlement policies
>> * OASIS LegalXML Electronic Court Filing TC - Using XML to create  
>> and transmit legal documents among attorneys, courts, litigants,  
>> and others
>> * OASIS Security Services Technical Committee (SSTC) - Using XML  
>> Security in its SAML specifications for the creation and exchange  
>> of authentication, authorization and attribute information.
>> * OASIS Universal Business Language (UBL) TC - Defining a common  
>> XML library of business documents (purchase orders, invoices, etc.)
>> * OASIS Web Services Federation (WSFED) TC - Extending the basic  
>> federation capabilities enabled by Web service Security  
>> specifications.
>> * OASIS Web Services Secure Exchange (WS-SX) - Extending the OASIS  
>> Web Services Security (WSS) standards to enable trusted SOAP  
>> message exchanges involving multiple message exchanges and to  
>> define security policies that govern the formats and tokens of  
>> such messages.
>> * OASIS Web Services Transaction (WS-TX) TC - Defining protocols  
>> for coordinating the outcome of distributed application actions
>
> Probably an oversight, but you missed WSS in this list above. Also  
> what about XKMS and XAdES?
>
>> The following are indirect users of XML Security:
>> * OASIS ebXML Messaging Services TC - Defining the transport,  
>> routing and packaging of e-business transactions. References OASIS  
>> Web Services Security which uses XML Security.
>> * OASIS Provisioning Services TC - Providing an XML framework for  
>> managing the provisioning and allocation of identity information  
>> and system resources within and between organizations. References  
>> OASIS Web Services Security which uses XML Security.
>> Is any work missing, or should any be removed or any descriptions  
>> corrected (from charters)?
>> I also suggest continuing to include Liberty Alliance and WS-I as  
>> in the current WG charter.
>> regards, Frederick
>> Frederick Hirsch
>> Nokia
>