The OASIS Energy Market Information Exchange (eMIX) TC members have produced an updated Committee Specification Draft (CSD) and submitted this specification for 15-day public review:

Energy Market Information Exchange (EMIX) Version 1.0
Committee Specification Draft 03 / Public Review Draft 03
23 June 2011

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

Public Review Period:

The public review starts Monday, 11 July 2011 and ends 26 July 2011. The specification was previously submitted for a 15-day public review on 11 May 2011 [2]. This 15-day review is limited in scope to changes made from the previous review of 11 May 2011.

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:

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

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

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

XML Schemas:
http://docs.oasis-open.org/emix/emix/v1.0/csprd03/xsd/
http://docs.oasis-open.org/emix/emix/v1.0/csprd03/xsd/emix-v1.0-csprd03-schemas.zip

ZIP distribution files (complete):
http://docs.oasis-open.org/emix/emix/v1.0/csprd03/emix-v1.0-csprd03.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 ‘Energy Market Information Exchange (EMIX) Version 1.0 Committee Specification Draft 03’, 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 Energy Market Information Exchange (eMIX) TC
http://www.oasis-open.org/committees/emix/

[2] Previous public review announcement (11 May 2011)
http://lists.oasis-open.org/archives/tc-announce/201105/msg00000.html

[3] Diff file
http://docs.oasis-open.org/emix/emix/v1.0/csprd03/emix-v1.0-csprd03-diff.pdf

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

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

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 2.0 Session Token Profile Version 1.0
Committee Specification Draft 02 / Public Review Draft 02
13 May 2011

Specification Overview:

Web Servers and Application Servers generally maintain security state information for currently active users, particularly once some type of authentication has occurred. This specification defines a format for communicating such security session state based on the OASIS SAML Assertion. It also specifies two different mechanisms for communicating this information between servers via a standard Web browser.

TC Description:

The Security Services TC is currently developing a number of specification which build on the SAML 2.0 OASIS Standard and specify its use in a variety of contexts.

Public Review Period:

The 15-day public review starts Monday, 11 July 2011 and ends Tuesday, 26 July 2011. The specification was previously submitted for a 30-day public review on 01 April 2011 [2]. This 15-day review is limited in scope to changes made from the previous review.

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/Post2.0/saml-session-token/v1.0/csprd02/saml-session-token-v1.0-csprd02.odt

PDF:
http://docs.oasis-open.org/security/saml/Post2.0/saml-session-token/v1.0/csprd02/saml-session-token-v1.0-csprd02.pdf:


HTML:

http://docs.oasis-open.org/security/saml/Post2.0/saml-session-token/v1.0/csprd02/saml-session-token-v1.0-csprd02.html

XML Schema:

http://docs.oasis-open.org/security/saml/Post2.0/saml-session-token/v1.0/csprd02/xsd/saml-session-token-v1.0-metadata.xsd

ZIP distribution package:

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-session-token/v1.0/csprd02/saml-session-token-v1.0-csprd02.zip

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

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

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/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 2.0 Session Token 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 Security Services (SAML) TC

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

[2] Previous public review (01 April 2011 through 01 May 2011)

http://lists.oasis-open.org/archives/tc-announce/201104/msg00000.html

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

[4] http://www.oasis-open.org/committees/ws-calendar/ipr.php
http://www.oasis-open.org/who/intellectualproperty.php#s10.2.2

RF on RAND

The OASIS Service Component Architecture / J (SCA-J) TC [1] members have produced a Committee Specification Draft (CSD) and submitted it for 30-day public review:

Service Component Architecture Spring Component Implementation Specification Version 1.1
Committee Specification Draft 01 / Public Review Draft 01
23 May 2011

Specification Overview:
The SCA Spring component implementation specification specifies how the Spring Framework [SPRING] can be used with SCA. This specification extends the SCA Assembly Model by defining how a Spring Framework application context provides an implementation of an SCA component, including its various attributes such as services, references, and properties and how that application context is used in SCA as a component implementation type. The goals of this specification are:

