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

AS4 Profile of ebMS 3.0 Version 1.0
Committee Specification Draft 05 / Public Review Draft 04
21 March 2012

Specification Overview:
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.

TC Description:
The ebXML Messaging Services Technical Committee designs Web Services-based messaging protocols for the transport, routing and packaging of B2B transactions.

Public Review Period:
The public review starts 30 March 2012 and ends 14 April 2012. The specification was previously submitted for a 15-day public review on 12 July 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 review 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/45570/AS4-profile-v1.0-csprd04.zip

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

http://www.oasis-open.org/committees/ebxml-msg/

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=ebxml-msg

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/ebxml-msg-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 AS4 Profile of ebMS 3.0 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 ebXML Messaging Services TC
http://www.oasis-open.org/committees/ebxml-msg/

[2] Public reviews:
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] http://www.oasis-open.org/who/intellectualproperty.php

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

OASIS Members,

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

SAML V2.0 Kerberos Web Browser SSO Profile Version 1.0
Committee Specification 01
07 February 2012

Overview:
The SAML V2.0 Kerberos Web Browser SSO Profile allows for transport of assertions using the Kerberos subject confirmation method by standard HTTP user agents with no modification of client software and maximum compatibility with existing deployments. The flow is similar to standard Web Browser SSO, but a Kerberos AP-REQ message is presented by the user agent via the HTTP Negotiate authentication scheme and the Kerberos GSS-API mechanism. The presentation of a valid Kerberos AP-REQ message whose client principal name matches the principal name given in the subject confirmation strengthens the assurance of the resulting authentication context and protects against credential theft.

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

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

HTML:
http://docs.oasis-open.org/security/saml/Post2.0/saml-kerberos-browser-sso/v1.0/cs01/saml-kerberos-browser-sso-v1.0-cs01.html

PDF:
http://docs.oasis-open.org/security/saml/Post2.0/saml-kerberos-browser-sso/v1.0/cs01/saml-kerberos-browser-sso-v1.0-cs01.pdf

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

Members of the OASIS Security Services (SAML) TC [1] 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 Committee Specification 01 is now available online in the OASIS Library as referenced above.

Our congratulations to the TC on achieving this milestone.

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

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

[2] Public reviews
15-day public review, 04 December 2011: http://lists.oasis-open.org/archives/tc-announce/201112/msg00000.html
60-day public review, 16 April 2010: http://lists.oasis-open.org/archives/tc-announce/201004/msg00005.html

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

OASIS Members,

We are pleased to announce the approval and publication of an OASIS Committee Specification (CS) by the members of the OASIS Energy Interoperation TC:

Energy Interoperation Version 1.0
Committee Specification 02
[Committee Specification 01 with errata]
18 February 2012

Overview:
OASIS Energy interoperation describes an information model and a communication model to enable collaborative and transactive use of energy, service definitions consistent with the OASIS SOA Reference Model, and XML vocabularies for the interoperable and standard exchange of:

* Dynamic price signals
* Reliability signals
* Emergency signals
* Communication of market participation information such as bids
* Load predictability and generation information

This work facilitates enterprise interaction with energy markets, which:

* Allows effective response to emergency and reliability events
* Allows taking advantage of lower energy costs by deferring or accelerating usage,
* Enables trading of curtailment and generation,
* Supports symmetry of interaction between providers and consumers of energy,
* Provides for aggregation of provision, curtailment, and use

The definition of a price and of reliability information depends on the market context in which it exists. It is not in scope for this TC to define specifications for markets or for pricing models, but the TC has coordinated with others to ensure that commonly used market and pricing models are supported.

While this specification uses Web Services to describe the services, no requirement or expectation of specific messaging implementation is assumed.

This document incorporates minor editorial and typographic corrections from Energy Interoperation Version 1.0 Committee Specification 01.

TC Description:

All work of the OASIS Energy Interoperation Technical Committee (TC) is publicly visible through the TCs home page at http://www.oasis-open.org/committees/energyinterop, including all correspondence and prior drafts.

