OASIS Forms AMQP Technical Committee to Advance Business Messaging Interoperability Within Middleware, Mobile, and Cloud Environments

1 Nov 2011 – The OASIS international open standards consortium announced the formation of a new Technical Committee for the Advanced Message Queuing Protocol (AMQP). A platform-agnostic solution for business messaging, AMQP provides organizations with an easier, more secure approach to passing real-time data streams and business transactions. The OASIS Technical Committee will advance the contributed AMQP version 1.0 through the international open standards process. “The implications of AMQP are potentially far-reaching. It could provide open interoperability, thereby reducing the cost of enterprise-quality messaging and making new kinds of applications practical,” said W. Roy Schulte, VP and Distinguished Analyst, Gartner Research. “AMQP’s move to OASIS marks a significant milestone in its evolution that will likely provide a significant boost in visibility and market interest.” “An efficient and open wire-level messaging protocol is a must for multi-vendor communications within the cloud,” said Angus Telfer of INETCO, co-chair of the OASIS AMQP Technical Committee. “AMQP fills that position in a vendor neutral way.” “The formation of the OASIS AMQP Technical Committee is an important next step in the advancement of AMQP as an open and interoperable messaging protocol. We expect the work done by the AMQP Technical Committee to open up new possibilities in business messaging,” said Ram Jeyaraman of Microsoft, who also co-chairs the OASIS AMQP Technical Committee. Current AMQP applications are as diverse as financial front office trading, ocean observation, computer-generated animation, and online gaming. Many operating systems include AMQP implementations, and many application frameworks are AMQP-aware. There are Cloud-hosted offerings of AMQP, and it is embedded in virtualization infrastructure. The OASIS AMQP Technical Committee currently has more than 50 members representing global financial service institutions, infrastructure providers, and integration, transaction and networking specialists from around the world. Participation is open to all interested parties, and new members may join at any time. Archives of the Committee’s work are accessible to both members and non-members, and OASIS invites public review and comment on the work. Support for AMQP Bank of America “The transition to OASIS marks a coming-of-age for AMQP. I look forward to the broader community that OASIS makes AMQP accessible to. I hope that others at OASIS will find AMQP a useful building block for their efforts at enabling connected business and look forward to engaging with them.” — John O’Hara, Chair of the OASIS AMQP Member Section and Head of Architecture Commodities Technology at Bank of America Merrill Lynch INETCO “Companies considering AMQP will need to see permanence and signs of a growing, knowledgeable eco-community. The OASIS AMQP Technical Committee will guarantee protocol stability, provide an international forum for all things AMQP, and ensure proven solutions are made accessible to AMQP implementers, such as the light-weight transaction management solution provided by INETCO that monitors AMQP business messaging performance across multi-vendor service applications, brokers, emerging mobile and cloud-based applications.”— Bijan Sanii, CEO, INETCO Kaazing “We are pleased to be a part of OASIS’ ongoing efforts to transform the way business is done in the Cloud and over the Internet. Kaazing, the enabler of the living web, is looking forward to participating and supporting this newly established technical committee dedicated to defining a ubiquitous, secure, reliable and open internet protocol for handling business messaging.”— John Fallows, CTO and Co-Founder, Kaazing Microsoft “As an active member of OASIS, Microsoft welcomes the formation of the AMQP Technical Committee. We hope that our contributions to this effort will serve to advance AMQP as an industry standard specification that can be broadly adopted across the industry, enabling both interoperability between vendor products and increased choice for customers. Microsoft supports thousands of standards in its products and we remain committed to supporting the development of new open standards and improving existing standards.” — Scott Guthrie, a corporate vice president in Microsoft’s Server and Tools Business division my-Channels “AMQP is facilitating improved information flows between the growing number of AMQP compliant messaging technologies in existence today. my-Channels is excited to have participated in the formation of the OASIS AMQP Technical Committee and continues to play an active role in the evolution and standardization of AMQP, a single standard targeted at enabling interoperability between middleware technologies. AMQP compatibility has been an important addition to my-Channels Nirvana and it has become increasingly important to our customers as AMQP gains trac-tion in the marketplace.” — Eddie McDaid, Director of Business Development, my-Channels Red Hat “Red Hat has been a long-time contributor to the AMQP Working Group as an original co-founder within the organization, and is pleased to extend our support and participation as a member of the OASIS AMQP Technical Committee. AMQP is a key messaging computing standard that we utilize in many of our solutions, including Red Hat Enterprise MRG and Red Hat Enterprise Linux, and we expect that it will continue to transform the industry with its extensions into the cloud.” — Carl Trieloff, Technical Director, Red Hat Software AG “For many years, Software AG has been closely involved at the forefront of leading industry standards, recognizing the need for interoperability in an ever-more connected world. AMQP is an exciting development aimed at overcoming practical barriers to B2B and large-scale enterprise integration and Software AG is proud to be part of this user-driven initiative.” — Hans-Christoph Rohland, Senior Vice President R&D, Software AG VMware “VMware welcomes the creation of the AMQP Technical Committee at OASIS. This is another important milestone which will help bring standardized and interoperable business messaging to a broad cross-section of the industry. We are committed to working with our partners and customers in developing and supporting the critical standards that will enable the open cloud computing vision.” — Winston Bumpus, Director of Standards Architecture, VMware Zenika “We fully expect AMQP to become the standard building block for middleware interoperability. As a global consulting group that architects and deploys message-oriented middleware systems for both banking and industrial customers, Zenika is proud to be part of the OASIS AMQP Technical Committee.” — Pierre Queinnec, Chief Technical Officer (CTO), Zenika Additional information: OASIS AMQP Technical Committee OASIS AMQP Member Section About OASIS: OASIS (Organization for the Advancement of Structured Information Standards) is a not-for-profit, international consortium that drives the development, convergence and adoption of open standards for the global information society. OASIS promotes industry consensus and produces worldwide standards for business transactions, security, privacy, cloud computing, SOA, the Smart Grid, content technologies, emergency management, and other applications. OASIS open standards offer the potential to lower cost, stimulate innovation, grow global markets, and protect the right of free choice of technology. OASIS members broadly represent the marketplace of public and private sector technology leaders, users, and influencers. The consortium has more than 5,000 participants representing over 600 organizations and individual members in 100 countries. http://www.oasis-open.org Press contact: Carol Geyer Senior Director of Communications and Development OASIS carol.geyer@oasis-open.org

