The OASIS TC Process, the policy document governing work at OASIS, is a product of your Board of Directors. Each July, the Board’s Process Committee presents its list of proposed changes to the full Board for consideration. Any changes proposed are typically in response to issues the Committee has observed or that have been brought to the Committee by members.

This past Wednesday, July 25th, the OASIS Board of Directors approved a set of updates that address significant pain points we have observed over the past few years. This email gives a short summary of the changes. An online meeting will be held in August to explain them in more detail and additional documentation will be send out in the weeks ahead.

The updated process takes effect tomorrow, August 1st. The changes:

• Eliminate the need for public reviews for non-material content changes
• Allow Statements of Use from non-OASIS members
• Ease the process of rechartering
• Allow all TCs to make ballot motions by email without having to adopt standing rules
• Clarify how a TC can close a sub-committee
• Clairify that documents referenced in a proposed Charter must be publicly available.

Each of these is discussed below.

1. Eliminate the need for public reviews for non-material content changes

The current TC Process requires a public review even if the changes made to a draft are trivial (for example mis-spellings or broken links). This has put TCs in the position of having to decide between holding a public review of no value or approving a final document with known deficiencies.

Under the approved process, a TC will now be able to request a Special Majority Vote to approve a Committee Specification or Committee Note when the only changes since the last public review are non-material. The TC will need to provide a record of the changes made along with their motion to proceed with the ballot.

In order to ensure transparency and accountability, TC Admin will announce such ballots to the membership. When the ballot closes, assuming it passes, the draft will be published as a Committee Specification or Committee Note. Note that should any OASIS member object that some of the changes are indeed material, the ballot will stop and the TC will need to do another public review.

Based on my experience this past year, I expect this to reduce the number of public reviews by as much as 25%. Even better, it will enable you to make those last finishing touches that will improve the quality of your final deliverables without incurring any process penalty.

See the definition of “non-material change” in the Definitions section and section 3.3, Approval of a Committee Specification or Committee Note for the description of the new approval process.

2. Allow Statements of Use from non-OASIS members

Statements of Use are required before a Committee Specification can be presented to the OASIS members for consideration as a Candidate OASIS Standard. The current TC Process requires that all Statements of Use come from OASIS members. For some TCs this has posed a barrier to advancing their work because the TC is small and most implementations have been done outside OASIS.

Under the approved process, a TC will be allowed to accept up to two of the three required Statements of Use from non-OASIS members.

See the new definition of “Statement of Use” in the Definitions section and section 3.4.1, Submission of a Candidate OASIS Standard for the change to the submission requirement.

3. Rechartering is now easier

Under the current TC Process, rechartering a TC has required starting a new Kavi group, giving the TC a new name abbreviation and closing the TC for an extended period of time.

Under the approved process, the TC will keep its existing Kavi resources, mailing list, document archive, etc. The TC will be able to continue working under the original charter up to the week before the first meeting under the new charter at which time members will need to rejoin the TC. Rechartering will be far less disruptive to the TC’s work schedule.

See section 2.12, TC Rechartering for the new description of rechartering.

4. Standing rules to allow ballot motions by email no longer must be adopted as standing rules

Under the current TC Process, if a TC wishes to allow motions to open electronic ballots to be made by email, the TC must adopt a standing rule allowing this.

Under the approved TC Process, this is now standard practice and is available to all TCs with no special action.

See the last sentence of section 2.13, TC Voting for the new text allowing this.

5. Clarification on closing TC sub-committees

The current TC Process is silent on how a TC closes a sub-committee. The approved TC Process clarifies that this may be done by resolution of the TC.

See the last sentence of section 2.14, TC Subcommittees for the new text.

5. Documents referenced in a proposed Charter must be publicly available.

This change clarifies that if a document is referenced in a proposed TC Charter, it must be available from a public source. Note that this does not mean that it must be available by a hypertext link, but simply that there must be some public source through which interested parties may obtain copies.