The committee includes members representing Independent System Operators and Regional Transmission Operators as well as the ISO/RTO Council, Utilities, Lawrence Berkeley Laboratories, building automation standards, market communication, schedule communication, electronic commerce (B2B) and software architecture experts and more.

The work of this committee is built in part on contributions of Requirements for Demand Response PAP09 (NAESB), OpenADR 1.0 (LBL), and business information requirements (IRC) as well as substantial contributions from members of the OpenADR Alliance.

The specification names three profiles, OpenADR 2.0, Price Distribution, and Transactive Energy, which call out subsets of the specification for particular purposes.

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

PDF (Authoritative):
http://docs.oasis-open.org/energyinterop/ei/v1.0/cs02/energyinterop-v1.0-cs02.pdf

HTML:
http://docs.oasis-open.org/energyinterop/ei/v1.0/cs02/energyinterop-v1.0-cs02.html

Editable Source:
http://docs.oasis-open.org/energyinterop/ei/v1.0/cs02/energyinterop-v1.0-cs02.doc

XML schemas:
http://docs.oasis-open.org/energyinterop/ei/v1.0/cs02/xsd/

wsdl files:
http://docs.oasis-open.org/energyinterop/ei/v1.0/cs02/wsdl/

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/energyinterop/ei/v1.0/cs02/energyinterop-v1.0-cs02.zip

Members of the OASIS Energy Interoperation TC [1] 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 CS02 is now available online in the OASIS Library as referenced above.

Our congratulations to the TC on achieving this milestone.

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

[1] OASIS Energy Interoperation TC
http://www.oasis-open.org/committees/energyinterop/

[2] Public reviews
15-day public review, 12 January 2012: http://lists.oasis-open.org/archives/tc-announce/201201/msg00002.html
15-day public review, 17 November 2011: http://lists.oasis-open.org/archives/tc-announce/201111/msg00005.html
15-day public review, 10 August 2011: http://lists.oasis-open.org/archives/tc-announce/201108/msg00005.html
30-day public review, 27 November 2010: http://lists.oasis-open.org/archives/tc-announce/201011/msg00014.html

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

OASIS Members,

We are pleased to announce the approval of an OASIS Committee Specification (CS) by the members of the Energy Market Information Exchange (eMIX) TC:

Energy Market Information Exchange (EMIX) Version 1.0
Committee Specification 02
11 January 2012

Overview:
This specification defines an information model and XML vocabulary for the interoperable and standard exchange of prices and product definitions in transactive energy markets:

* Price information
* Bid information
* Time for use or availability
* Units and quantity to be traded
* Characteristics of what is traded

This specification is one of three related OASIS technical works in progress. For a graphical view of the relationships, see http://collaborate.nist.gov/twiki-sggrid/bin/view/SmartGrid/EMIXissuesPage on the NIST Smart Grid collaborative site.