(PR) 30-day Public Review for EMIX Committee Note Drafts

The OASIS Energy Market Information Exchange (EMIX) TC [1] members have recently approved six Committee Note Drafts (CNDs) and submitted these drafts for 30-day public review:

EMIX Overview Version 1.0
Committee Note Draft 01 / Public Review Draft 01
12 October 2011

EMIX 1.0 and the OASIS Smart Grid Suite of Standards
Committee Note Draft 01 / Public Review Draft 01
13 October 2011

Retail Block & Tier Prices using EMIX 1.0
Committee Note Draft 01 / Public Review Draft 01
13 October 2011

Using EMIX 1.0 to support Transactive Energy Markets
Committee Note Draft 01 / Public Review Draft 01
30 September 2011

Transactive Energy Market Information Exchange (TeMIX) using EMIX 1.0
Committee Note Draft 01 / Public Review Draft 01
13 October 2011

TEMIX, a transactive profile of EMIX 1.0
Committee Note Draft 01 / Public Review Draft 01
30 September 2011

Specification Overview:
This group of Committee Specification Drafts explain what EMIX is, what it can do, and how it works with other specifications and standards. The goal of the Technical Commitee is to produce brief, focused Notes explaining applications, addressing technical issues, and providing examples for the use of EMIX.

This group of six is entering the Public Review process together. Three Note Drafts address general and technical issues:

* EMIX Overview Version 1.0

* EMIX 1.0 and the OASIS Smart Grid Suite of Standards

* Retail Block & Tier Prices using EMIX 1.0

and three Note Drafts address the use of EMIX in Transactive Energy Markets in the broad sense, and a brief and a longer Note Draft describing the restricted profile TEMIX:

* Using EMIX 1.0 to support Transactive Energy Markets

* Transactive Energy Market Information Exchange (TeMIX) using EMIX 1.0

* TEMIX, a Transactive Profile of EMIX 1.0

When providing review comments, please use the line numbers in the respective PDFs for each Note Draft.