See the first paragraph of section 2.2, TC Formation for the revised text.

The revised TC Process will be available at http://www.oasis-open.org/policies-guidelines/tc-process beginning tomorrow, August 1st.

The OASIS eXtensible Access Control Markup Language (XACML) TC [1] members have recently approved a Committee Specification Draft (CSD) and submitted this specification for 30-day public review:

XACML Intellectual Property Control (IPC) Profile Version 1.0
Committee Specification Draft 03 / Public Review Draft 03
17 May 2012

Specification Overview:

This specification defines a profile for the use of XACML in expressing policies for intellectual property control (IPC). It defines standard attribute identifiers useful in such policies, and recommends attribute value ranges for certain attributes.

TC Description:

The XACML Technical Committee defines schemas for representing authorization and entitlement policies. This Profile deals with defining Policies for securing Intellectual Property assets.

Public Review Period:

The public review starts 20 July 2012 and ends 19 August 2012.

This is an open invitation to comment. OASIS solicits feedback from potential users, developers and others, whether OASIS members or not, for the sake of improving the interoperability and quality of its technical work.

URIs:

The prose specification document and related files are available here:

Editable Source (Authoritative):
http://docs.oasis-open.org/xacml/3.0/ipc/v1.0/csprd03/xacml-3.0-ipc-v1.0-csprd03-en.doc

HTML:
http://docs.oasis-open.org/xacml/3.0/ipc/v1.0/csprd03/xacml-3.0-ipc-v1.0-csprd03-en.html

PDF:
http://docs.oasis-open.org/xacml/3.0/ipc/v1.0/csprd03/xacml-3.0-ipc-v1.0-csprd03-en.pdf

ZIP distribution file (complete):

For your convenience, OASIS provides a complete package of the prose specification and related files in a ZIP distribution file. You can download the ZIP file here:

http://docs.oasis-open.org/xacml/3.0/ipc/v1.0/csprd03/xacml-3.0-ipc-v1.0-csprd03-en.zip

Additional information about the specification and the OASIS eXtensible Access Control Markup Language (XACML) TC may be found at the TC’s public home page located at:

http://www.oasis-open.org/committees/xacml/

Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility which can be accessed via the button labeled “Send A Comment” at the top of the TC public home page, or directly at:

http://www.oasis-open.org/committees/comments/form.php?wg_abbrev=xacml

Feedback submitted by TC non-members for this work and for other work of this TC is publicly archived and can be viewed at:

http://lists.oasis-open.org/archives/xacml-comment/

All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the TC members. In connection with this public review of XACML Intellectual Property Control (IPC) Profile Version 1.0, we call your attention to the OASIS IPR Policy [2] applicable especially [3.0] to the work of this technical committee. All members of the TC should be familiar with this document, which may create obligations regarding the disclosure and availability of a member’s patent, copyright, trademark and license rights that read on an approved OASIS specification.

OASIS invites any persons who know of any such claims to disclose these if they may be essential to the implementation of the above specification, so that notice of them may be posted to the notice page for this TC’s work.

========== Additional references:

[1] OASIS eXtensible Access Control Markup Language (XACML) TC
http://www.oasis-open.org/committees/xacml/

[2] http://www.oasis-open.org/who/intellectualproperty.php

[3] http://www.oasis-open.org/committees/xacml/ipr.php
http://www.oasis-open.org/who/intellectualproperty.php#s10.2.3
RF on Limited Terms

We are pleased to announce the approval and publication of an OASIS Committee Note (CN) by the members of the OASIS Energy Market Information Exchange (eMIX) TC [1]:

TeMIX: a Transactive Profile of EMIX 1.0 Version 1.0
Committee Note 01
06 June 2012

Overview:
TeMIX (Transactive Energy Market Information Exchange) is a profile of the EMIX information model for Transactive Energy. TeMIX tenders and transactions are useful for price discovery, negotiation and response to grid conditions using many small, automated tenders and transactions.

