The OASIS Key Management Interoperability Protocol (KMIP) TC [1] members have recently approved two Committee Specification Drafts (CSD) and two Committee Note Drafts (CND) and submitted these drafts for 15-day public review:

Key Management Interoperability Protocol Specification Version 1.1
Committee Specification Draft 02 / Public Review Draft 02
14 May 2012

Key Management Interoperability Protocol Profiles Version 1.1
Committee Specification Draft 02 / Public Review Draft 02
14 May 2012

Key Management Interoperability Protocol Usage Guide Version 1.1
Committee Note Draft 02 / Public Review Draft 02
14 May 2012

Key Management Interoperability Protocol Test Cases Version 1.1
Committee Note Draft 02 / Public Review Draft 02
14 May 2012

Specification Overview:

The KMIP Specification V1.1 CSPRD02 is the normative description of objects, operations and attributes for this version of the OASIS Key Management Interoperability Protocol.

The KMIP Profile V1.1 CSPRD02 is the normative description of conformance profiles for this version of the OASIS Key Management Interoperability Protocol.

The KMIP Usage Guide V1.1 CSD.02 provides illustrative information regarding the implementation of solutions using the objects, operations and attributes for this version of the OASIS Key Management Interoperability Protocol.

The KMIP Test Cases V1.1 CSD.02 is the illustrative description of test cases for objects, operations and attributes for this version of the OASIS Key Management Interoperability Protocol.

TC Description:

The OASIS KMIP TC works to define a single, comprehensive protocol for communication between encryption systems and a broad range of new and legacy enterprise applications, including email, databases, and storage devices. By removing redundant, incompatible key management processes, KMIP will provide better data security while at the same time reducing expenditures on multiple products.

Public Review Period:

The public review starts 4 June 2012 and ends 19 June 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 complete packages of the prose specification and note documents and related
files are available in the ZIP distribution file at:

Key Management Interoperability Protocol Specification Version 1.1
http://www.oasis-open.org/committees/download.php/46154/kmip-spec-v1.1-csprd02.zip

Key Management Interoperability Protocol Profiles Version 1.1
http://www.oasis-open.org/committees/download.php/46155/kmip-profiles-v1.1-csprd02.zip

Key Management Interoperability Protocol Usage Guide Version 1.1
http://www.oasis-open.org/committees/download.php/46157/kmip-ug-v1.1-cnprd02.zip

Key Management Interoperability Protocol Test Cases Version 1.1
http://www.oasis-open.org/committees/download.php/46156/kmip-testcases-v1.1-cnprd02.zip

The resolution log for comments received in the prior public review announced 22 January 2012 is available at:
http://www.oasis-open.org/committees/download.php/46158/KMIP-TC-Public-Review-Comments-22mar2012-.xls

Additional information about the specification and the OASIS Key Management Interoperability Protocol (KMIP) TC may be found at the TC’s public home page:

https://www.oasis-open.org/committees/kmip/

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

https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=kmip

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

http://lists.oasis-open.org/archives/kmip-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 KMIP V1.1 Committee Specification and Note drafts, we call your attention to the OASIS IPR Policy [2] applicable especially [3] 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 Key Management Interoperability Protocol (KMIP) TC
https://www.oasis-open.org/committees/kmip/

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

[3] http://www.oasis-open.org/committees/kmip/ipr.php
RF on RAND Mode
https://www.oasis-open.org/policies-guidelines/ipr#s10.2.2

The OASIS eXtensible Access Control Markup Language (XACML) TC members [1] have produced an updated Committee Specification Draft (CSD) and submitted this specification for 15-day public review:

eXtensible Access Control Markup Language (XACML) Version 3.0
Committee Specification Draft 06 / Public Review Draft 04
19 April 2012

Specification Overview:
This specification defines version 3.0 of the extensible access control markup language.

TC Description:
The XACML Technical Committee defines a core XML schema for representing authorization and entitlement policies.

Public Review Period:
The public review starts 31 May 2012 and ends 14 June 2012. The specification was previously submitted for public review [2]. This 15-day review is limited in scope to changes made from the previous review.

Changes are highlighted in the diff-marked PDF file [3].

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/xacml-3.0-core-spec-csprd04-en.doc

HTML:
http://docs.oasis-open.org/xacml/3.0/xacml-3.0-core-spec-csprd04-en.html