TC Description :
OASIS Energy Market Information Exchange is now in its fourth Public Review. As that work is nearly completed, the Technical Committee is working on roughly a dozen Technical Notes.

The purpose of these notes is to provide an overview and understanding of EMIX.

Notes in process describe the relationship with OpenADR and Energy Interoperation, the Transactive Energy Markets approach that motivated several TC members, answer questions about the technical application of EMIX, such as the expression of Block & Tier prices, the use of and relationship of EMIX with facility automation systems including the ZigBee Smart Energy Profile, the description of Ancillary Services products, and relationships and mapping to and from IEC and other standards.

Public Review Period:

The public review starts 1 November 2011 and ends 30 November 2011.

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 Committee Note Documents are available in the ZIP distribution files at the following URIs:

EMIX Overview Version 1.0
http://www.oasis-open.org/committees/download.php/44171/emix-over-v1.0-cnprd01.zip

EMIX 1.0 and the OASIS Smart Grid Suite of Standards
http://www.oasis-open.org/committees/download.php/44170/emix-oasis-v1.0-cnprd01.zip

Retail Block & Tier Prices using EMIX 1.0
http://www.oasis-open.org/committees/download.php/44168/emix-block-v1.0-cnprd01.zip

Using EMIX 1.0 to support Transactive Energy Markets
http://www.oasis-open.org/committees/download.php/44174/emix-trans-v1.0-cnprd01.zip

Transactive Energy Market Information Exchange (TeMIX) using EMIX 1.0
http://www.oasis-open.org/committees/download.php/44172/emix-temix-v1.0-cnprd01.zip

TEMIX, a transactive profile of EMIX 1.0
http://www.oasis-open.org/committees/download.php/44173/emix-temixbrief-v1.0-cnprd01.zip

Additional information about the specification and the OASIS Energy Market Information Exchange (eMIX) TC may be found at the TC’s public home page located at:

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

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

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/emix-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 these EMIX Committee 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 Energy Market Information Exchange (eMIX) TC
http://www.oasis-open.org/committees/emix/

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

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

(PR) 15-day Public Review for Service Component Architecture SCA-J Common Annotations and APIs Specification Version 1.1

The OASIS Service Component Architecture / J (SCA-J) TC [1] members have produced an updated Committee Specification Draft (CSD) and submitted this specification for 15-day public review:

Service Component Architecture SCA-J Common Annotations and APIs Specification Version 1.1
Committee Specification Draft 06 / Public Review Draft 04
15 August 2011

Specification Overview:
The SCA-J Common Annotations and APIs specification defines a Java syntax for programming concepts defined in the SCA Assembly Model Specification. It specifies a set of APIs and annotations that can be used by Java-based artifacts described by other SCA specifications such as the POJO Component Implementation Specification [JAVA_CI].

Specifically, this specification covers:
1. Implementation metadata for specifying component services, references, and properties
2. A client and component API
3. Metadata for asynchronous services
4. Metadata for callbacks
5. Definitions of standard component implementation scopes
6. Java to WSDL and WSDL to Java mappings
7. Security policy annotations

Note that other Java-based SCA specifications can choose to implement their own mappings of assembly model concepts using native APIs and idioms when appropriate.

TC Description:
The SCA-J TC defines the Java ™ language binding for SCA components based on the SCA Assembly specification. The specifications include POJO/Spring client and implementation specification, a common annotations specification, an EJB binding specification and the J2EE integration specification.