URIs:
The Committee Notes is available here:

PDF (Authoritative):
http://docs.oasis-open.org/emix/emix-temixbrief/v1.0/emix-temixbrief-v1.0.pdf

HTML:
http://docs.oasis-open.org/emix/emix-temixbrief/v1.0/emix-temixbrief-v1.0.html

Editable source:
http://docs.oasis-open.org/emix/emix-temixbrief/v1.0/emix-temixbrief-v1.0.doc

Members of the EMIX TC requested a Special Majority Vote to approve the Committee Note. The Committee Note Draft had been released for public review as required by the TC Process [2]. The vote to approve at Committee Note (CN) level passed [3], and the approved CN01 is now available online in the OASIS Library as referenced above.

Our congratulations to the TC on achieving this milestone.

========== Additional references:

[1] OASIS Energy Market Information Exchange (eMIX) TC
http://www.oasis-open.org/committees/emix/

[2] Public reviews
30-day public review, 31 October 2011: https://lists.oasis-open.org/archives/tc-announce/201110/msg00015.html

[3] CN ballot
https://www.oasis-open.org/committees/ballot.php?id=2243

We are pleased to announce the approval and publication of two OASIS Committee Notes (CN) by the members of the OASIS Energy Market Information Exchange (eMIX) TC [1]:

EMIX 1.0 and the OASIS Smart Grid Suite of Standards Version 1.0
Committee Note 01
06 June 2012

Using EMIX 1.0 to support Transactive Energy Markets Version 1.0
Committee Note 01
06 June 2012

Overview:

“EMIX 1.0 and the OASIS Smart Grid Suite of Standards” describes how EMIX relates to other OASIS Standards, including WS-Calendar, Energy Interoperation, Emergency Management, SOA Reference Model, and Security standards.

“Using EMIX 1.0 to support Transactive Energy Markets” describes the use of EMIX 1.0 to as an information model for price and product communication for energy transactions in both centralized and decentralized energy markets.

URIs:
The prose specification document and related files are available here:

– EMIX 1.0 and the OASIS Smart Grid Suite of Standards Version 1.0

PDF (Authoritative):
http://docs.oasis-open.org/emix/emix-oasis/v1.0/cn01/emix-oasis-v1.0-cn01.pdf

HTML:
http://docs.oasis-open.org/emix/emix-oasis/v1.0/cn01/emix-oasis-v1.0-cn01.html

Editable source:
http://docs.oasis-open.org/emix/emix-oasis/v1.0/cn01/emix-oasis-v1.0-cn01.doc

– Using EMIX 1.0 to support Transactive Energy Markets Version 1.0

PDF (Authoritative):
http://docs.oasis-open.org/emix/emix-trans/v1.0/cn01/emix-trans-v1.0-cn01.pdf

HTML:
http://docs.oasis-open.org/emix/emix-trans/v1.0/cn01/emix-trans-v1.0-cn01.html

PDF:
http://docs.oasis-open.org/emix/emix-trans/v1.0/cn01/emix-trans-v1.0-cn01.doc

Members of the OASIS Energy Market Information Exchange (eMIX) TC requested Special Majority Votes to approve these Committee Notes. The Committee Note Drafts had been released for public review as required by the TC Process [2]. The vote to approve at Committee Note (CN) level passed [3], and the approved notes are now available online in the OASIS Library as referenced above.

Our congratulations to the TC on achieving this milestone.

========== Additional references:

[1] OASIS Energy Market Information Exchange (eMIX) TC
http://www.oasis-open.org/committees/emix/

[2] Public reviews
30-day public review, 31 October 2011: https://lists.oasis-open.org/archives/tc-announce/201110/msg00015.html

[3] CN ballots
https://www.oasis-open.org/committees/ballot.php?id=2241
https://www.oasis-open.org/committees/ballot.php?id=2240