PDF:
http://docs.oasis-open.org/xacml/3.0/xacml-3.0-core-spec-csprd04-en.pdf

XML Schema:
http://docs.oasis-open.org/xacml/3.0/xacml-core-v3-schema-wd-17.xsd

ZIP distribution files (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/xacml-3.0-core-spec-csprd04-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 eXtensible Access Control Markup Language (XACML) Version 3.0, we call your attention to the OASIS IPR Policy [4] applicable especially [5] 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] Public Reviews:
15-day public review, 6 October 2011: http://lists.oasis-open.org/archives/tc-announce/201110/msg00006.html
30-day public review: http://lists.oasis-open.org/archives/tc-announce/201005/msg00003.html
60-day public review: http://lists.oasis-open.org/archives/tc-announce/200905/msg00006.html

[3] DIFF file and list of changes:
Red-lined DIFF file: http://docs.oasis-open.org/xacml/3.0/xacml-3.0-core-spec-csprd04-diff.pdf

List of changes for CSD06 / CSPRD04: http://lists.oasis-open.org/archives/xacml/201204/msg00017.html

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

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

The OASIS Field Force Management (FFM) TC [1] members have recently approved a Committee Specification Draft (CSD) and submitted this specification for 30-day public review:

Field Force Management Integration Interface Specification Version 1.0
Committee Specification Draft 01 / Public Review Draft 01
23 May 2012

Specification Overview:

This document describes the Field Force Management Integration Interface (FFMII). FFMII provides a flexible interface between Enterprise Resource Management System (ERMS) and Field Force Management System (FFMS).

The role of ERMS is to take a holistic view at work scheduling and resource allocation from the corporate point of view. For this purpose it needs to manage individual units of work performed without strong supervisory guidance (Field Work) in a way aligned with the business objectives of the company.

The role of FFMS is to communicate with available set of workers (Field Force) and to provide individual workers (Assignees) performing Field Work with technical means of accessing information about and sending feedback on work assigned to them. While ERMS defines the structure, content and resource allocation of dispatched work, FFMS is responsible for communicating that information to the field and enforcing any specified constraints on user provided feedback.

For facilitating structured communication between ERMS and FFMS in heterogeneous scenarios, FFMII defines flexible mechanisms that enable Work Request modeling (data content, workflow), exchange, work history collection, and collection of data from the field. Information carried with work requests, work request structure (work-flow, schedule) and data to be collected can all be defined dynamically ‘as data’. This data driven architecture makes FFMII very flexible and adaptable to numerous industries.

Additional FFMII capabilities include Field-Initiated Requests that facilitate structured requests and reporting information outside the usual work flow, such as reporting absence, requesting additional work, or providing a sales lead. Reference Data Management provides means to establish custom data repositories with arbitrary content. This enables e.g. input value selection, content validation, or delivery of documents to Field Force. Furthermore, flexible Integration Topologies are supported. Further flexibility is provided by scalability of FFMII itself: Basic features of FFMII are mandatory, and some features are optional. This allows both simple basic implementations and a range of more complete implementations.

Public Review Period:

The public review starts 29 May 2012 and ends 28 June 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 complete package of the prose specification document and related files are available in the ZIP distribution file at:

http://www.oasis-open.org/committees/download.php/46130/FFMII-SPEC-v1.0-csprd01.zip

Additional information about the specification and the Field Force Management (FFM) TC may be found at the TC’s public home page:

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

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

http://www.oasis-open.org/committees/comments/index.php?wg_abbrev=ffm

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

http://lists.oasis-open.org/archives/ffm-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 Field Force Management Integration Interface Specification Version 1.0, we call your attention to the OASIS IPR Policy [2] applicable especially [3] 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 Field Force Management (FFM) TC
http://www.oasis-open.org/committees/ffm/

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

[3] http://www.oasis-open.org/committees/ffm/ipr.php
http://www.oasis-open.org/policies-guidelines/ipr#s10.2.3
RF on Limited Mode

OASIS members:

We are pleased to announce that Biometric Identity Assurance Services (BIAS) SOAP Profile Version 1.0 has been approved by the membership as an OASIS Standard [1].

The call to vote was announced on 9 May 2012 [2] and closed 24 May 2012. A minimum of 49 affirmative votes were needed in order to win approval. The finally vote tally was 50 affirmative votes and 0 opposed.