Public Review Period:
The public review starts 27 October 2011 and ends 11 November 2011. The specification was previously submitted for a 15-day public review on 23 November 2010 [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 in the specification package.

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/44110/sca-javacaa-1.1-spec-csprd04.zip

Additional information about the specification and the Service Component Architecture / J (SCA-J) TC may be found at the TC’s public home page located at:

http://www.oasis-open.org/committees/sca-j/

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=sca-j

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/sca-j-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 Service Component Architecture SCA-J Common Annotations and APIs Specification Version 1.1, 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 Service Component Architecture / J (SCA-J) TC
http://www.oasis-open.org/committees/sca-j

[2] Previous public reviews
15-day public review, 23 November 2010: http://lists.oasis-open.org/archives/members/201011/msg00010.html
60-day public review, 8 June 2009: http://lists.oasis-open.org/archives/members/200906/msg00002.html

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

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

[PR] 15-day Public Review for Service Component Architecture Assembly Model Specification Version 1.1

The OASIS Service Component Architecture / Assembly (SCA-Assembly) TC [1] members have produced an updated Committee Specification Draft (CSD) and submitted this specification for 15-day public review:

Service Component Architecture Assembly Model Specification Version 1.1
Committee Specification Draft 09 / Public Review Draft 04
13 September 2011

Specification Overview:
The SCA Assembly Model consists of a series of artifacts which define the configuration of an SCA Domain in terms of composites which contain assemblies of service components and the connections and related artifacts which describe how they are linked together.

This specification describes the SCA Assembly Model, which covers:
– A model for the assembly of services, both tightly coupled and loosely coupled
– A model for applying infrastructure capabilities to services and to service interactions, including Security and Transactions

TC Description:
The SCA Assembly TC has completed work on V1.1 of the Assembly specification and is working towards publishing the specification as a Committee Specification.

Public Review Period:
The public review starts 26 October 2011 and ends 10 November 2011. The specification was previously submitted for a 15-day public review on 9 August 2011 [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 included in the specification package.

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/44090/sca-assembly-spec-v1.1-csprd04.zip

Additional information about the specification and the OASIS Service Component Architecture / Assembly (SCA-Assembly) TC may be found at the TC’s public home page located at:

http://www.oasis-open.org/committees/sca-assembly/

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=sca-assembly

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/sca-assembly-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 Service Component Architecture Assembly Model Specification Version 1.1, 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 Service Component Architecture / Assembly (SCA-Assembly) TC
http://www.oasis-open.org/committees/sca-assembly

[2] Previous public reviews
15-day public review, 9 August 2011: http://lists.oasis-open.org/archives/members/201108/msg00005.html
15-day public review, 16 February 2010: http://lists.oasis-open.org/archives/members/201002/msg00006.html
60-day public review, 24 April 2009: http://lists.oasis-open.org/archives/members/200904/msg00007.html

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

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

[PR] 15-day Public Review for Field Force Management Integration Interface Requirements Version 1.0

The Field Force Management (FFM) TC members have produced an updated Committee Note Draft (CND) and submitted this note for 15-day public review:

Field Force Management Integration Interface Requirements Version 1.0
Committee Note Draft 01 / Public Review Draft 01
12 September 2011

Specification Overview:
This document describes the Field Force Management Integration Interface (FFMII) business drivers, business use cases, and high level features requirements.

TC Description:
The OASIS FFM TC addresses the data use and integration challenges faced by enterprises that deploy large field staffs to deliver services to customers. FFM TC members define a standard integration interface for use in relaying field work requests between centralized planning and field communication systems. Principal use cases include field work request dispatching and the reliable and scalable collection of data from the field. FFM is designed for use in products that support communication between field work operations and central data stores such as CRM contact info, job ticketing, inventory and accounting systems, installation records, etc.

Public Review Period:
The public review starts 26 October 2011 and ends 10 November 2011.

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/44076/FFM-IF-Requirements-v1.0-cnprd01.zip

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

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

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/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 Requirements 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/who/intellectualproperty.php#s10.2.3
RF on Limited Terms

[PR] 60-day Candidate OASIS Standard Public Review for ebXML RegRep Version 4.0

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

OASIS ebXML RegRep Version 4.0
Candidate OASIS Standard 01
15 September 2011

Specification Overview:
The OASIS ebXML RegRep Version 4.0 specification is a multi-part specification that may be used to implement interoperable registries and repositories. The complete specification is composed of:

* Part 0: Overview Document – provides a global overview and description of all the other parts
* Part 1: Registry Information Model (ebRIM) – specifies the types of metadata and content that can be stored in an ebXML RegRep
* Part 2: Services and Protocols (ebRS) – specifies the services and protocols for ebXML RegRep
* Part 3: XML Schema – specifies the XML Schema for ebXML RegRep
* Part 4: WSDL – specifies the WSDL interface descriptions for ebXML RegRep
* Part 5: XML Definitions – specifies the canonical XML data for ebXML RegRep as well as example XML documents used in the specification


Public Review Period:
The 60-day public review starts today, 24 October 2011 and ends 23 December 2011.

The specification was previously submitted for a 30-day public review on 15 June 2011 [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:

* Part 0: Overview Document
Editable Source: (Authoritative)
http://docs.oasis-open.org/regrep/regrep-core/v4.0/cos01/regrep-core-overview-v4.0-cos01.odt

HTML:
http://docs.oasis-open.org/regrep/regrep-core/v4.0/cos01/regrep-core-overview-v4.0-cos01.html

PDF:

http://docs.oasis-open.org/regrep/regrep-core/v4.0/cos01/regrep-core-overview-v4.0-cos01.pdf

* Part 1: Registry Information Model (ebRIM)
Editable Source: (Authoritative)
http://docs.oasis-open.org/regrep/regrep-core/v4.0/cos01/regrep-core-rim-v4.0-cos01.odt

HTML:
http://docs.oasis-open.org/regrep/regrep-core/v4.0/cos01/regrep-core-rim-v4.0-cos01.html

PDF:

http://docs.oasis-open.org/regrep/regrep-core/v4.0/cos01/regrep-core-rim-v4.0-cos01.pdf

* Part 2: Services and Protocols (ebRS)
Editable Source: (Authoritative)
http://docs.oasis-open.org/regrep/regrep-core/v4.0/cos01/regrep-core-rs-v4.0-cos01.odt

HTML:
http://docs.oasis-open.org/regrep/regrep-core/v4.0/cos01/regrep-core-rs-v4.0-cos01.html

PDF:

http://docs.oasis-open.org/regrep/regrep-core/v4.0/cos01/regrep-core-rs-v4.0-cos01.pdf

* Part 3: XML Schema
http://docs.oasis-open.org/regrep/regrep-core/v4.0/cos01/xsd/

* Part 4: WSDL
http://docs.oasis-open.org/regrep/regrep-core/v4.0/cos01/wsdl/1.1/

* Part 5: XML Definitions
http://docs.oasis-open.org/regrep/regrep-core/v4.0/cos01/xml/

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/regrep/regrep-core/v4.0/cos01/regrep-core-v4.0-cos01.zip

Additional information about the specification and the OASIS ebXML Registry TC may be found at the TC’s public home page:

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

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

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/regrep-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 OASIS ebXML RegRep Version 4.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.

==============
[1] OASIS ebXML Registry Technical Committee
http://www.oasis-open.org/committees/regrep/

[2] COS ballot
http://www.oasis-open.org/committees/ballot.php?id=2105

CS ballot
http://www.oasis-open.org/apps/org/workgroup/regrep/ballot.php?id=2072

[3] 30-day public review:
http://lists.oasis-open.org/archives/tc-announce/201106/msg00004.html

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

[5] RF on Limited Terms Mode IPR Mode

http://www.oasis-open.org/committees/office/ipr.php

http://www.oasis-open.org/who/intellectualproperty.php#s10.2.3

OASIS briefing to European Parliament at Open Forum Europe

Read transcript from 19 Oct in Brussels

OASIS to Define Trust Elevation Standard for Authenticating e-Identity Credentials

19 Oct 2011 – The OASIS international open standards consortium has begun work to define a set of standardized protocols that online service providers may use to elevate trust when authenticating electronic identity credentials. The goal of the new OASIS Electronic Identity Credential Trust Elevation Methods (Trust Elevation) Technical Committee is to extend interoperability among online service providers (such as banks and health care providers) and make e-transactions easier for end users.

The OASIS Trust Elevation protocol will be vendor-neutral and product-agnostic. It will promote interoperability among multiple identity providers as well as among federations and frameworks. The work will reconcile the fundamental gap between credential-based trust approaches (used in e-gov) and transaction risk mitigation-based trust approaches (used in B2B).

The Trust Elevation Committee was formed in response to governments calling for national and global identity infrastructures to be developed through private sector cooperation among providers, users, and subjects of trusted identity systems.

“We are pleased to be a co-founder and convener of the OASIS Trusted Elevation Technical Committee,” said Jeremy Grant, Senior Executive Advisor for Identity Management at the U.S. National Institute of Standards and Technology (NIST). “The group’s focus on identifying and analyzing the broad range of products, services and techniques used to ensure high levels of trust in online transactions will help to create new solutions to support the National Identity for Trusted Identities in Cyberspace (NSTIC). The insight gained about how these techniques work–and how well they work–will be a valuable addition to our existing knowledge on using credential-based techniques for assuring high levels of trust in online transactions.”

The OASIS Trust Elevation Committee currently has more than 40 members representing financial services companies, healthcare organizations, government agencies, academia, software providers, and other groups from around the world. The Committee is co-chaired by Abbie Barbir of Bank of America and Don Thibeau of Open Identity Exchange (OIX).

“We intend to analyze and build on what’s out there, re-using existing definitions of policy concepts, such as identity tokens and personally-identifiable data wherever possible,” said Thibeau. “The Committee will provide functional comparisons of alternative assurance level schemes, making it easy to map our trust elevation processes to a wide variety of regulatory frameworks.”

Participation in the Trust Elevation Technical Committee is open to all interested parties. Archives of the Committee’s work are accessible to both members and non-members, and OASIS invites public review and comment.

Support for Trust Elevation

Axiomatics
“Axiomatics is proud to take part in the OASIS Trust Elevation Technical Committee. As a global leader in context-aware authorization based on XACML, we advocate the use of standards. We believe it is important to provide a standardized baseline for authentication based on electronic identity. We feel it is important to take part in this initiative to raise awareness of the different authentication alternatives and to produce best practices and recommendations for online security.”
–David Brossard, VP Product Marketing & Customer Relations, Axiomatics

CA Technologies

“As more and more critical transactions take place online, the need for strong and robust identity authentication tools has become more critical than ever. The adoption of interoperable electronic identity authentication technologies at varying levels will enhance security and ease of use for users. We are excited to participate in the newly formed OASIS Trust Elevation Technical Committee, which will examine trust elevation methods in use globally today, and work to identify standard protocols to ensure that trusted transactions can be conducted with multiple partners at different levels of trust.”
–Brendan M. Peter, Director, Global Government Relations, CA Technologies

OIX
“There is an important connection between the Open Identity Exchange attribute binding pilots Google and Verizon are sponsoring and the OASIS Trust Elevation Technical Committee’s work. The OIX pilots could be helpful because they are real time, transparent tests of technology interoperability and the value of user asserted and permissioned attributes in the emerging identity ecosystem. Together, the OIX pilots and the OASIS Trust Elevation Committee work represent important and constructive steps towards new approaches to identity verification for step up multi-factor authentication solutions.”
— Don Thibeau, Chairman and President, OIX

Additional information:
OASIS Trust Elevation Technical Committee

About OASIS:
OASIS (Organization for the Advancement of Structured Information Standards) is a not-for-profit, international consortium that drives the development, convergence and adoption of open standards for the global information society. OASIS promotes industry consensus and produces worldwide standards for security, privacy, cloud computing, SOA, Web services, the Smart Grid, content technologies, business transactions, emergency management, and other applications. OASIS open standards offer the potential to lower cost, stimulate innovation, grow global markets, and protect the right of free choice of technology. OASIS members broadly represent the marketplace of public and private sector technology leaders, users, and influencers. The consortium has more than 5,000 participants representing over 600 organizations and individual members in 100 countries.

Press contact:
Carol Geyer
OASIS Senior Director of Communications and Development
carol.geyer@oasis-open.org
+1.941.284.0403

[PR] 30-day Public Review for SAML V2.0 Attribute Predicate Profile Version 1.0

The OASIS Security Services (SAML) TC [1] members have recently approved a Committee Specification Draft and submitted this specification for 30-day public review:

SAML V2.0 Attribute Predicate Profile Version 1.0
Committee Specification Draft 01 / Public Review Draft 01
26 July 2011

Specification Overview:
The SAML V2.0 Attribute Predicate Profile provides a mechanism to allow a SAML authority to certify that a given Boolean predicate holds over one or more of a subject’s attribute values, without revealing the exact values of these attributes. The profile further defines a query format for attribute predicates.

Public Review Period:
The public review starts 15 October 2011 and ends 14 November 2011.

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/43935/sstc-saml-attr-predicate-v1.0-csprd01.zip

Additional information about the specification and the OASIS Security Services (SAML) TC may be found at the TC’s public home page:

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

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

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/security-services-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 SAML V2.0 Attribute Predicate Profile 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 Security Services (SAML) TC
http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=security

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

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

[PR] 30-day Public Review for SAML V2.0 Metadata Extensions for Login and Discovery User Interface Version 1.0

The OASIS Security Services (SAML) TC [1] members have recently approved a Committee Specification Draft and submitted this specification for 30-day public review:

SAML V2.0 Metadata Extensions for Login and Discovery User Interface Version 1.0
Committee Specification Draft 02 / Public Review Draft 01
26 July 2011

Specification Overview:
This document defines a set of extensions to SAML metadata that provide information necessary for user agents to present effective user interfaces and, in the case of identity provider discovery, recommend appropriate choices to the user.

Public Review Period:
The public review starts Friday, 14 October 2011 and ends 13 November 2011.

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/43924/sstc-saml-metadata-ui-v1.0-csprd01.zip

Additional information about the specification and the OASIS Security Services (SAML) TC may be found at the TC’s public home page:

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

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

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/security-services-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 SAML V2.0 Metadata Extensions for Login and Discovery User Interface 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 Security Services (SAML) TC
http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=security

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

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

[PR] 15-day Public Review for SAML 2.0 Profile of XACML, Version 2.0

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

SAML 2.0 Profile of XACML, Version 2.0
Committee Specification Draft 04 / Public Review Draft 03
22 September 2011

Specification Overview:
This specification defines a profile for the integration of the OASIS Security Assertion Markup Language (SAML) Version 2.0 with all versions of XACML. SAML 2.0 complements XACML functionality in many ways, so a number of somewhat independent functions are described in this profile:

1) use of SAML 2.0 Attribute Assertions with XACML, including the use of SAML Attribute Assertions in a SOAP Header to convey Attributes that can be consumed by an XACML PDP,
2) use of SAML to carry XACML authorization decisions, authorization decision queries, and authorization decision responses,
3)use of SAML to carry XACML policies, policy queries, and policy query responses,
4) use of XACML authorization decisions or policies as Advice in SAML Assertions, and
5) use of XACML responses in SAML Assertions as authorization tokens.