We are pleased to announce the approval and publication of an OASIS Committee Note (CN) by the members of the OASIS Transformational Government Framework TC [1]:

Transformational Government Framework (TGF) Tools and Models for the Business Management Framework: Volume 1 Using the Policy Product Matrix Version 1.0
Committee Note 01
07 June 2012

Overview:
This Committee Note and the associated Wiki resource contain detailed information and guidance on using the Policy Products matrix in the Business Management Framework, as identified in the TGF Primer and TGF Core Pattern Language. It is the first in an intended series of Committee Notes providing further guidance on the Business Management Framework. Policy Products are the written policies, frameworks and standards which inform government activity.

The TGF Primer contains the following statement:

“A full analysis of the Policy Products which we recommend are typically needed to deliver an effective and holistic transformation program will be included in a separate Committee Note “Tools and Models for the Business Management Framework”. Although the detailed Policy Products in that note are advisory and not all of them may be needed, any conformant transformation program MUST use the overall framework and matrix of the Policy Product Map in order to conduct at minimum a gap analysis aimed at identifying the key Policy Products needed for that government, taking the Committee Note into account as guidance.”

This Committee Note, together with the associated Wiki resource – http://wiki.oasis-open.org/tgf/FrontPage, sets out the range of Policy Products which should be considered in any Transformational Government program. Not all may be necessary for every program, and in some cases a program may wish to meet the objectives of what are shown here as separate Policy Products through a single, broader Policy Product.

URIs:
The prose specification document and related files are available here:

PDF (Authoritative):
http://docs.oasis-open.org/tgf/TGF-BMF-Tools/v1.0/cn01/TGF-BMF-Tools-v1.0-cn01.pdf

HTML:
http://docs.oasis-open.org/tgf/TGF-BMF-Tools/v1.0/cn01/TGF-BMF-Tools-v1.0-cn01.html

Editable source:
http://docs.oasis-open.org/tgf/TGF-BMF-Tools/v1.0/cn01/TGF-BMF-Tools-v1.0-cn01.doc

Distribution ZIP files
For your convenience, OASIS provides a complete package of the prose specification and related files in a ZIP distribution file. You can download the ZIP file here:

http://docs.oasis-open.org/tgf/TGF-BMF-Tools/v1.0/cn01/TGF-BMF-Tools-v1.0-cn01.zip

Members of the OASIS Transformational Government Framework TC requested a Special Majority Vote to approve the Committee Note. The Committee Note Draft had been released for public review as required by the TC Process [2]. The vote to approve at Committee Note (CN) level passed [3], and the approved CN is now available online in the OASIS Library as referenced above.

Our congratulations to the TC on achieving this milestone.

========== Additional references:

[1] OASIS Transformational Government Framework TC
http://www.oasis-open.org/committees/tgf/

[2] Public reviews
30-day public review, 20 April 2012: https://lists.oasis-open.org/archives/tc-announce/201204/msg00007.html

[3] CN ballot
https://www.oasis-open.org/committees/ballot.php?id=2244

A new OASIS technical committee is being formed. The OASIS Web Services Basic Reliable and Secure Profiles (WS-BRSP) Technical Committee has been proposed by the members of OASIS listed in the charter below. The TC name, statement of purpose, scope, list of deliverables, audience, IPR mode and language specified in the proposal will constitute the TC’s official charter. Submissions of technology for consideration by the TC, and the beginning of technical discussions, may occur no sooner than the TC’s first meeting.

The eligibility requirements for becoming a participant in the TC at the first meeting are:

(a) you must be an employee or designee of an OASIS member organization or an individual member of OASIS, and


(b) you must join the Technical Committee, which members may do by using the “Join this TC” button on the TC’s home page at [a].

To be considered a voting member at the first meeting, you must:

(a) join the Technical Committee at least 7 days prior to the first meeting (on or before 30 August 2012); and