– Coarse-grained integration: The integration with Spring is at the SCA Component level, where a Spring application context provides a component implementation, exposing services and using references via SCA. This means that a Spring application context defines the internal structure of an implementation.

– Start from SCA Component Type: Use of Spring Framework to implement any SCA Component that uses WSDL or Java interfaces to define services, possibly with some SCA specific extensions.

– Start from Spring context: Generation of an SCA Component from any Spring application context and use that component within an SCA assembly.

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 tomorrow, 29 June 2011 and ends 29 July 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 prose specification document and related files are available here:

PDF (Authoritative):
http://docs.oasis-open.org/opencsa/sca-j/sca-springci-spec/v1.1/csprd01/sca-springci-spec-v1.1-csprd01.pdf

HTML:
http://docs.oasis-open.org/opencsa/sca-j/sca-springci-spec/v1.1/csprd01/sca-springci-spec-v1.1-csprd01.html

Editable Source:
http://docs.oasis-open.org/opencsa/sca-j/sca-springci-spec/v1.1/csprd01/sca-springci-spec-v1.1-csprd01.doc

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/opencsa/sca-j/sca-springci-spec/v1.1/csprd01/sca-springci-spec-v1.1-csprd01.zip

Additional information about the specification and the OASIS 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 Spring Component Implementation Specification Version 1.1, 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 Service Component Architecture / J (SCA-J) TC
http://www.oasis-open.org/committees/sca-j/

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

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

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

WS-Calendar Version 1.0
Committee Specification Draft 04 / Public Review Draft 03
17 June 2011

Specification Overview:
The WS-Calendar specification adapts the existing specifications for calendaring and applies them to a new specification for how schedule and event information is passed between and within services. The standard adopts the semantics and vocabulary of iCalendar for application to the completion of web service contracts. WS Calendar builds on work done and ongoing in The Calendaring and Scheduling Consortium (CalConnect), which works to increase interoperation between calendaring systems, and the Internet Engineering Task Force (IETF).

The specification describes how to specify a sequence of services, how to schedule them, and how to invoke them. The specification was developed to support use cases in smart grids and smart energy, but it supports any sort of coordinated activities between domains. The committee explicitly considered coordination between energy coordination, enterprise systems, building systems, and financial markets.

The WS-Calendar specification also defines a conforming model for inheritance to reduce duplication of expression when similar services are requested in a recurring schedule.

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 15-day public review starts tomorrow, 29 June 2011 and ends 14 July 2011. The specification was previously submitted for a 15-day public review on 09 April 2011 [2]. This 15-day review is limited in scope to changes made from the previous review. Note that since the last review, numerous minor edits have applied across the document, and numerous things that were unclear have been made clearer. Of more substance, the REST and SOAP communications services were removed from the specification as they were not ready at this time. The TC work plan is to bring them back in as part of a later version of the specification

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:

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

Editable source:
http://docs.oasis-open.org/ws-calendar/ws-calendar-spec/v1.0/csprd03/ws-calendar-spec-v1.0-csprd03.doc

HTML:
http://docs.oasis-open.org/ws-calendar/ws-calendar-spec/v1.0/csprd03/ws-calendar-spec-v1.0-csprd03.html

XML Schemas:
http://docs.oasis-open.org/ws-calendar/ws-calendar-spec/v1.0/csprd03/xsd/
http://docs.oasis-open.org/ws-calendar/ws-calendar-spec/v1.0/csprd03/xsd/ws-calendar-spec-v1.0-csprd03-schemas.zip

ZIP distribution package:
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-spec/v1.0/csprd03/ws-calendar-spec-v1.0-csprd03.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 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 Web Services Calendar (WS-Calendar) TC
http://www.oasis-open.org/committees/ws-calendar/

[2] Previous public review (09 April 2011 through 24 April 2011)
http://lists.oasis-open.org/archives/members/201104/msg00005.html

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

