Members of the Web Services Quality Model TC [1] have recently approved a Special Majority Ballot [2] to advance Web Services Quality Factors V1.0 as a Candidate OASIS Standard (COS). The COS now enters a 60-day public review period in preparation for a member ballot to consider its approval as an OASIS Standard.

Web Services Quality Factors Version 1.0
Candidate OASIS Standard 01
31 October 2012

Specification Overview:

The purpose of this candidate standard is to provide a standard for quality factors of web services in their development, usage and management.

Web services usually have distinguished characteristics. They are service-oriented, network-based, variously bind-able, loosely-coupled, platform independent, and standard-protocol based. As a result, a web service system requires its own quality factors unlike installation-based software. For instance, as the quality of web services can be altered in real-time according to changes by the service provider, considering real-time properties of web services is very meaningful in describing the web services quality.

This document presents the quality factors of web services with definition, classification, and sub-factors case by case. For each quality factor, related specifications are cited with a brief explanation. This specification can be generally extended to the definition of quality of SOA and to provide the foundation for quality in the SOA system.

Public Review Period:

The 60-day public review starts 06 December 2012 and ends 04 February 2013.

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/wsqm/WS-Quality-Factors/v1.0/cos01/WS-Quality-Factors-v1.0-cos01.doc

HTML:
http://docs.oasis-open.org/wsqm/WS-Quality-Factors/v1.0/cos01/WS-Quality-Factors-v1.0-cos01.html

PDF:
http://docs.oasis-open.org/wsqm/WS-Quality-Factors/v1.0/cos01/WS-Quality-Factors-v1.0-cos01.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/wsqm/WS-Quality-Factors/v1.0/cos01/WS-Quality-Factors-v1.0-cos01.zip

Additional information about the specification and the Web Services Quality Model TC may be found at the TC’s public home page:

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

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 page, or directly at:

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

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/wsqm-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 Web Services Quality Factors Version 1.0, we call your attention to the OASIS IPR Policy [3] applicable especially [4] 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.

==============
[1] OASIS Web Services Quality Model TC
http://www.oasis-open.org/committees/wsqm/

[2] Candidate OASIS Standard ballot
https://www.oasis-open.org/committees/ballot.php?id=2308

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

[4] http://www.oasis-open.org/committees/wsqm/ipr.php
RF on Limited Terms Mode
https://www.oasis-open.org/policies-guidelines/ipr#s10.2.2

The Symptoms Automation Framework (SAF) TC members [1] have produced an updated Committee Specification Draft (CSD) and submitted this specification for 15-day public review:

Symptoms Automation Framework (SAF) Version 1.0
Committee Specification Draft 03 / Public Review Draft 02
29 October 2012

Specification Overview:

This document normatively defines a reference architecture for the Symptoms Automation Framework, a tool in the automatic detection, optimization, and remediation of operational aspects of complex systems, notably data centers.

It also provides a non-normative XML data model, based on a pseudo schema and an XSD.

TC Description:

SAF is a catalog-based XML collaborative knowledge framework that is designed to automate appropriate responses to changing business conditions and integrate contributions from diverse domains. SAF has applicability in IT and business including cloud computing, service management, governance, security, energy, eGov, financial, emergency management, healthcare, and communications.

Cloud computing, in particular, exacerbates the separation between consumer-based business requirements and provider-supplied IT responses. SAF facilitates knowledge sharing across these domains, allowing consumer and provider to work cooperatively together to ensure adequate capacity, maximize quality of service, and reduce cost.

The SAF technical committee considers cloud computing to be an area where the value of existing and developing standards could be significantly enhanced using SAF, and as such it has been working on a Cloud primer document alongside the core specification.

Public Review Period:

The public review starts 06 December 2012 and ends 21 December 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.

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/saf/saf/v1.0/csprd02/saf-v1.0-csprd02.doc

HTML:
http://docs.oasis-open.org/saf/saf/v1.0/csprd02/saf-v1.0-csprd02.html

PDF:
http://docs.oasis-open.org/saf/saf/v1.0/csprd02/saf-v1.0-csprd02.pdf

XML Schemas:
http://docs.oasis-open.org/saf/saf/v1.0/csprd02/schemas/

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/saf/saf/v1.0/csprd02/saf-v1.0-csprd02.zip