(b) you must attend the first meeting of the TC, at the time and date fixed below (06 September 2012).

Participants also may join the TC at a later time. OASIS and the TC welcomes all interested parties.

Non-OASIS members who wish to participate may contact us about joining OASIS [b]. In addition, the public may access the information resources maintained for each TC: a mail list archive, document repository and public comments facility, which will be linked from the TC’s public home page.

Please feel free to forward this announcement to any other appropriate lists. OASIS is an open standards organization. We encourage your participation.
———-

[a] http://www.oasis-open.org/committees/ws-brsp/ 

[b] See http://www.oasis-open.org/join/


———-

CALL FOR PARTICIPATION

(1) Charter of the Technical Committee

(a) Name of the TC

OASIS Web Services Basic Reliable and Secure Profiles (WS-BRSP) Technical Committee

(b) Statement of Purpose

The purpose of this Technical Committee (TC) is to maintain WS-I (Web Services Interoperability) Basic Profiles (1.2 and 2.0), Basic Security Profile (1.0), Reliable Secure Profile (1.0), and ISO/IEC JTC 1 Profile Specifications (ISO/IEC 29361:2008 standard Information technology – Web Services Interoperability – WS-I Basic Profile Version 1.1, ISO/IEC 29362:2008 standard Information technology – Web Services Interoperability – WS-I Attachments Profile Version 1.0, ISO/IEC 29363:2008 document Information technology – Web Services Interoperability – WS-I Simple SOAP Binding Profile Version 1.0).

(c) Scope of Work

Note: A ‘Profile’ consists of a ‘Profile Specification’ and its associated Scenarios and Test Tools.

1. Perform ongoing maintenance of the following existing ISO/IEC JTC 1 Profile Specifications:

* ISO/IEC 29361:2008 standard Information technology – Web Services Interoperability – WS-I Basic Profile Version 1.1
* ISO/IEC 29362:2008 standard Information technology – Web Services Interoperability – WS-I Attachments Profile Version 1.0
* ISO/IEC 29363:2008 document Information technology – Web Services Interoperability – WS-I Simple SOAP Binding Profile Version 1.0

2. Perform maintenance as well as minor modifications that enhance interoperability of Basic Profiles (1.2 and 2.0), Reliable Secure Profile (1.0), and Basic Security Profile (1.1).

3. Progress Basic Profiles (1.2 and 2.0), Reliable Secure Profile (1.0), and Basic Security Profile (1.1) through the OASIS process and prepare them for submission to ISO/IEC JTC 1.

4. Conduct testing and demonstrations of interoperability which, at a minimum, meet the requirements imposed by OASIS policies and rules.

5. Address issues with Basic Profiles (1.2 and 2.0), Reliable Secure Profile (1.0), and Basic Security Profile (1.1) and with the Testing Tools that prevent performing work item (1)(c)4 in a repeatable, automated fashion. NOTE: The existing testing mechanism for the aforementioned ISO/IEC JTC 1 Profiles and Basic Security Profile (1.1) use a testing methodology which may not be amenable to automation.

6. Perform ongoing maintenance of Basic Profiles (1.2 and 2.0), Reliable Secure Profile (1.0), and Basic Security Profile (1.1) within this TC, including after they become ISO/IEC JTC 1 standards.

(d) Deliverables

1. OASIS Basic Profile v1.2 Specification
2. OASIS Basic Profile v2.0 Specification
3. OASIS Reliable Secure Profile v1.0 Specification
4. OASIS Basic Security Profile v1.1 Specification
5. Scenarios for OASIS Basic Profile v1.2
6. Scenarios for OASIS Basic Profile v2.0
7. Scenarios for OASIS Reliable Secure Profile v1.0
8. Scenarios for OASIS Basic Security Profile v1.1
9. Testing tools used in the TC’s work
10. Future versions as part of maintenance and/or other requirements which the TC decides are appropriate

(e) IPR Mode