[4] 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 OpenDocument Version 1.2 specification produced by
the OASIS Open Document Format for Office Applications
(OpenDocument) Technical Committee [1] is now entering
60-day COS public review in preparation for member
ballot to consider approval as an OASIS Standard:

Open Document Format for Office Applications (OpenDocument) Version 1.2
Candidate OASIS Standard (COS) 01
10 May 2011

In addition to the prose Overview document, the
specification is comprised of the following parts:

OpenDocument v1.2 Part 1: OpenDocument Schema
OpenDocument v1.2 Part 2: Recalculated Formula (OpenFormula) Format
OpenDocument v1.2 Part 3: Packages
OpenDocument v1.2 Relax NG Schema
OpenDocument v1.2 Manifest Schema
OpenDocument v1.2 Digital Signature Schema
OpenDocument v1.2 Metadata Manifest Ontology
OpenDocument v1.2 Package Metadata Manifest Ontology
.
Members of the OpenDocument TC have approved a Special
Majority ballot to advance OpenDocument v1.2 Committee
Specification (CS) to Candidate OASIS Standard (COS) level,
and have met all the requirements of the TC process for
a COS Submission [2]. The declarations include
certification that all schemas and XML instances are
well formed/valid; statements of use; accounts of
previous public reviews; disposition logs; etc. Details
of the submission request are available online for public
inspection [3].

Specification Summary

Open Document Format for Office Applications (OpenDocument)
Version 1.2 specifies the characteristics of an XML-based
application-independent and platform-independent digital
document file format, as well as the characteristics of
software applications which read, write and process such
documents. This standard is applicable to document
authoring, editing, viewing, exchange and archiving,
including text documents, spreadsheets, presentation
graphics, drawings, charts and similar documents commonly
used by personal productivity software applications.

OASIS has two other Technical Committees, the ODF Adoption
TC and the ODF Interoperability and Conformance TC which
do work that compliments the work of the OpenDocument TC.
The OpenDocument TC has liaisons to these other committees.

ISO/IEC JTC1 approved OASIS OpenDocument v1.0 under their
Publically Available Specification (PAS) process as ISO/IEC
26300:2006, and is in the process of approving OASIS
OpenDocument v1.1. It is expected that the OpenDocument
TC will ask OASIS to submit OASIS OpenDocument v1.2 to them
under PAS rules for transposition into an International
Standard. There is an OASIS and an OASIS OpenDocument TC
liaison with JTC1/SC34, the committee that maintains
ISO/IEC 26300. Maintenance is done under an agreement
between OASIS and ISO/IEC JTC1 that requires that the ISO
version remains ‘technically equivalent’ to the OASIS
version.

The OpenDocument Technical Committee was chartered to
create an open, XML-based file format specification for
office applications.

Public Review Period

The 60-day public review starts today, 23 June 2011 and
ends 22 August 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 prose specification document and related files are available here:

Editable Source:
Core: http://docs.oasis-open.org/office/v1.2/cos01/OpenDocument-v1.2-cos01.odt
Part 1: http://docs.oasis-open.org/office/v1.2/cos01/OpenDocument-v1.2-cos01-part1.odt
Part 2: http://docs.oasis-open.org/office/v1.2/cos01/OpenDocument-v1.2-cos01-part2.odt
Part 3: http://docs.oasis-open.org/office/v1.2/cos01/OpenDocument-v1.2-cos01-part3.odt

HTML:
Core: http://docs.oasis-open.org/office/v1.2/cos01/OpenDocument-v1.2-cos01.html
Part 1: http://docs.oasis-open.org/office/v1.2/cos01/OpenDocument-v1.2-cos01-part1.html
Part 2: http://docs.oasis-open.org/office/v1.2/cos01/OpenDocument-v1.2-cos01-part2.html
Part 3: http://docs.oasis-open.org/office/v1.2/cos01/OpenDocument-v1.2-cos01-part3.html