Particular implementations may provide only a subset of these functions.

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

Public Review Period:
The public review starts Friday, 14 October 2011 and ends 29 October 2011. The specification was previously submitted for a 30-day public review on 7 May 2010 [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 included in the release package.

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/43921/xacml-profile-saml2.0-v2-csprd03.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 SAML 2.0 Profile of XACML, Version 2.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 eXtensible Access Control Markup Language (XACML) TC
http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=xacml

[2] Previous public reviews
30-day public review, 7 May 2010: http://lists.oasis-open.org/archives/tc-announce/201005/msg00003.html
60-day public review, 21 May 2009: http://lists.oasis-open.org/archives/tc-announce/200905/msg00006.html

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

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

15-day Public Review for Content Management Interoperability Services (CMIS) V1.0 Errata 01

The OASIS Content Management Interoperability Services (CMIS) TC members have produced an updated Committee Specification Draft (CSD) and submitted this specification for 15-day public review:

Content Management Interoperability Services (CMIS) Version 1.0 Errata 01
Committee Specification Draft 02 / Public Review Draft 02
08 August 2011

Specification Overview:
This is an Errata for CMIS 1.0. It contains a list of nonsubstantive changes to the CMIS 1.0 specification.

TC Description:
The CMIS TC develops interoperable interfaces for content management repositories/systems, and conducts interoperability testing among TC member implementations.

Public Review Period:
The public review starts Monday, 10 October 2011 and ends Tuesday, 25 October 2011. The specification was previously submitted for a 15-day public review on 8 June 2011 [2].

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/43812/cmis-spec-v1.0-errata-01-csprd02.zip

Additional information about the specification and the OASIS Content Management Interoperability Services (CMIS) TC may be found at the TC’s public home page located at:

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

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/index.php?wg_abbrev=cmis

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/cmis-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 Content Management Interoperability Services (CMIS) Version 1.0 Errata 01, 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 Content Management Interoperability Services (CMIS) TC
http://www.oasis-open.org/committees/cmis/

[2] 15-day public review: http://lists.oasis-open.org/archives/tc-announce/201106/msg00002.html

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

[4] http://www.oasis-open.org/committees/cmis/ipr.php
http://www.oasis-open.org/who/intellectualproperty.php
RF on RAND Mode

No results with the selected filters