Additional information about the specification and the OASIS Symptoms Automation Framework (SAF) TC may be found at the TC’s public home page located at:

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

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=saf

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/saf-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 Symptoms Automation Framework (SAF) Version 1.0, we call your attention to the OASIS IPR Policy [3] applicable especially [4] 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] Symptoms Automation Framework (SAF) TC
http://www.oasis-open.org/committees/saf/

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

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

[4] http://www.oasis-open.org/committees/saf/ipr.php
RF on Limited Terms
https://www.oasis-open.org/policies-guidelines/ipr#s10.2.2

The OASIS Integrated Collaboration Object Model for Interoperable Collaboration Services (ICOM) TC members [1] have produced an updated Committee Specification Draft (CSD) and submitted this specification for 15-day public review:

Integrated Collaboration Object Model (ICOM) for Interoperable Collaboration Services Version 1.0
Committee Specification Draft 05 / Public Review Draft 05
27 October 2012

Specification Overview:

The Integrated Collaboration Object Model (ICOM) for Interoperable Collaboration Services defines a framework for integrating a broad range of domain models for collaboration activities in an integrated and interoperable collaboration environment.

The framework is not intended to prescribe how applications or services conforming to its model implement, store, or transport the data for objects. It is intended as a basis for integrating a broad range of collaboration objects to enable seamless transitions across collaboration activities. This enables applications to maintain a complete thread of conversations across multiple collaboration activities.

The model integrates a broad range of collaboration activities, by encompassing and improving on a range of models which are part of existing standards and technologies. The model is modular to allow extensibility. The core concepts, metadata concepts, and their relations are included in the Core, while the specific concepts and relations for each area of collaboration activities are defined in separate extension modules.

The framework lowers the barrier for independent software vendors and open source communities to integrate collaboration services and to create collaboration tools that offer seamless user experience for diverse collaboration activities with minimal context switching.

TC Description:

The OASIS ICOM TC works to define a standard for integrated and interoperable enterprise collaboration.

Public Review Period:

The public review starts 03 December 2012 and ends 18 December 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.

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/icom/icom-ics/v1.0/csprd05/icom-ics-v1.0-csprd05.doc

HTML:
http://docs.oasis-open.org/icom/icom-ics/v1.0/csprd05/icom-ics-v1.0-csprd05.html

PDF:
http://docs.oasis-open.org/icom/icom-ics/v1.0/csprd05/icom-ics-v1.0-csprd05.pdf

XML Schemas:
http://docs.oasis-open.org/icom/icom-ics/v1.0/csprd05/schemas/

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/icom/icom-ics/v1.0/csprd05/icom-ics-v1.0-csprd05.zip

Additional information about the specification and the OASIS Integrated Collaboration Object Model for Interoperable Collaboration Services (ICOM) TC can be found at the TC’s public home page located at:

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

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=icom

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/icom-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 Integrated Collaboration Object Model (ICOM) for Interoperable Collaboration Services Version 1.0, we call your attention to the OASIS IPR Policy [3] applicable especially [4] 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 Integrated Collaboration Object Model for Interoperable Collaboration Services (ICOM) TC
http://www.oasis-open.org/committees/icom/

[2] Public Reviews:
15-day public review, 05 September 2012: https://lists.oasis-open.org/archives/tc-announce/201209/msg00000.html
15-day public review, 11 May 2012: https://lists.oasis-open.org/archives/tc-announce/201205/msg00004.html
15-day public review, 20 November 2011: http://www.oasis-open.org/apps/org/workgroup/icom/email/archives/201111/msg00010.html
30-day public review, 19 May 2011: http://lists.oasis-open.org/archives/tc-announce/201105/msg00002.html

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

[4] http://www.oasis-open.org/committees/icom/ipr.php
http://www.oasis-open.org/policies-guidelines/ipr#s10.2.3
RF on Limited Terms mode

The OASIS Web Services Calendar (WS-Calendar) TC members [1] have produced an updated Committee Specification Draft (CSD) and submitted this specification for 15-day public review:

WS-Calendar SOAP-based Services Version 1.0
Committee Specification Draft 02 / Public Review Draft 02
09 November 2012

Specification Overview:

This document describes standard messages and interactions for service interactions with a system that hosts calendar-based information using SOAP. Hosted information can be either traditional personal and enterprise calendar information or services that support XML payloads developed in conformance with the WS-Calendar specification.

TC Description:

The OASIS Web Services Calendar (WS-Calendar) Technical Committee was chartered to adapt the existing specifications for calendaring and apply them to develop a standard for how schedule and event information is passed between and within services. The standard should adopt the semantics and vocabulary of iCalendar for application to the completion of web service contracts.