BIAS SOAP Profile Version 1.0 specifies how to use the XML defined in ANSI INCITS 442-2010 – Biometric Identity Assurance Services [INCITS-BIAS] to invoke Simple Object Access Protocol (SOAP)-based services that implement BIAS operations. These SOAP-based services enable an application to invoke biometric identity assurance operations remotely in a Services Oriented Architecture (SOA) infrastructure.

The BIAS SOAP Profile specifies XML-encoded SOAP messages to exchange biometric data and perform biometric-based identity operations. BIAS is intended to provide a common, yet flexible, Web Services interface that can be used within both closed and open SOA systems.

The BIAS SOAP Profile is a companion document to ANSI INCITS 442-2010 – Biometric Identity Assurance Services. The INCITS document defines the general architecture, requirements, operations, and data elements. The OASIS document specifies the SOAP binding/implementation of these operations.

The specification was approved as a Candidate OASIS Standard on 02 February 2012. Statements of use were received from National Institute of Standards and Technology (NIST), Viometric LLC and the Department of Defense (DoD) Biometric Identity Management Agency (BIMA).

More information can be found on the TCs web page at http://www.oasis-open.org/committees/bias/.

TC Administration will now prepare and publish the final OASIS Standard and notify members when it is available.

Our congratulations to the members of the TC and to the community of implementers, developers and users who have brought the work successfully to this milestone.

=== Additional information

[1] http://www.oasis-open.org/committees/ballot.php?id=2225

[2] http://lists.oasis-open.org/archives/tc-announce/201205/msg00002.html

[3] The Candidate OASIS Standard can be found at http://docs.oasis-open.org/bias/soap-profile/v1.0/cos01/biasprofile-v1.0-cos01.html

We are pleased to announce the approval and publication of an OASIS Approved Errata by the members of the Security Services (SAML) TC [1]:

SAML Version 2.0 Errata 05
OASIS Approved Errata
01 May 2012

URIs:
The prose errata documents are available here:

Editable Source (Authoritative):
http://docs.oasis-open.org/security/saml/v2.0/errata05/os/saml-v2.0-errata05-os.odt

HTML:
http://docs.oasis-open.org/security/saml/v2.0/errata05/os/saml-v2.0-errata05-os.html

PDF:
http://docs.oasis-open.org/security/saml/v2.0/errata05/os/saml-v2.0-errata05-os.pdf

Our congratulations to the TC on this milestone.

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

[1] Security Services (SAML) TC
http://www.oasis-open.org/committees/security/

We are pleased to announce the approval and publication of an OASIS Committee Specification (CS) by the members of the Security Services (SAML) TC [1]:

SAML V2.0 Metadata Extensions for Registration and Publication Information Version 1.0
Committee Specification 01
03 April 2012

Overview:
The Metadata Extensions for Registration and Publication Information define a set of extensions to SAML metadata that provide information about the creation and intended usage of the metadata document and information about who and how particular entities were registered.

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

Editable Source (Authoritative):
http://docs.oasis-open.org/security/saml/Post2.0/saml-metadata-rpi/v1.0/cs01/saml-metadata-rpi-v1.0-cs01.odt

HTML:
http://docs.oasis-open.org/security/saml/Post2.0/saml-metadata-rpi/v1.0/cs01/saml-metadata-rpi-v1.0-cs01.html

PDF:
http://docs.oasis-open.org/security/saml/Post2.0/saml-metadata-rpi/v1.0/cs01/saml-metadata-rpi-v1.0-cs01.pdf

XML schema:
http://docs.oasis-open.org/security/saml/Post2.0/saml-metadata-rpi/v1.0/cs01/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/security/saml/Post2.0/saml-metadata-rpi/v1.0/cs01/saml-metadata-rpi-v1.0-cs01.zip

Members of the Security Services (SAML) TC requested a Special Majority Vote to approve this specification as a Committee Specification. The specification had been released for public review as required by the TC Process [2]. The vote to approve at Committee Specification (CS) level passed [3], and the approved CS01 is now available online in the
OASIS Library as referenced above.

Our congratulations to the TC on achieving this milestone.

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

[1] Security Services (SAML) TC
http://www.oasis-open.org/committees/security/

[2] Public reviews
15-day public review, 15 February 2012: http://lists.oasis-open.org/archives/tc-announce/201202/msg00003.html
30-day public review, 5 October 2011: https://www.oasis-open.org/apps/org/workgroup/security/email/archives/201110/msg00005.html