This TC will operate under Non-Assert IPR mode as defined in the OASIS Intellectual Property Rights (IPR) Policy effective 15 October 2010.

(f) Anticipated Audience

End users and implementers of the WS-I Profiles.

(g) Language

TC business will be conducted in English.

References

1. ISO/IEC 29361:2008 standard Information technology – Web Services Interoperability – WS-I Basic Profile Version 1.1.
2. ISO/IEC 29362:2008 standard Information technology – Web Services Interoperability – WS-I Attachments Profile Version 1.0.
3. ISO/IEC 29363:2008 document Information technology – Web Services Interoperability – WS-I Simple SOAP Binding Profile Version 1.0.
4. WS-I Basic Profile 1.2 Final Material 2010-11-09 http://ws-i.org/Profiles/BasicProfile-1.2-2010-11-09.html.
5. WS-I Basic Profile 2.0 Final Material 2010-11-09 http://ws-i.org/Profiles/BasicProfile-2.0-2010-11-09.html.
6. WS-I Reliable Secure Profile 1.0 Final Material 2010-11-09 http://www.ws-i.org/Profiles/ReliableSecureProfile-1.0-2010-11-09.html.
7. WS-I Basic Security Profile 1.1 Final Material 2010-01-24 http://www.ws-i.org/Profiles/BasicSecurityProfile-1.1.html.

(2) Non-normative information regarding the startup of the TC

(a) Similar Work

There is no similar work being done in OASIS or to our knowledge in any other organizations.

(b) Date, Time, and Location of First Meeting

The First Meeting will be held by teleconference at 11:00 am Pacific Time on Thursday, September 6, 2012 and will be sponsored by Fujitsu Limited.

(c) On-Going Meeting Plans & Sponsors

It is anticipated that the WS-BRSP TC will meet monthly via teleconference and face-to-face (if needed); however at its First Meeting, the TC will elect a Chair and setup an on-going meeting schedule and determine who will sponsor these meetings.

(d) Proposers of the TC

Michael DeNicola, MDeNicola@us.fujitsu.com, Fujitsu Limited

Joel J. Fleck, joel.fleck@hp.com, Hewlett-Packard

Micah Hainline, micah.hainline@asolutions.com, Asynchrony Solutions, Inc.

Ram Jeyaraman, ram.jeyaraman@microsoft.com, Microsoft

Prasad Yendluri, Prasad.Yendluri@Softwareag.com, Software AG

(e) Statement of Support

* Hiroshi Yoshida, jikeitou-std-contact@ml.css.fujitsu.com, Fujitsu Limited – “I, Hiroshi Yoshida (jikeitou-std-contact@ml.css.fujitsu.com), Principal Architect, Cloud Platform Development Unit, Fujitsu Limited support the goals of the proposed OASIS Web Services Basic, Reliable, and Secure Profiles (WS-BRSP) Technical Committee as described in this Charter.”

* Joel Fleck, joel.fleck@hp.com, Hewlett-Packard – “As the Primary Representative for Hewlett-Packard in OASIS, I submit this statement in support of the mission and goals of the proposed Technical Committee ‘OASIS Web Services Basic, Reliable and Secure Profiles (WS-BRSP)’ as described in this Charter.”

* Micah Hainline, micah.hainline@asolutions.com, Asynchrony Solutions, Inc.- “As the primary representative for Asynchrony Solutions, Inc., I state that our organization supports the goals of the proposed OASIS Web Services Basic, Reliable, and Secure Profiles (WS-BRSP) Technical Committee as described in this Charter.”

* Ram Jeyaraman, ram.jeyaraman@microsoft.com, Microsoft – “As the Primary Representative for Microsoft in OASIS, I support the goals of the proposed OASIS Web Services Basic, Reliable, and Secure Profiles (WS-BRSP) Technical Committee as described in this Charter.”