Public Review Period:
The public review starts 26 November 2012 and ends 11 December 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:

PDF (Authoritative):
http://docs.oasis-open.org/ws-calendar/ws-calendar-soap/v1.0/csprd02/ws-calendar-soap-v1.0-csprd02.pdf

HTML:
http://docs.oasis-open.org/ws-calendar/ws-calendar-soap/v1.0/csprd02/ws-calendar-soap-v1.0-csprd02.html

Editable source:
http://docs.oasis-open.org/ws-calendar/ws-calendar-soap/v1.0/csprd02/ws-calendar-soap-v1.0-csprd02.odt

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/ws-calendar/ws-calendar-soap/v1.0/csprd02/ws-calendar-soap-v1.0-csprd02.zip

Additional information about this specification and the OASIS Web Services Calendar (WS-Calendar) TC may be found on the TC’s public home page located at:

http://www.oasis-open.org/committees/ws-calendar/

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=ws-calendar

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/ws-calendar-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 WS-Calendar SOAP-based Services Version 1.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 Web Services Calendar (WS-Calendar) TC
http://www.oasis-open.org/committees/ws-calendar/

[2] Previous public review:
30-day public review, 17 April 2012: https://lists.oasis-open.org/archives/tc-announce/201204/msg00005.html

[3] Red-lined diff file:
http://docs.oasis-open.org/ws-calendar/ws-calendar-soap/v1.0/csprd02/ws-calendar-soap-v1.0-csprd02-diff.pdf

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

[5] http://www.oasis-open.org/committees/ws-calendar/ipr.php
http://www.oasis-open.org/who/intellectualproperty.php#s10.3
Non-Assertion IPR Mode

The OASIS Biometric Identity Assurance Services (BIAS) Integration TC members [1] have produced an updated Committee Specification Draft (CSD) and submitted this specification for 15-day public review:

Biometric Identity Assurance Services (BIAS) SOAP Profile Version 1.0 Errata 01
Committee Specification Draft 01 / Public Review Draft 01
25 October 2012

Specification Overview:

This document lists errata for Biometric Identity Assurance Services (BIAS) SOAP Profile Version 1.0 produced by the OASIS Biometric Identity Assurance Services (BIAS) Technical Committee.

Public Review Period:

The public review starts 21 November 2012 and ends 06 December 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:

This Errata is part of a multi-part work product that also includes Biometric Identity Assurance Services (BIAS) SOAP Profile Version 1.0 Plus Errata01, OASIS Standard Incorporating Public Review Draft 01 of Errata 01

The prose specification document and related files are available here:

– Biometric Identity Assurance Services (BIAS) SOAP Profile Version 1.0 Errata01

Editable source (Authoritative)
http://docs.oasis-open.org/bias/soap-profile/v1.0/errata01/csprd01/biasprofile-v1.0-errata01-csprd01.doc

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

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

– Biometric Identity Assurance Services (BIAS) SOAP Profile Version 1.0 Plus Errata01
OASIS Standard Incorporating Public Review Draft 01 of Errata 01

Editable source (Authoritative):
http://docs.oasis-open.org/bias/soap-profile/v1.0/errata01/csprd01/biasprofile-v1.0-errata01-csprd01-complete.doc

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

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

Additional information about the specification and the OASIS Biometric Identity Assurance Services (BIAS) Integration TC may be found at the TC’s public home page located at:

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

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=bias

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/bias-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 Biometric Identity Assurance Services (BIAS) SOAP Profile Version 1.0 Errata 01, 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 Biometric Identity Assurance Services (BIAS) Integration TC
http://www.oasis-open.org/committees/bias/

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

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

Members of the Search Web Services TC [1] have recently approved a Special Majority Ballot [2] to advance searchRetrieve Version 1.0 as a Candidate OASIS Standard (COS). The COS now enters a 60-day public review period in preparation for a member ballot to consider its approval as an OASIS Standard.

searchRetrieve Version 1.0
Candidate OASIS Standard 01
25 October 2012

Specification Overview:

searchRetrieve Version 1.0 is a multi-part specification that defines a generic protocol for the interaction required between a client and server for performing searches.

Part 1, the Abstract Protocol Definition (APD) defines a model and a generic protocol for the interaction between a client and server for performing searches. It facilitates interoperability between different search protocols by providing a common framework and terminology for describing these search protocols.The intention is that all search protocols can be regarded as concrete implementations of this definition.