[3] CS ballot
http://www.oasis-open.org/committees/ballot.php?id=2202

We are pleased to announce the approval and publication of an OASIS Committee Specification (CS) by the members of the OASIS ebXML Messaging Services TC [1]:

AS4 Profile of ebMS 3.0 Version 1.0
Committee Specification 03
30 April 2012

Overview:
While ebMS 3.0 represents a leap forward in reducing the complexity of Web Services B2B messaging, the specification still contains numerous options and comprehensive alternatives for addressing a variety of scenarios for exchanging data over a Web Services platform. The AS4 profile of the ebMS 3.0 specification has been developed in order to bring continuity to the principles and simplicity that made AS2 successful, while adding better compliance to Web Services standards, and features such as message pulling capability and a built-in Receipt mechanism. Using ebMS 3.0 as a base, a subset of functionality is defined along with implementation guidelines adopted based on the “just-enough” design principles and AS2 functional requirements to trim down ebMS 3.0 into a more simplified and AS2-like specification for Web Services B2B messaging. In addition to addressing EDIINT requirements, a Minimal Client conformance profile is provided that addresses lower-end exchange requirements. This document defines the AS4 profile as a combination of conformance profiles that concern an implementation capability, and of a usage profile that concerns how to use this implementation. A couple of variants are defined for the AS4 conformance profile – the AS4 ebHandler profile, the AS4 Light Client profile and the AS4 Minimal Client profile – which reflect different endpoint capabilities.

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

Editable Source (Authoritative):
http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/profiles/AS4-profile/v1.0/cs03/AS4-profile-v1.0-cs03.odt

HTML:
http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/profiles/AS4-profile/v1.0/cs03/AS4-profile-v1.0-cs03.html

PDF:
http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/profiles/AS4-profile/v1.0/cs03/AS4-profile-v1.0-cs03.pdf

XML examples:
http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/profiles/AS4-profile/v1.0/cs03/examples/

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/ebxml-msg/ebms/v3.0/profiles/AS4-profile/v1.0/cs03/AS4-profile-v1.0-cs03.zip

Members of the OASIS ebXML Messaging Services TC requested a Special Majority Vote to approve this specification as a Committee Specification. The specification
had been released for public review as required by the TC Process [2]. The vote to approve at Committee Specification (CS) level passed [3], and the approved CS03 is now available online in the OASIS Library as referenced above.

Our congratulations to the TC on achieving this milestone.

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

[1] OASIS ebXML Messaging Services TC
http://www.oasis-open.org/committees/ebxml-msg/

[2] Public reviews
15-day public review, 29 March 2012: http://lists.oasis-open.org/archives/tc-announce/201203/msg00014.html
15-day public review, 12 July 2012: http://lists.oasis-open.org/archives/tc-announce/201107/msg00004.html
15-day public review, 23 October 2009: http://lists.oasis-open.org/archives/tc-announce/200910/msg00014.html
60-day public review, 25 April 2009: http://lists.oasis-open.org/archives/tc-announce/200904/msg00013.html

[3] CS ballot
http://www.oasis-open.org/apps/org/workgroup/ebxml-msg/ballot.php?id=2213

We are pleased to announce that Web Services Security Version 1.1.1 has been approved by the membership as an OASIS Standard [1].

The call to vote was announced on 3 May 2012 [2] and closed 18 May 2012. A minimum of 48 affirmative votes were needed in order to win approval. The finally vote tally was 68.

WSS-M v1.1.1 [3] 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

Statements of Use were received from Tibco Software Inc, Oracle Corporation and IBM Corporation. More information can be found on the TCs web page at http://www.oasis-open.org/committees/wss-m/.

TC Administration will now prepare and publish the final OASIS Standard and notify members when it is available.

Our congratulations to the members of the TC and to the community of implementers, developers and users who have brought the work successfully to this milestone

=== Additional information

[1] http://www.oasis-open.org/committees/ballot.php?id=2221

[2] http://lists.oasis-open.org/archives/members/201205/msg00001.html

[3] The HTML versions of the Candidate OASIS Standard can be found at:

Web Services Security Kerberos Token Profile Version 1.1.1
http://docs.oasis-open.org/wss-m/wss/v1.1.1/cos01/wss-KerberosTokenProfile-v1.1.1-cos01.html
—
Web Services Security SAML Token Profile Version 1.1.1
http://docs.oasis-open.org/wss-m/wss/v1.1.1/cos01/wss-SAMLTokenProfile-v1.1.1-cos01.html
—
Web Services Security: SOAP Message Security Version 1.1.1
http://docs.oasis-open.org/wss-m/wss/v1.1.1/cos01/wss-SOAPMessageSecurity-v1.1.1-cos01.html
—
Web Services Security SOAP Message with Attachments (SwA) Profile Version 1.1.1
http://docs.oasis-open.org/wss-m/wss/v1.1.1/cos01/wss-SwAProfile-v1.1.1-cos01.html
—
Web Services Security Username Token Profile Version 1.1.1
http://docs.oasis-open.org/wss-m/wss/v1.1.1/cos01/wss-UsernameTokenProfile-v1.1.1-cos01.html
—
Web Services Security Rights Expression Language (REL) Token Profile Version 1.1.1
http://docs.oasis-open.org/wss-m/wss/v1.1.1/cos01/wss-rel-token-profile-v1.1.1-cos01.html
—
Web Services Security X.509 Certificate Token Profile Version 1.1.1
http://docs.oasis-open.org/wss-m/wss/v1.1.1/cos01/wss-x509TokenProfile-v1.1.1-cos01.html
—
XML Schemas: http://docs.oasis-open.org/wss-m/wss/v1.1.1/cos01/xsd/

We are pleased to announce the approval and publication of an OASIS Committee Specification (CS) by the members of the OASIS Search Web Services TC [1]:

searchRetrieve Version 1.0
Committee Specification 01
13 April 2012

Overview:

The OASIS Search Web Services (SWS) initiative defines a generic protocol for the interaction required between a client and server for performing searches. SWS defines an Abstract Protocol Definition (APD searchRetrieve Part 1) to describe this interaction. All search protocols can be regarded as concrete implementations of this definition. The Abstract Protocol Definition facilitates interoperability between different search protocols by providing a common framework and terminology for describing search protocols.

The specification is a multi-part work product with the following components:

– Part 0. Overview.
– Part 1. Abstract Protocol Definition.
– Part 2. APD Binding for SRU 1.2.
– Part 3. APD Binding for SRU 2.0.
– Part 4. APD Binding for OpenSearch.
– Part 5. CQL: The Contextual Query Language.
– Part 6. SRU Scan Operation.
– Part 7. SRU Explain Operation.
– XML schemas

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

– Part 0. Overview.
Editable source (Authoritative):
http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/cs01/part0-overview/searchRetrieve-v1.0-cs01-part0-overview.doc

HTML:
http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/cs01/part0-overview/searchRetrieve-v1.0-cs01-part0-overview.html

PDF:
http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/cs01/part0-overview/searchRetrieve-v1.0-cs01-part0-overview.pdf

– Part 1. Abstract Protocol Definition.
Editable source (Authoritative):
http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/cs01/part1-apd/searchRetrieve-v1.0-cs01-part1-apd.doc

HTML:
http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/cs01/part1-apd/searchRetrieve-v1.0-cs01-part1-apd.html

PDF:
http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/cs01/part1-apd/searchRetrieve-v1.0-cs01-part1-apd.pdf

– Part 2. APD Binding for SRU 1.2.
Editable source (Authoritative):
http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/cs01/part2-sru1.2/searchRetrieve-v1.0-cs01-part2-sru1.2.doc

HTML:
http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/cs01/part2-sru1.2/searchRetrieve-v1.0-cs01-part2-sru1.2.html

PDF:
http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/cs01/part2-sru1.2/searchRetrieve-v1.0-cs01-part2-sru1.2.pdf

– Part 3. APD Binding for SRU 2.0.
Editable source (Authoritative):
http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/cs01/part3-sru2.0/searchRetrieve-v1.0-cs01-part3-sru2.0.doc

HTML:
http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/cs01/part3-sru2.0/searchRetrieve-v1.0-cs01-part3-sru2.0.html

PDF:
http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/cs01/part3-sru2.0/searchRetrieve-v1.0-cs01-part3-sru2.0.pdf

– Part 4. APD Binding for OpenSearch.
Editable source (Authoritative):
http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/cs01/part4-opensearch/searchRetrieve-v1.0-cs01-part4-opensearch.doc