* Prasad Yendluri, Prasad.Yendluri@Softwareag.com, Software AG – “I, Prasad Yendluri (Prasad.Yendluri@Softwareag.com) VP & Deputy CTO, Software AG support the goals of the proposed OASIS Web Services Basic, Reliable, and Secure Profiles (WS-BRSP) Technical Committee as described in this Charter.”

(f) TC Convener

The TC Convener for the Convener Call and first meeting will be Michael DeNicola from Fujitsu.

(g) Affiliation to Member Section

It is intended that this TC will be affiliated with the WS-I Member Section.

(h) List of anticipated contributions

1. WS-I Basic Profile 1.2 Final Material 2010-11-09 http://ws-i.org/Profiles/BasicProfile-1.2-2010-11-09.html, related scenarios, and test tools.

2. WS-I Basic Profile 2.0 Final Material 2010-11-09 http://ws-i.org/Profiles/BasicProfile-2.0-2010-11-09.html, related scenarios, and test tools.

3. WS-I Reliable Secure Profile 1.0 Final Material 2010-11-09 http://www.ws-i.org/Profiles/ReliableSecureProfile-1.0-2010-11-09.html, related scenarios, and test tools.

4. WS-I Basic Security Profile 1.1 Final Material 2010-01-24 http://www.ws-i.org/Profiles/BasicSecurityProfile-1.1.html, related scenarios, and test tools.

(i) Frequently Asked Questions (FAQ) relating to the planned scope of the TC

None

(j) Proposed working title and acronym for the specification(s) to be developed by the TC

1. Proposed title of the Technical Committee: Web Services Basic Reliable and Secure Profiles TC

2. Proposed acronym of the specification: WS-BRSP TC

We are pleased to announce that Biometric Identity Assurance Services (BIAS) SOAP Profile Version 1.0 OASIS Standard has been published and is available in the OASIS Library. The Standard specifies a SOAP profile that implements the BIAS abstract operations specified in INCITS 442 as SOAP messages.

Biometric Identity Assurance Services (BIAS) SOAP Profile Version 1.0
OASIS Standard
24 May 2012

The prose specification document and related files are available here:

Editable Source:
http://docs.oasis-open.org/bias/soap-profile/v1.0/os/biasprofile-v1.0-os.doc

HTML:
http://docs.oasis-open.org/bias/soap-profile/v1.0/os/biasprofile-v1.0-os.html

PDF:
http://docs.oasis-open.org/bias/soap-profile/v1.0/os/biasprofile-v1.0-os.pdf

XML schema:
http://docs.oasis-open.org/bias/soap-profile/v1.0/os/cbeff.xsd

WSDL:
http://docs.oasis-open.org/bias/soap-profile/v1.0/os/BIAS.wsdl

For more information on BIAS SOAP Profile V1.0 and the TC generally, see the TCs web page at http://www.oasis-open.org/committees/bias/.

The Web Services Security Version 1.1.1 OASIS Standard has now been published. The prose specification documents and related files are available here:

– Web Services Security Kerberos Token Profile Version 1.1.1
Editable Source: (Authoritative)
http://docs.oasis-open.org/wss-m/wss/v1.1.1/os/wss-KerberosTokenProfile-v1.1.1-os.doc

HTML:
http://docs.oasis-open.org/wss-m/wss/v1.1.1/os/wss-KerberosTokenProfile-v1.1.1-os.html

PDF:
http://docs.oasis-open.org/wss-m/wss/v1.1.1/os/wss-KerberosTokenProfile-v1.1.1-os.pdf

—
– Web Services Security SAML Token Profile Version 1.1.1
Editable Source: (Authoritative)
http://docs.oasis-open.org/wss-m/wss/v1.1.1/os/wss-SAMLTokenProfile-v1.1.1-os.doc

HTML:
http://docs.oasis-open.org/wss-m/wss/v1.1.1/os/wss-SAMLTokenProfile-v1.1.1-os.html