PDF:
Core: http://docs.oasis-open.org/office/v1.2/cos01/OpenDocument-v1.2-cos01.pdf
Part 1: http://docs.oasis-open.org/office/v1.2/cos01/OpenDocument-v1.2-cos01-part1.pdf
Part 2: http://docs.oasis-open.org/office/v1.2/cos01/OpenDocument-v1.2-cos01-part2.pdf
Part 3: http://docs.oasis-open.org/office/v1.2/cos01/OpenDocument-v1.2-cos01-part3.pdf

RNG schema and OWL files:
http://docs.oasis-open.org/office/v1.2/cos01/OpenDocument-v1.2-cos01-dsig-schema.rng
http://docs.oasis-open.org/office/v1.2/cos01/OpenDocument-v1.2-cos01-manifest-schema.rng
http://docs.oasis-open.org/office/v1.2/cos01/OpenDocument-v1.2-cos01-schema.rng
http://docs.oasis-open.org/office/v1.2/cos01/OpenDocument-v1.2-cos01-metadata.owl
http://docs.oasis-open.org/office/v1.2/cos01/OpenDocument-v1.2-cos01-package-metadata.owl

Distribution ZIP files
Entire specification:
http://docs.oasis-open.org/office/v1.2/cos01/OpenDocument-v1.2-cos01.zip
Schema files:
http://docs.oasis-open.org/office/v1.2/cos01/OpenDocument-v1.2-cos01-schemas.zip

Other specification artifacts:
http://docs.oasis-open.org/office/v1.2/cos01/

Additional information about the specification and the OASIS
Open Document Format for Office Applications (OpenDocument)
Technical Committee may be found at the TC’s public home page:
http://www.oasis-open.org/committees/office/

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:

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

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/office-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 ‘OpenDocument Version 1.2
(COS)’, 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 Open Document Format for Office Applications (OpenDocument)
Technical Committee
http://www.oasis-open.org/committees/office/

[2] Candidate OASIS Standard and OS approval
http://www.oasis-open.org/policies-guidelines/tc-process-2008-06-19#OASISstandard

[3] COS submission request
http://www.oasis-open.org/committees/download.php/41827/odf12-submission.odt