HTML:
http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/cs01/part4-opensearch/searchRetrieve-v1.0-cs01-part4-opensearch.html

PDF:
http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/cs01/part4-opensearch/searchRetrieve-v1.0-cs01-part4-opensearch.pdf

– Part 5. CQL: The Contextual Query Language.
Editable source (Authoritative):
http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/cs01/part5-cql/searchRetrieve-v1.0-cs01-part5-cql.doc

HTML:
http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/cs01/part5-cql/searchRetrieve-v1.0-cs01-part5-cql.html

PDF:
http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/cs01/part5-cql/searchRetrieve-v1.0-cs01-part5-cql.pdf

– Part 6. SRU Scan Operation.
Editable source (Authoritative):
http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/cs01/part6-scan/searchRetrieve-v1.0-cs01-part6-scan.doc

HTML:
http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/cs01/part6-scan/searchRetrieve-v1.0-cs01-part6-scan.html

PDF:
http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/cs01/part6-scan/searchRetrieve-v1.0-cs01-part6-scan.pdf

– Part 7. SRU Explain Operation.
Editable source (Authoritative):
http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/cs01/part7-explain/searchRetrieve-v1.0-cs01-part7-explain.doc

HTML:
http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/cs01/part7-explain/searchRetrieve-v1.0-cs01-part7-explain.html

PDF:
http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/cs01/part7-explain/searchRetrieve-v1.0-cs01-part7-explain.pdf

– XML schemas
http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/cs01/schemas/

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/search-ws/searchRetrieve/v1.0/cs01/searchRetrieve-v1.0-cs01.zip

Members of the OASIS Search Web Services TC requested a Special Majority Vote to approve this specification as a Committee Specification. The specification had been released for public review as required by the TC Process [2]. The vote to approve at Committee Specification (CS) level passed [3], and the approved CS01 is now available online in the OASIS Library as referenced above.

Our congratulations to the TC on achieving this milestone.

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

[1] OASIS Search Web Services TC
http://www.oasis-open.org/committees/search-ws

[2] Public reviews
30-day public review, 12 January 2012: http://lists.oasis-open.org/archives/tc-announce/201201/msg00003.html

[3] CS ballot
http://www.oasis-open.org/committees/ballot.php?id=2204

We are pleased to announce the approval and publication of an OASIS Committee Specification (CS) by the members of the OASIS Emergency Management TC [1]:

Emergency Data Exchange Language (EDXL) Common Alerting Protocol (CAP) v1.2 Australia (AU) Profile Version 1.0
Committee Specification 01
26 April 2012

Overview:

This Profile of the XML-based Common Alerting Protocol (CAP) describes an interpretation of the OASIS CAP v1.2 standard necessary to meet the needs of the Australian Government.

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

Editable Source (Authoritative):
http://docs.oasis-open.org/emergency/edxl-cap1.2-au/v1.0/cs01/edxl-cap1.2-au-v1.0-cs01.doc

HTML:
http://docs.oasis-open.org/emergency/edxl-cap1.2-au/v1.0/cs01/edxl-cap1.2-au-v1.0-cs01.html

PDF:
http://docs.oasis-open.org/emergency/edxl-cap1.2-au/v1.0/cs01/edxl-cap1.2-au-v1.0-cs01.pdf

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/emergency/edxl-cap1.2-au/v1.0/cs01/edxl-cap1.2-au-v1.0-cs01.zip

Members of the OASIS Emergency Management TC requested a Special Majority Vote to approve this specification as a Committee Specification. The specification had been released for public review as required by the TC Process [2]. The vote to approve at Committee Specification (CS) level passed [3], and the approved CS01 is now available online in the OASIS Library as referenced above.

Our congratulations to the TC on achieving this milestone.

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

[1] OASIS Emergency Management TC
http://www.oasis-open.org/committees/emergency/

[2] Public reviews
15-day public review, 19 March 2012: http://lists.oasis-open.org/archives/tc-announce/201203/msg00006.html
15-day public review, 5 March 2012: http://lists.oasis-open.org/archives/tc-announce/201203/msg00000.html
30-day public review, 13 December 2011: http://lists.oasis-open.org/archives/tc-announce/201112/msg00005.html

[3] CS ballot
http://www.oasis-open.org/apps/org/workgroup/emergency/ballot.php?id=2209