The model presumes that a client and server communicate via a searchRetrieve protocol which incorporates a query language. The APD serves as a guideline for the development of application protocol bindings for specific protocols.

The specification includes bindings for SRU1.2, SRU2.0 and OpenSearch. It specifies one query language, the Contextual Query Language (CQL). The specification also specifies a utility protocol, Scan, allowing a client
to request a range of the available terms at a given point within a list of indexed terms, used to select terms for subsequent searching.

Public Review Period:

The 60-day public review starts 15 November 2012 and ends 14 January 2013.

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:

– searchRetrieve: Part 0. Overview Version 1.0:

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

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

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

– searchRetrieve: Part 1. Abstract Protocol Definition Version 1.0:

Editable source (Authoritative):
http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/cos01/part1-apd/searchRetrieve-v1.0-cos01-part1-apd.doc

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

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

– searchRetrieve: Part 2. searchRetrieve Operation: APD Binding for SRU 1.2 Version 1.0:

Editable source (Authoritative):
http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/cos01/part2-sru1.2/searchRetrieve-v1.0-cos01-part2-sru1.2.doc

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

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

– searchRetrieve: Part 3. APD Binding for SRU 2.0 Version 1.0:

Editable source (Authoritative):
http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/cos01/part3-sru2.0/searchRetrieve-v1.0-cos01-part3-sru2.0.doc

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

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

– searchRetrieve: Part 4. APD Binding for OpenSearch Version 1.0:

Editable source (Authoritative):
http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/cos01/part4-opensearch/searchRetrieve-v1.0-cos01-part4-opensearch.doc

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

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

– searchRetrieve: Part 5. CQL: The Contextual Query Language Version 1.0:

Editable source (Authoritative):
http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/cos01/part5-cql/searchRetrieve-v1.0-cos01-part5-cql.doc

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

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

– searchRetrieve: Part 6. SRU Scan Operation Version 1.0:

Editable source (Authoritative):
http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/cos01/part6-scan/searchRetrieve-v1.0-cos01-part6-scan.doc

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

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

– searchRetrieve: Part 7. Explain Version 1.0:

Editable source (Authoritative):
http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/cos01/part7-explain/searchRetrieve-v1.0-cos01-part7-explain.doc

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

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

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

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

Additional information about the specification and the OASIS Search Web Services TC may be found at the TC’s public home page:

http://www.oasis-open.org/committees/search-ws/

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 page, or directly at:

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

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/search-ws-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 searchRetrieve Version 1.0, we call your attention to the OASIS IPR Policy [3] applicable especially [4] 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.

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

[2] Candidate OASIS Standard ballot
https://www.oasis-open.org/committees/ballot.php?id=2302

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

[4] http://www.oasis-open.org/committees/search-ws/ipr.php
RF on Limited Mode
https://www.oasis-open.org/policies-guidelines/ipr#s10.2.3

The OASIS Emergency Management TC members [1] have produced an updated Committee Specification Draft (CSD) and submitted this specification for 15-day public review:

Emergency Data Exchange Language (EDXL) Distribution Element Version 2.0
Committee Specification Draft 02 / Public Review Draft 02
11 September 2012

Specification Overview:

This Distribution Element 2.0 (DE 2.0) specification describes a standard message distribution format for data sharing among emergency information systems. The DE 2.0 serves two important purposes:

(1) The DE 2.0 allows an organization to wrap separate but related pieces of emergency information, including any of the EDXL message types, into a single “package” for easier and more useful distribution;

(2) The DE 2.0 allows an organization to “address” the package to organizations or individuals with specified roles, located in specified locations or those interested in specified keywords.

This version of the DE expands the ability to use local community-defined terms, uses a profile of the Geographic Markup Language (GML), follows best practices for naming conventions, provides the capability to link content objects, and is reorganized for increased flexibility and reuse of common types. The DE 2.0 packages and addresses emergency information for effective distribution with improved standardization and ability to be tailored for user needs.

Public Review Period:

The public review starts 12 November 2012 and ends 27 November 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/emergency/edxl-de/v2.0/csprd02/edxl-de-v2.0-csprd02.odt (Authoritative)

HTML:
http://docs.oasis-open.org/emergency/edxl-de/v2.0/csprd02/edxl-de-v2.0-csprd02.html