[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

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

OASIS ebXML RegRep Version 4.0
Committee Specification Draft 02 / Public Review Draft 01
12 May 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 public review starts today, 15 June 2011 and ends 15 July 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 prose specification document and related files are available here:

Editable Source (Authoritative):
Part 0: http://docs.oasis-open.org/regrep/regrep-core/v4.0/csprd01/regrep-core-overview-v4.0-csprd01.odt
Part 1: http://docs.oasis-open.org/regrep/regrep-core/v4.0/csprd01/regrep-core-rim-v4.0-csprd01.odt
Part 2: http://docs.oasis-open.org/regrep/regrep-core/v4.0/csprd01/regrep-core-rs-v4.0-csprd01.odt

HTML:
Part 0: http://docs.oasis-open.org/regrep/regrep-core/v4.0/csprd01/regrep-core-overview-v4.0-csprd01.html
Part 1: http://docs.oasis-open.org/regrep/regrep-core/v4.0/csprd01/regrep-core-rim-v4.0-csprd01.html
Part 2: http://docs.oasis-open.org/regrep/regrep-core/v4.0/csprd01/regrep-core-rs-v4.0-csprd01.html

PDF:
Part 0: http://docs.oasis-open.org/regrep/regrep-core/v4.0/csprd01/regrep-core-overview-v4.0-csprd01.pdf
Part 1: http://docs.oasis-open.org/regrep/regrep-core/v4.0/csprd01/regrep-core-rim-v4.0-csprd01.pdf
Part 2: http://docs.oasis-open.org/regrep/regrep-core/v4.0/csprd01/regrep-core-rs-v4.0-csprd01.pdf

XML schemas and WSDL files:
http://docs.oasis-open.org/regrep/regrep-core/v4.0/csprd01/xsd/
http://docs.oasis-open.org/regrep/regrep-core/v4.0/csprd01/wsdl/
http://docs.oasis-open.org/regrep/regrep-core/v4.0/csprd01/xml/

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/regrep/regrep-core/v4.0/csprd01/regrep-core-v4.0-csprd01.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 [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 ebXML Registry TC
http://www.oasis-open.org/committees/regrep

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

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

The Content Management Interoperability Services TC [1] members have produced a Committee Specification Draft (CSD) and submitted it for 15-day public review:

Content Management Interoperability Services (CMIS) Version 1.0 – Errata 1
Committee Specification Draft 01 / Public Review Draft 01
11 Mar 2011

Specification Overview:

This is an Errata for CMIS 1.0. It contains a list of non-substantive changes to the CMIS 1.0 specification.

Public Review Period:
The public review starts today, 08 June 2011 and ends 23 June 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 prose specification document and related files are available here:

Editable Source (Authoritative):
http://docs.oasis-open.org/cmis/CMIS/v1.0/errata-01/csprd01/cmis-spec-v1.0-errata-01-csprd01.doc

HTML:
http://docs.oasis-open.org/cmis/CMIS/v1.0/errata-01/csprd01/cmis-spec-v1.0-errata-01-csprd01.html

PDF:
http://docs.oasis-open.org/cmis/CMIS/v1.0/errata-01/csprd01/cmis-spec-v1.0-errata-01-csprd01.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/cmis/CMIS/v1.0/errata-01/csprd01/cmis-spec-v1.0-errata-01-csprd01.zip

Additional information about the specification and the Content Management Interoperability Services 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/form.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 1 , 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.

—————-

Chet Ensign
Director of Standards Development and TC Administration
OASIS: Advancing open standards for the information society
http://www.oasis-open.org

Primary: +1 973-378-3472
Mobile: +1 201-341-1393

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

[1] OASIS Content Management Interoperability Services TC
http://www.oasis-open.org/committees/cmis/

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

[3] http://www.oasis-open.org/committees/ebxml-msg/ipr.php
http://www.oasis-open.org/who/intellectualproperty.php#s10.2.2
RF on RAND IPR Mode

The OASIS LegalXML Electronic Court Filing TC [1] members have produced a Committee Specification Draft (CSD) and submitted it for 30-day public review:

ECF 4.0 Portable Media Service Interaction Profile Version 2.0
Committee Specification Draft 01 / Public Review Draft 01

Specification Overview:

The ECF 4.0 Portable Media Service Interaction Profile defines a transmission system that supports the functional requirements of electronic filing as defined in section 5 of the LegalXML Electronic Court Filing 4.0 (ECF 4.0) specification. The Portable Media Service Interaction Profile may be used to store ECF 4.0 message transmissions to portable media in the absence of an active network between the sending and receiving MDEs.

Public Review Period:

The public review starts today, 1 June 2011 and ends 30 June 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 prose specification document and related files are available here:

Editable Source (Authoritative):

http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.0/ecf-v4.0-portablemedia-spec/v2.0/csprd01/ecf-v4.0-portablemedia-spec-v2.0-csprd01.doc

HTML:

http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.0/ecf-v4.0-portablemedia-spec/v2.0/csprd01/ecf-v4.0-portablemedia-spec-v2.0-csprd01.html

PDF:

http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.0/ecf-v4.0-portablemedia-spec/v2.0/csprd01/ecf-v4.0-portablemedia-spec-v2.0-csprd01.pdf

XML Schemas:

http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.0/ecf-v4.0-portablemedia-spec/v2.0/csprd01/xsd/ECF-4.0-PortableMediaProfile.xsd

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/legalxml-courtfiling/specs/ecf/v4.0/ecf-v4.0-portablemedia-spec/v2.0/csprd01/ecf-v4.0-portablemedia-spec-v2.0-csprd01.zip

Additional information about the specification and the OASIS LegalXML Electronic Court Filing TC may be found at the TC’s public home page located at:

http://www.oasis-open.org/committees/legalxml-courtfiling

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=legalxml-courtfiling

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/legalxml-courtfiling-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 ECF 4.0 Portable Media Service Interaction Profile Version 2.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.

—————-

Chet Ensign
Director of Standards Development and TC Administration
OASIS: Advancing open standards for the information society
http://www.oasis-open.org

Primary: +1 973-378-3472
Mobile: +1 201-341-1393

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

[1] OASIS LegalXML Electronic Court Filing TC
http://www.oasis-open.org/committees/legalxml-courtfiling/

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

[3] 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 IPR Mode

The OASIS LegalXML Electronic Court Filing TC [1] members have produced a Committee Specification Draft (CSD) and submitted it for 30-day public review:

ECF 4.0 Web Services Service Interaction Profile Version 2.0
Committee Specification Draft 01 / Public Review Draft 01

Specification Overview:

The ECF 4.0 Web Services Service Interaction Profile defines a transmission system that supports the functional requirements of electronic filing as defined in section 5 of the LegalXML Electronic Court Filing 4.0 (ECF 4.0) specification. The Web Services Service Interaction Profile may be used to transmit ECF 4.0 messages between Internet-connected systems.

Public Review Period:

The public review starts today, 1 June 2011 and ends 30 June 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 prose specification document and related files are available here:

Editable Source (Authoritative):

http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.0/ecf-v4.0-webservices-spec/v2.01/csprd01/ecf-v4.0-webservices-spec-v2.01-csprd01.doc

HTML:

http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.0/ecf-v4.0-webservices-spec/v2.01/csprd01/ecf-v4.0-webservices-spec-v2.01-csprd01.html

PDF:

http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.0/ecf-v4.0-webservices-spec/v2.01/csprd01/ecf-v4.0-webservices-spec-v2.01-csprd01.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/legalxml-courtfiling/specs/ecf/v4.0/ecf-v4.0-webservices-spec/v2.01/csprd01/ecf-v4.0-webservices-spec-v2.01-csprd01.zip

Additional information about the specification and the OASIS LegalXML Electronic Court Filing TC may be found at the TC’s public home page located at:

http://www.oasis-open.org/committees/legalxml-courtfiling

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=legalxml-courtfiling

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/legalxml-courtfiling-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 ECF 4.0 Web Services Service Interaction Profile Version 2.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.

—————-

Chet Ensign
Director of Standards Development and TC Administration
OASIS: Advancing open standards for the information society
http://www.oasis-open.org

Primary: +1 973-378-3472
Mobile: +1 201-341-1393

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

[1] OASIS LegalXML Electronic Court Filing TC
http://www.oasis-open.org/committees/legalxml-courtfiling/

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

[3] 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 IPR Mode

The OASIS Integrated Collaboration Object Model for Interoperable Collaboration Services (ICOM) TC [1] members have recently approved a Committee Specification Draft (CSD) and submitted this specification for 30-day public review:

Integrated Collaboration Object Model (ICOM) for Interoperable Collaboration Services Version 1.0
Committee Specification Draft 01 / Public Review Draft 01
16 March 2011

Specification Overview:

The Integrated Collaboration Object Model (ICOM) for Interoperable Collaboration Services standard defines a framework for integrating a broad range of domain models for collaboration activities in an integrated and interoperable collaboration environment. The framework is intended to enable seamless transitions across collaboration activities. For example, applications can aggregate conversation threads in email with other conversations on the same topic in instant message, over the phone or via real-time conferencing, by discussion threads in community forum, weblog or micro blog, and activity stream of participants from all channels. ICOM encompasses and improves on a range of models which are part of existing standards and technologies. 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.

Public Review Period:

The public review starts today, 19 May 2011 and ends 18 June 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 prose specification document and related files are available here:

Editable Source (Authoritative):
http://docs.oasis-open.org/icom/icom-ics/v1.0/csprd01/icom-ics-v1.0-csprd01.doc

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

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

Other specification artifacts:

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

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 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/form.php?wg_abbrev=icom

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/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 [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 Integrated Collaboration Object Model for Interoperable Collaboration Services TC
http://www.oasis-open.org/committees/icom/

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

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