(a) Web Services Calendar 1.0 (WS-Calendar Technical Committee page is http://www.oasis-open.org/committees/ws-calendar) is the common XML vocabulary for expressing schedules. EMIX uses this vocabulary to express energy
schedules and prices; implementers and other standards are also using WS-Calendar. WS-Calendar has just started its third Public Review.

(b) Energy Market Information Exchange 1.0 (EMIX Technical Committee page is http://www.oasis-open.org/committees/emix) is the TC that has approved this public review. EMIX is the common XML vocabulary for expressing market information including tenders, market transactions, prices and product definitions for implementers and other standards. EMIX uses the WS-Calendar vocabulary to express schedule information, and the EMIX vocabulary is used by Energy Interoperation and other standards and implementations.

(c) Energy Interoperation 1.0 (Energy Interoperation Technical Committee page is http://www.oasis-open.org/committees/energyinterop) is the common XML vocabulary for expressing curtailment events, price communication, as well as Web services definitions for interactions using the information payloads. The Energy Interoperation TC is planning its second Public Review in July 2011.

Please refer to line numbers in the PDF version of the specification when providing comments.

TC Description:
The OASIS Energy Market Information Exchange (eMIX) TC [1] was chartered to define standards for exchanging energy characteristics, availability, and schedules to support the free and effective exchange of information. Better communication of actionable energy prices will help enable and expand efficient markets that satisfy the growing demand for lower-carbon, lower-energy buildings, net zero-energy systems, and supply-demand integration that take advantage of dynamic pricing. The TC has addressed requirements consolidated by NAESB and the Smart Grid Interoperability Panel’s Priority Action Plan 03 Working Group.

Direct participants have included representatives of Southern California Edison, the ISO-RTO Council, California ISO, Midwest ISO, New York ISO, Lawrence Berkeley National Laboratory, Enernex, UISOL, members of the UCAIug OpenADR Task Force, the OpenADR Alliance, and representatives of the National Institute of Science and Technology, Schneider Electric, Siemens AG, EPRI, OATi, The Open Geospatial Consortium, LonMark International, Lockheed Martin, EnerNOC, Trane, CPower, Microsoft, JPMorganChase, TIBCO, University of North Carolina, Alstom Power, and experts in energy markets and in cross-domain integration and information modeling.

This work is closely related to OASIS WS-Calendar 1.0 and OASIS Energy Interoperation 1.0.

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

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

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

Editable Source:
http://docs.oasis-open.org/emix/emix/v1.0/cs02/emix-v1.0-cs02.doc

XML schemas:
http://docs.oasis-open.org/emix/emix/v1.0/cs02/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/emix/emix/v1.0/cs02/emix-v1.0-cs02.zip

Members of the OASIS Energy Market Information Exchange (eMIX) TC [1] 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 CS02 is now available online in the OASIS Library as referenced above.

Our congratulations to the TC on achieving this milestone.

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

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

[2] Public review
15-day public review, 21 November 2011: http://lists.oasis-open.org/archives/tc-announce/201111/msg00009.html
15-day public review, 05 October 2011: http://lists.oasis-open.org/archives/emix/201110/msg00003.html
15-day public review, 08 July 2011: http://lists.oasis-open.org/archives/tc-announce/201107/msg00002.html
15-day public review, 11 May 2011: http://lists.oasis-open.org/archives/tc-announce/201105/msg00000.html
30-day public review, 17 November 2010: http://lists.oasis-open.org/archives/members/201011/msg00005.html

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

OASIS Members,

We are pleased to announce the approval and publication of an OASIS Committee Specification (CS) by the members of the OASIS Energy Interoperation TC:

Energy Interoperation Version 1.0
Committee Specification 01
16 December 2011

Overview:
OASIS Energy interoperation describes an information model and a communication model to enable collaborative and transactive use of energy, service definitions consistent with the OASIS SOA Reference Model, and XML vocabularies for the interoperable and standard exchange of:

* Dynamic price signals
* Reliability signals
* Emergency signals
* Communication of market participation information such as bids
* Load predictability and generation information

This work facilitates enterprise interaction with energy markets, which:

* Allows effective response to emergency and reliability events
* Allows taking advantage of lower energy costs by deferring or accelerating usage,
* Enables trading of curtailment and generation,
* Supports symmetry of interaction between providers and consumers of energy,
* Provides for aggregation of provision, curtailment, and use

The definition of a price and of reliability information depends on the market context in which it exists. It is not in scope for this TC to define specifications for markets or for pricing models, but the TC has coordinated with others to ensure that commonly used market and pricing models are supported.

While this specification uses Web Services to describe the services, no requirement or expectation of specific messaging implementation is assumed.

TC Description:

All work of the OASIS Energy Interoperation Technical Committee (TC) is publicly visible through the TCs home page at http://www.oasis-open.org/committees/energyinterop, including all correspondence and prior drafts.

The committee includes members representing Independent System Operators and Regional Transmission Operators as well as the ISO/RTO Council, Utilities, Lawrence Berkeley Laboratories, building automation standards, market communication, schedule communication, electronic commerce (B2B) and software architecture experts and more.

The work of this committee is built in part on contributions of Requirements for Demand Response PAP09 (NAESB), OpenADR 1.0 (LBL), and business information requirements (IRC) as well as substantial contributions from members of the OpenADR Alliance.

The specification names three profiles, OpenADR 2.0, Price Distribution, and Transactive Energy, which call out subsets of the specification for particular purposes.

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

PDF (Authoritative):
http://docs.oasis-open.org/energyinterop/ei/v1.0/cs01/energyinterop-v1.0-cs01.pdf

HTML:
http://docs.oasis-open.org/energyinterop/ei/v1.0/cs01/energyinterop-v1.0-cs01.html

Editable source:
http://docs.oasis-open.org/energyinterop/ei/v1.0/cs01/energyinterop-v1.0-cs01.doc

XML schemas:
http://docs.oasis-open.org/energyinterop/ei/v1.0/cs01/xsd/

WSDL files:
http://docs.oasis-open.org/energyinterop/ei/v1.0/cs01/wsdl/

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/energyinterop/ei/v1.0/cs01/energyinterop-v1.0-cs01.zip

Members of the OASIS Energy Interoperation TC [1] 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 Energy Interoperation TC
http://www.oasis-open.org/committees/energyinterop/

[2] Public review
15-day public review, 17 November 2011: http://lists.oasis-open.org/archives/tc-announce/201111/msg00005.html
15-day public review, 10 August 2011: http://lists.oasis-open.org/archives/tc-announce/201108/msg00005.html
30-day public review, 27 November 2010: http://lists.oasis-open.org/archives/tc-announce/201011/msg00014.html

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

OASIS Members,

We are pleased to announce the approval of an OASIS Committee Specification (CS) by the members of the Energy Market Information Exchange (eMIX) TC:

Energy Market Information Exchange (EMIX) Version 1.0
Committee Specification 01
15 November 2011

Overview:
This specification defines an information model and XML vocabulary for the interoperable and standard exchange of prices and product definitions in transactive energy markets:

* Price information
* Bid information
* Time for use or availability
* Units and quantity to be traded
* Characteristics of what is traded

This specification is one of three related OASIS technical works in progress. For a graphical view of the relationships, see http://collaborate.nist.gov/twiki-sggrid/bin/view/SmartGrid/EMIXissuesPage on the NIST Smart Grid collaborative site.

(a) Web Services Calendar 1.0 (WS-Calendar Technical Committee page is http://www.oasis-open.org/committees/ws-calendar) is the common XML vocabulary for expressing schedules. EMIX uses this vocabulary to express energy schedules and prices; implementers and other standards are also using WS-Calendar. WS-Calendar has just started its third Public Review.

(b) Energy Market Information Exchange 1.0 (EMIX Technical Committee page is http://www.oasis-open.org/committees/emix) is the TC that has approved this public review. EMIX is the common XML vocabulary for expressing market information including tenders, market transactions, prices and product definitions for implementers and other standards. EMIX uses the WS-Calendar vocabulary to express schedule information, and the EMIX vocabulary is used by Energy Interoperation and other standards and implementations.

(c) Energy Interoperation 1.0 (Energy Interoperation Technical Committee page is http://www.oasis-open.org/committees/energyinterop) is the common XML vocabulary for expressing curtailment events, price communication, as well as Web services definitions for interactions using the information payloads. The Energy Interoperation TC is planning its second Public Review in July 2011.

Please refer to line numbers in the PDF version of the specification when providing comments.

TC Description:
The OASIS Energy Market Information Exchange (eMIX) TC [1] was chartered to define standards for exchanging energy characteristics, availability, and schedules to support the free and effective exchange of information. Better communication of actionable energy prices will help enable and expand efficient markets that satisfy the growing demand for lower-carbon, lower-energy buildings, net zero-energy systems, and supply-demand integration that take advantage of dynamic pricing. The TC has addressed requirements consolidated by NAESB and the Smart Grid Interoperability Panel’s Priority Action Plan 03 Working Group.

Direct participants have included representatives of Southern California Edison, the ISO-RTO Council, California ISO, Midwest ISO, New York ISO, Lawrence Berkeley National Laboratory, Enernex, UISOL, members of the UCAIug OpenADR Task Force, the OpenADR Alliance, and representatives of the National Institute of Science and Technology, Schneider Electric, Siemens AG, EPRI, OATi, The Open Geospatial Consortium, LonMark International, Lockheed Martin, EnerNOC, Trane, CPower, Microsoft, JPMorganChase, TIBCO, University of North Carolina, Alstom Power, and experts in energy markets and in cross-domain integration and information modeling.

This work is closely related to OASIS WS-Calendar 1.0 and OASIS Energy Interoperation 1.0.

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

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

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

Editable Source:
http://docs.oasis-open.org/emix/emix/v1.0/cs01/emix-v1.0-cs01.doc

XML schemas:
http://docs.oasis-open.org/emix/emix/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/emix/emix/v1.0/cs01/emix-v1.0-cs01.zip

Members of the OASIS Energy Market Information Exchange (eMIX) TC [1] 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 CS is now available online in the OASIS Library as referenced above.

Our congratulations to the TC on achieving this milestone.

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

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

[2] Public review
15-day public review, 05 October 2011: http://lists.oasis-open.org/archives/emix/201110/msg00003.html
15-day public review, 08 July 2011: http://lists.oasis-open.org/archives/tc-announce/201107/msg00002.html
15-day public review, 11 May 2011: http://lists.oasis-open.org/archives/tc-announce/201105/msg00000.html
30-day public review, 17 November 2010: http://lists.oasis-open.org/archives/members/201011/msg00005.html

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

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

SAML Version 2.0 Errata 05
Committee Specification Draft 01 / Public Review Draft 01
21 February 2012

Specification Overview:
This document lists approved errata to the SAML V2.0 OASIS Standard.

TC Description :
The Security Services TC works on ongoing maintenance of the SAML V2.0 standard and a variety of extensions and profiles to facilitate its deployability.

Public Review Period:
The public review starts 20 March 2012 and ends 4 April 2012.

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

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

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

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

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

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/security/saml/v2.0/errata05/csprd01/saml-v2.0-errata05-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 these public reviews of SAML Version 2.0 Errata 05 Committee Specification Draft, 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/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/who/intellectualproperty.php#s10.2.3
RF on Limited Terms

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

Emergency Data Exchange Language (EDXL) Common Alerting Protocol (CAP) v1.2 Australia (AU) Profile Version 1.0
Committee Specification Draft 03 / Public Review Draft 03
16 March 2012

Specification 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.

TC Description:
The Emergency Data Exchange Language (EDXL) is a broad initiative to create an integrated framework for a wide range of emergency data exchange standards to include the Common Alerting Protocol (EDXL-CAP), Distribution Element (EDXL-DE), Hospital AVailability Exchange (EDXL-HAVE), Resource Message (EDXL-RM), Reference Information Model (EDXL-RIM), Situation Reporting (EDXL-SitRep), and Tracking Emergency Patients (EDXL-TEP).

Public Review Period:
The public review starts 20 March 2012 and ends 4 April 2012. The specification was previously submitted for public review on 5 March 2012 [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 ZIP file 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/45486/edxl-cap-v1.2-au-profile-v1.0-csprd03.zip

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

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

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/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) Common Alerting Protocol (CAP) v1.2 Australia (AU) Profile 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 Emergency Management TC
http://www.oasis-open.org/committees/emergency/

[2] Previous public reviews:
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] 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

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

Field Force Management Integration Interface Requirements Version 1.0
Committee Note Draft 02 / Public Review Draft 02
28 February 2012

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 13 March 2012 and ends 28 March 2012. The specification was previously submitted for a 15-day public review on 25 October 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.

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/45408/ffm-if-requirements-v1.0-cnprd02.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 [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 Field Force Management (FFM) TC
http://www.oasis-open.org/committees/ffm

[2] 15-day public review, 25 October 2011: http://lists.oasis-open.org/archives/tc-announce/201110/msg00014.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