PDF:
http://docs.oasis-open.org/emergency/edxl-de/v2.0/csprd02/edxl-de-v2.0-csprd02.pdf

XML Schemas:
http://docs.oasis-open.org/emergency/edxl-de/v2.0/csprd02/schema/

XML Examples:
http://docs.oasis-open.org/emergency/edxl-de/v2.0/csprd02/examples/

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/emergency/edxl-de/v2.0/csprd02/edxl-de-v2.0-csprd02.zip

Additional information about the specification and the OASIS Emergency Management TC may be found at the TC’s public home page located at:

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

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=emergency

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/emergency-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 Emergency Data Exchange Language (EDXL) Distribution Element Version 2.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 Emergency Management TC
http://www.oasis-open.org/committees/emergency/

[2] Public Reviews:
45-day public review, 8 December 2011: https://lists.oasis-open.org/archives/tc-announce/201112/msg00002.html

[3] Redlined PDF DIFF file
http://docs.oasis-open.org/emergency/edxl-de/v2.0/csprd02/edxl-de-v2.0-csprd02-diff.pdf

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

[4] http://www.oasis-open.org/committees/emergency/ipr.php
http://www.oasis-open.org/policies-guidelines/ipr#s10.2.2
RF on RAND mode

We are pleased to announce that Test Assertions Model Version 1.0 OASIS Standard has been published and is available in the OASIS Library. The Standard defines a model for Test Assertions that are associated with a specification, and defines their use and semantics. The OASIS membership approved the Committee Specification as an OASIS Standard on 15 October 2012.

We congratulate the OASIS Test Assertions Guidelines (TAG) Technical Committee on achieving this milestone.

Test Assertions Model Version 1.0
OASIS Standard
15 October 2012

The prose specification document and related files are available here:

PDF (Authoritative):
http://docs.oasis-open.org/tag/model/v1.0/os/testassertionsmodel-1.0-os.pdf

HTML:
http://docs.oasis-open.org/tag/model/v1.0/os/testassertionsmodel-1.0-os.html

Editable Source:
http://docs.oasis-open.org/tag/model/v1.0/os/testassertionsmodel-1.0-os.odt

This specification is related to:

– Test Assertions Guidelines Version 1.0. Latest version:
http://docs.oasis-open.org/tag/guidelines/v1.0/guidelines-v1.0.html

– Test Assertion Markup Language Version 1.0. Latest version:
http://docs.oasis-open.org/tag/taml/v1.0/testassertionmarkuplanguage-1.0.html

For more information on Test Assertions Model v1.0 and the TC generally, see the TC’s web page at http://www.oasis-open.org/committees/tag/.

We are pleased to announce that OASIS Advanced Message Queueing Protocol (AMQP) Version 1.0 has been approved by the membership as an OASIS Standard [1].

The call to vote was announced on 15 October 2012 [2] and closed 29 October 2012. A minimum of 48 affirmative votes were needed in order to win approval. The finally vote tally was 66 affirmative votes, with one abstention and no negative votes..

AMQP (Advanced Message Queuing Protocol) is an efficient, reliable, wire level messaging protocol supporting common middleware messaging interaction patterns: messaging, request/response, publish/subscribe, transactions, and store and forward. It allows middleware applications to communicate with each other without having to have the same infrastructure on both ends (i.e. it provides vendor-neutral communications).

Like all communication protocols, AMQP describes the message syntax and sequence for performing their different assigned tasks. AMQP is capable of being used in both synchronous (point-to-point) and asynchronous (broker based) architectures and is independent of any particular broker architecture. AMQP is of special importance in providing enterprise and cloud messaging services.

URIs:

The complete OASIS Standard is available in PDF, HTML (six parts), and XML (six parts) formats in the OASIS Library at:

http://docs.oasis-open.org/amqp/core/v1.0/os/

The HTML Overview file, which contains links to all other parts, can be accessed at:

http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-overview-v1.0-os.html

The PDF file, which contains all six parts, can be accessed at:

http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-complete-v1.0-os.pdf

For your convenience, a ZIP file containing the entire OASIS Standard can be downloaded at:

http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-v1.0-os.zip

More information on AMQP Version 1.0 and the TC generally can be found on the TCs web page at http://www.oasis-open.org/committees/amqp/.

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] OASIS organizational ballot:
https://www.oasis-open.org/committees/ballot.php?id=2300

[2] Call to vote:
https://lists.oasis-open.org/archives/tc-announce/201210/msg00009.html