PDF:
http://docs.oasis-open.org/wss-m/wss/v1.1.1/os/wss-SAMLTokenProfile-v1.1.1-os.pdf

—
– Web Services Security: SOAP Message Security Version 1.1.1
Editable Source: (Authoritative)
http://docs.oasis-open.org/wss-m/wss/v1.1.1/os/wss-SOAPMessageSecurity-v1.1.1-os.doc

HTML:
http://docs.oasis-open.org/wss-m/wss/v1.1.1/os/wss-SOAPMessageSecurity-v1.1.1-os.html

PDF:
http://docs.oasis-open.org/wss-m/wss/v1.1.1/os/wss-SOAPMessageSecurity-v1.1.1-os.pdf

—
– Web Services Security SOAP Message with Attachments (SwA) Profile Version 1.1.1
Editable Source: (Authoritative)
http://docs.oasis-open.org/wss-m/wss/v1.1.1/os/wss-SwAProfile-v1.1.1-os.doc

HTML:
http://docs.oasis-open.org/wss-m/wss/v1.1.1/os/wss-SwAProfile-v1.1.1-os.html

PDF:
http://docs.oasis-open.org/wss-m/wss/v1.1.1/os/wss-SwAProfile-v1.1.1-os.pdf

—
– Web Services Security Username Token Profile Version 1.1.1
Editable Source: (Authoritative)
http://docs.oasis-open.org/wss-m/wss/v1.1.1/os/wss-UsernameTokenProfile-v1.1.1-os.doc

HTML:
http://docs.oasis-open.org/wss-m/wss/v1.1.1/os/wss-UsernameTokenProfile-v1.1.1-os.html

PDF:
http://docs.oasis-open.org/wss-m/wss/v1.1.1/os/wss-UsernameTokenProfile-v1.1.1-os.pdf

—
– Web Services Security Rights Expression Language (REL) Token Profile Version 1.1.1
Editable Source: (Authoritative)
http://docs.oasis-open.org/wss-m/wss/v1.1.1/os/wss-rel-token-profile-v1.1.1-os.doc

HTML:
http://docs.oasis-open.org/wss-m/wss/v1.1.1/os/wss-rel-token-profile-v1.1.1-os.html

PDF:
http://docs.oasis-open.org/wss-m/wss/v1.1.1/os/wss-rel-token-profile-v1.1.1-os.pdf

—
– Web Services Security X.509 Certificate Token Profile Version 1.1.1
Editable Source: (Authoritative)
http://docs.oasis-open.org/wss-m/wss/v1.1.1/os/wss-x509TokenProfile-v1.1.1-os.doc

HTML:
http://docs.oasis-open.org/wss-m/wss/v1.1.1/os/wss-x509TokenProfile-v1.1.1-os.html

PDF:
http://docs.oasis-open.org/wss-m/wss/v1.1.1/os/wss-x509TokenProfile-v1.1.1-os.pdf

—
XML Schemas: http://docs.oasis-open.org/wss-m/wss/v1.1.1/os/xsd/

Distribution ZIP files:
For your convenience, OASIS provides a complete package of the prose specification and related files in a ZIP distribution file. You can download the ZIP file here:

http://docs.oasis-open.org/wss-m/wss/v1.1.1/os/wss-v1.1.1-os.zip

Specification Summary

WSS-M v1.1.1 integrates specific error corrections or editorial changes to the preceding Web Services Security specifications. It is a multi-part specification consisting of:

– Web Services Security Kerberos Token Profile
– Web Services Security Rights Expression Language (REL) Token Profile
– Web Services Security SAML Token Profile
– Web Services Security: SOAP Message Security Version
– Web Services Security SOAP Message with Attachments (SwA) Profile
– Web Services Security Username Token Profile
– Web Services Security X.509 Certificate Token Profile Version

For more information on OASIS Web Services Security Version 1.1.1 and the TC generally, see the TCs web page at http://www.oasis-open.org/committees/wss-m/.