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


Help: OASIS Mailing Lists Help | MarkMail Help

tc-announce message

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

Subject: WS-Federation v1.2 Submitted for OASIS Standard Approval Ballot

OASIS Members:

The OASIS Web Services Federation (WSFED) Technical Committee has  
submitted the following specification, which is an approved Committee  
Specification, to be considered as an OASIS Standard:

Web Services Federation Language (WS-Federation) Version 1.2

The text of the TC submission is appended.

You now have until 15 April to familiarize yourself with the  
submission and provide input to your organization's voting  

On 16 April, a Call For Vote will be issued to all Voting  
Representatives of OASIS member organizations. They will have until  
the last day of April, inclusive, to cast their ballots on whether  
this Committee Specification should be approved as an OASIS Standard  
or not.

Members who wish to discuss this ballot may do so through member-discuss@lists.oasis-open.org 

In accordance with the OASIS Technical Committee Process, this  
Committee Specification has already completed the necessary 60-day  
public review period as noted in the submission below.

The normative TC Process for approval of Committee Specifications as  
OASIS Standards is found at

Any statements related to the IPR of this specification are posted at:

Your participation in the review and balloting process is greatly  


Mary P McRae
Director, Technical Committee Administration
OASIS: Advancing open standards for the information society
email: mary.mcrae@oasis-open.org
web: www.oasis-open.org
twitter: fiberartisan
phone: 1.603.232.9090


WSFED OASIS Submission of WS-Federation 1.2

(a) Links to the approved Committee Specification in the TC's document  
repository, and any appropriate supplemental documentation for the  
specification, both of which must be written using the OASIS templates.


The schemas for this specification can be located at:

(b) The editable version of all files that are part of the Committee  


(c) Certification by the TC that all schema and XML instances included  
in the specification, whether by inclusion or reference, including  
fragments of such, are well formed, and that all expressions are valid;

Yes the XML has been verified.

(d) A clear English-language summary of the specification;

This specification defines mechanisms to allow different security  
realms to federate, such that authorized access to resources managed  
in one realm can be provided to security principals whose identities  
and attributes are managed in other realms.   This includes mechanisms  
for brokering of identity, attribute, authentication and authorization  
assertions between realms, and privacy of federated claims.

(e) A statement regarding the relationship of this specification to  
similar work of other OASIS TCs or other standards developing  

This specification utilizes the WS-Security, WS-Trust and WS- 
SecurityPolicy specifications.

(f) Certification by at least three OASIS member organizations that  
they are successfully using the specification;

(g) The beginning and ending dates of the public review(s), a pointer  
to the announcement of the public review(s), and a pointer to an  
account of each of the comments/issues raised during the public review  
period(s), along with its resolution;
1st Public Review
Began 16 July 2008 and ended 14 September 2008.
See http://lists.oasis-open.org/archives/tc-announce/200807/msg00008.html
2nd Public Review
Began 13 January 2009 and ended 12 February 2009
See http://lists.oasis-open.org/archives/tc-announce/200901/msg00013.html
Issues and resolutions: http://docs.oasis-open.org/wsfed/issues/Issues.xml

(h) An account of and results of the voting to approve the  
specification as a Committee Specification, including the date of the  
ballot and a pointer to the ballot;


(i) An account of or pointer to votes and comments received in any  
earlier attempts to standardize substantially the same specification,  
together with the originating TC's response to each comment;

This is the first submission to standardize this specification.

(j) A pointer to the publicly visible comments archive for the  
originating TC;


(k) A pointer to any minority reports submitted by one or more Members  
who did not vote in favor of approving the Committee Specification,  
which report may include statements regarding why the member voted  
against the specification or that the member believes that Substantive  
Changes were made which have not gone through public review; or  
certification by the Chair that no minority reports exist.

No minority reports exist.

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