OASIS and the OASIS PKCS 11 TC are pleased to announce that four PKCS #11 specifications are now available for public review and comment:
PKCS #11 Cryptographic Token Interface Base Specification Version 3.0
PKCS #11 Cryptographic Token Interface Profiles Version 3.0
PKCS #11 Cryptographic Token Interface Current Mechanisms Specification Version 3.0
PKCS #11 Cryptographic Token Interface Historical Mechanisms Specification Version 3.0

The PKCS #11 specifications define a platform-independent API to cryptographic tokens, such as hardware security modules and smart cards. The API itself is named “Cryptoki” (from “cryptographic token interface” and pronounced as “crypto-key”).

“Base Specification” defines data types, functions and other basic components of the PKCS #11 Cryptoki interface.
“Profiles” is intended for developers and architects who wish to design systems and applications that conform to the PKCS #11 Cryptographic Token Interface standard.
“Current Mechanisms” defines mechanisms that are anticipated for use with the current version of PKCS #11.
“Historical Mechanisms” defines mechanisms for PKCS #11 that are no longer in general use.

The documents and related files are available here:

*********************
PKCS #11 Cryptographic Token Interface Base Specification Version 3.0
Committee Specification Draft 01 / Public Review Draft 01
29 May 2019

Editable source (Authoritative):
https://docs.oasis-open.org/pkcs11/pkcs11-base/v3.0/csprd01/pkcs11-base-v3.0-csprd01.docx
HTML:
https://docs.oasis-open.org/pkcs11/pkcs11-base/v3.0/csprd01/pkcs11-base-v3.0-csprd01.html
PDF:
https://docs.oasis-open.org/pkcs11/pkcs11-base/v3.0/csprd01/pkcs11-base-v3.0-csprd01.pdf
*********************
PKCS #11 Cryptographic Token Interface Profiles Version 3.0
Committee Specification Draft 01 / Public Review Draft 01
29 May 2019

Editable source (Authoritative):
https://docs.oasis-open.org/pkcs11/pkcs11-profiles/v3.0/csprd01/pkcs11-profiles-v3.0-csprd01.docx
HTML:
https://docs.oasis-open.org/pkcs11/pkcs11-profiles/v3.0/csprd01/pkcs11-profiles-v3.0-csprd01.html
PDF:
https://docs.oasis-open.org/pkcs11/pkcs11-profiles/v3.0/csprd01/pkcs11-profiles-v3.0-csprd01.pdf
*********************
PKCS #11 Cryptographic Token Interface Current Mechanisms Specification Version 3.0
Committee Specification Draft 01 / Public Review Draft 01
29 May 2019

Editable source (Authoritative):
https://docs.oasis-open.org/pkcs11/pkcs11-curr/v3.0/csprd01/pkcs11-curr-v3.0-csprd01.docx
HTML:
https://docs.oasis-open.org/pkcs11/pkcs11-curr/v3.0/csprd01/pkcs11-curr-v3.0-csprd01.html
PDF:
https://docs.oasis-open.org/pkcs11/pkcs11-curr/v3.0/csprd01/pkcs11-curr-v3.0-csprd01.pdf
*********************
PKCS #11 Cryptographic Token Interface Historical Mechanisms Specification Version 3.0
Committee Specification Draft 01 / Public Review Draft 01
29 May 2019

Editable source (Authoritative):
https://docs.oasis-open.org/pkcs11/pkcs11-hist/v3.0/csprd01/pkcs11-hist-v3.0-csprd01.docx
HTML:
https://docs.oasis-open.org/pkcs11/pkcs11-hist/v3.0/csprd01/pkcs11-hist-v3.0-csprd01.html
PDF:
https://docs.oasis-open.org/pkcs11/pkcs11-hist/v3.0/csprd01/pkcs11-hist-v3.0-csprd01.pdf
*********************

For your convenience, OASIS provides a complete package of the specification document and any related files in ZIP distribution files. You can download the ZIP files at:
“Base Specification”:
https://docs.oasis-open.org/pkcs11/pkcs11-base/v3.0/csprd01/pkcs11-base-v3.0-csprd01.zip
“Profiles”:
https://docs.oasis-open.org/pkcs11/pkcs11-profiles/v3.0/csprd01/pkcs11-profiles-v3.0-csprd01.zip
“Current Mechanisms”:
https://docs.oasis-open.org/pkcs11/pkcs11-curr/v3.0/csprd01/pkcs11-curr-v3.0-csprd01.zip
“Historical Mechanisms”:
https://docs.oasis-open.org/pkcs11/pkcs11-hist/v3.0/csprd01/pkcs11-hist-v3.0-csprd01.zip

How to Provide Feedback

OASIS and the OASIS PKCS 11 TC value your feedback. We solicit input from developers, users and others, whether OASIS members or not, for the sake of improving the interoperability and quality of its technical work.

The public review starts 7 June 2019 at 00:00 UTC and ends 6 July 2019 at 23:59 UTC.

Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility which can be used by following the instructions on the TC’s “Send A Comment” page (https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=pkcs11).

Comments submitted by TC non-members for this work and for other work of this TC are publicly archived and can be viewed at:
https://lists.oasis-open.org/archives/pkcs11-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, we call your attention to the OASIS IPR Policy [1] applicable especially [2] 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 information about the specification and the PKCS11 TC can be found at the TC’s public home page:
https://www.oasis-open.org/committees/pkcs11/

========== Additional references:
[1] https://www.oasis-open.org/policies-guidelines/ipr

[2] https://www.oasis-open.org/committees/pkcs11/ipr.php
https://www.oasis-open.org/policies-guidelines/ipr#RF-on-RAND-Mode
RF on RAND Mode

OASIS and the OASIS Static Analysis Results Interchange Format (SARIF) TC are pleased to announce that Static Analysis Results Interchange Format (SARIF) Version 2.1.0 is now available for public review and comment.

Software developers use a variety of tools to assess the quality of their programs. These tools can report results on qualities such as validity, security, performance, compliance with legal requirements, etc. To form an overall picture of program quality, developers often need to aggregate the results produced by all of these tools, a task made difficult when each tool produces output in a different format.

SARIF defines a standard format for the output of static analysis tools in order to:
· Comprehensively capture the range of data produced by commonly used static analysis tools.
· Reduce the cost and complexity of aggregating the results of various analysis tools into common workflows.
· Represent analysis results for all kinds of programming artifacts, including source code and object code.

The documents and related files are available here:

Static Analysis Results Interchange Format (SARIF) Version 2.1.0
Committee Specification Draft 01 / Public Review Draft 01
27 May 2019

Editable source (Authoritative):
https://docs.oasis-open.org/sarif/sarif/v2.1.0/csprd01/sarif-v2.1.0-csprd01.docx
HTML:
https://docs.oasis-open.org/sarif/sarif/v2.1.0/csprd01/sarif-v2.1.0-csprd01.html
PDF:
https://docs.oasis-open.org/sarif/sarif/v2.1.0/csprd01/sarif-v2.1.0-csprd01.pdf
JSON schemas:
https://docs.oasis-open.org/sarif/sarif/v2.1.0/csprd01/schemas/

For your convenience, OASIS provides a complete package of the specification document and any related files in ZIP distribution files. You can download the ZIP file at:
https://docs.oasis-open.org/sarif/sarif/v2.1.0/csprd01/sarif-v2.1.0-csprd01.zip

How to Provide Feedback

OASIS and the SARIF TC value your feedback. We solicit input from developers, users and others, whether OASIS members or not, for the sake of improving the interoperability and quality of its technical work.

The public review starts 5 June 2019 at 00:00 UTC and ends 5 July 2019 at 23:59 UTC.

Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility which can be used by following the instructions on the TC’s “Send A Comment” page (https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=sarif).

Comments submitted by TC non-members for this work and for other work of this TC are publicly archived and can be viewed at:
https://lists.oasis-open.org/archives/sarif-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, we call your attention to the OASIS IPR Policy [1] applicable especially [2] 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 information about the specification and the SARIF TC can be found at the TC’s public home page:
https://www.oasis-open.org/committees/sarif/

========== Additional references:
[1] https://www.oasis-open.org/who/intellectualproperty.php

[2] https://www.oasis-open.org/committees/sarif/ipr.php
https://www.oasis-open.org/policies-guidelines/ipr#RF-on-RAND-Mode
RF on RAND Mode

OASIS and the OASIS Static Analysis Results Interchange Format (SARIF) TC [1] are pleased to announce that Static Analysis Results Interchange Format (SARIF) Version 2.0 is now available for public review and comment. This is the second public review for SARIF v2.0.

Software developers use a variety of tools to assess the quality of their programs. These tools can report results on qualities such as validity, security, performance, compliance with legal requirements, etc. To form an overall picture of program quality, developers often need to aggregate the results produced by all of these tools, a task made difficult when each tool produces output in a different format.

SARIF defines a standard format for the output of static analysis tools in order to:
· Comprehensively capture the range of data produced by commonly used static analysis tools.
· Reduce the cost and complexity of aggregating the results of various analysis tools into common workflows.
· Represent analysis results for all kinds of programming artifacts, including source code and object code.

The documents and related files are available here:

Static Analysis Results Interchange Format (SARIF) Version 2.0
Committee Specification Draft 02 / Public Review Draft 02
27 May 2019

Editable source (Authoritative):
https://docs.oasis-open.org/sarif/sarif/v2.0/csprd02/sarif-v2.0-csprd02.docx

HTML:
https://docs.oasis-open.org/sarif/sarif/v2.0/csprd02/sarif-v2.0-csprd02.html

PDF:
https://docs.oasis-open.org/sarif/sarif/v2.0/csprd02/sarif-v2.0-csprd02.pdf

JSON schemas:
https://docs.oasis-open.org/sarif/sarif/v2.0/csprd02/schemas/

For your convenience, OASIS provides a complete package of the specification document and any related files in ZIP distribution files. You can download the ZIP file at:

https://docs.oasis-open.org/sarif/sarif/v2.0/csprd02/sarif-v2.0-csprd02.zip

How to Provide Feedback

OASIS and the SARIF TC value your feedback. We solicit input from developers, users and others, whether OASIS members or not, for the sake of improving the interoperability and quality of its technical work.

The public review starts 04 June 2019 at 00:00 UTC and ends 18 June 2019 at 23:59 UTC.

This specification was previously submitted for public review [2]. This 15-day review is limited in scope to changes made from the previous review. Changes are highlighted in red-lined file included in the package [3].

Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility which can be used by following the instructions on the TC’s “Send A Comment” page (https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=sarif).

Comments submitted by TC non-members for this work and for other work of this TC are publicly archived and can be viewed at:
https://lists.oasis-open.org/archives/sarif-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, 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 information about the specification and the SARIF TC can be found at the TC’s public home page:
https://www.oasis-open.org/committees/sarif/

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

[1] OASIS Static Analysis Results Interchange Format (SARIF) TC
https://www.oasis-open.org/committees/sarif/

[2] Previous public review:
– 30-day public review, 22 June 2018:
https://lists.oasis-open.org/archives/sarif/201806/msg00083.html
– Comment resolution log:
https://docs.oasis-open.org/sarif/sarif/v2.0/csprd01/sarif-v2.0-csprd01-comment-resolution-log.txt

[3] Red-lined version (PDF):
https://docs.oasis-open.org/sarif/sarif/v2.0/csprd02/sarif-v2.0-csprd02-DIFF.pdf

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

[5] https://www.oasis-open.org/committees/sarif/ipr.php
https://www.oasis-open.org/policies-guidelines/ipr#RF-on-RAND-Mode
RF on RAND Mode

OASIS is pleased to announce that Service Metadata Publishing (SMP) Version 2.0 from the OASIS Business Document Exchange (BDXR) TC [1] has been approved as an OASIS Committee Specification.

SMP v2.0 describes a protocol for publishing service metadata within a 4-corner network. In a 4-corner network, entities are exchanging business documents through intermediary gateway services (sometimes called Access Points).

To successfully send a business document in a 4-corner network, an entity must be able to discover critical metadata about the recipient of the business document, such as types of documents the recipient is capable of receiving and methods of transport supported. The recipient makes this metadata available to other entities in the network through a Service Metadata Publisher service. This specification describes the request/response exchanges between a Service Metadata Publisher and a client wishing to discover endpoint information. A client can either be an end-user business application or a gateway/access point in the 4-corner network.

This Committee Specification is an OASIS deliverable, completed and approved by the TC and fully ready for testing and implementation.

The prose specifications and related files are available here:

Service Metadata Publishing (SMP) Version 2.0
Committee Specification 01
20 May 2019

Editable source (Authoritative):
https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs01/bdx-smp-v2.0-cs01.docx
HTML:
https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs01/bdx-smp-v2.0-cs01.html
PDF:
https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs01/bdx-smp-v2.0-cs01.pdf
XML schemas and documentation:
https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs01/xsd/
https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs01/xsdrt/
https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs01/mod/

Distribution ZIP file
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:
https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs01/bdx-smp-v2.0-cs01.zip

Members of the BDXR TC [1] approved this specification by Special Majority Vote. The specification had been released for public review as required by the TC Process [2]. The vote to approve as a Committee Specification passed [3], and the document is now available online in the OASIS Library as referenced above.

Our congratulations to the TC on achieving this milestone and our thanks to the reviewers who provided feedback on the specification drafts to help improve the quality of the work.

========== Additional references:
[1] OASIS Business Document Exchange (BDXR) TC
https://www.oasis-open.org/committees/bdxr/

[2] Public reviews:
* 30-day public review, 25 July 2018:
https://lists.oasis-open.org/archives/bdxr/201807/msg00008.html
– Comment resolution log:
https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/csprd01/bdx-smp-v2.0-csprd01-comment-resolution-log.xlsx

* 15-day public review, 12 February 2019:
https://lists.oasis-open.org/archives/bdxr/201902/msg00001.html
– Comment resolution log:
https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/csprd02/bdx-smp-v2.0-csprd02-comment-resolution-log.xlsx

[3] Approval ballot:
https://www.oasis-open.org/committees/ballot.php?id=3399

OASIS and the OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC are pleased to announce that TOSCA Simple Profile in YAML Version 1.3 is now available for public review and comment.

YAML is a human friendly data serialization standard with a syntax much easier to read and edit than XML. The TOSCA Simple Profile in YAML specifies a rendering of TOSCA which aims to provide a more accessible syntax as well as a more concise and incremental expressiveness of the TOSCA DSL (Domain Specific Language) in order to minimize the learning curve and speed the adoption of the use of TOSCA to portably describe cloud applications.

The documents and related files are available here:

TOSCA Simple Profile in YAML Version 1.3
Committee Specification Draft 01 / Public Review Draft 01
25 April 2019

PDF (Authoritative):
https://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.3/csprd01/TOSCA-Simple-Profile-YAML-v1.3-csprd01.pdf
HTML:
https://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.3/csprd01/TOSCA-Simple-Profile-YAML-v1.3-csprd01.html
Editable source:
https://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.3/csprd01/TOSCA-Simple-Profile-YAML-v1.3-csprd01.docx

For your convenience, OASIS provides a complete package of the prose document and related files in a ZIP distribution file. You can download the ZIP file here:
https://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.3/csprd01/TOSCA-Simple-Profile-YAML-v1.3-csprd01.zip

How to Provide Feedback

OASIS and the TOSCA TC value your feedback. We solicit input from developers, users and others, whether OASIS members or not, for the sake of improving the interoperability and quality of its technical work.

The public review starts 23 May 2019 at 00:00 UTC and ends 21 June 2019 at 23:59 UTC.

Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility which can be used by following the instructions on the TC’s “Send A Comment” page (https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=tosca).

Comments submitted by TC non-members for this work and for other work of this TC are publicly archived and can be viewed at:
https://lists.oasis-open.org/archives/tosca-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 “TOSCA Simple Profile in YAML Version 1.3”, we call your attention to the OASIS IPR Policy [1] applicable especially [2] 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 information about the specification and the TOSCA TC can be found at the TC’s public home page:
https://www.oasis-open.org/committees/tosca/

========== Additional references:
[1] https://www.oasis-open.org/policies-guidelines/ipr

[2] https://www.oasis-open.org/committees/tosca/ipr.php
https://www.oasis-open.org/policies-guidelines/ipr#RF-on-Limited-Mode
RF on Limited Terms Mode

OASIS is pleased to announce that Cross-Enterprise Security and Privacy Authorization (XSPA) Profile of SAML v2.0 for Healthcare Version 2.0 from the OASIS Cross-Enterprise Security and Privacy Authorization (XSPA) TC [1] has been approved as an OASIS Committee Specification.

The XSPA profile defines a set of SAML attributes and corresponding vocabularies for healthcare information exchange applications.

The core use-cases are the cross-enterprise exchange of protected data objects from a Service Provider (SP) to a Service Consumer (SC). In the scenarios, the request includes SAML attribute assertions that vouch for the identity of the requesting Principal and other attributes that are consequential in making the access control decision at the SP’s side.

In addition to the main use-cases, the attributes’ name and values can be used in some other scenarios, such as including SAML Assertions to vouch for some of SP’s organizational attributes, or carrying the identity attributes of the signer of a data object.

This Committee Specification is an OASIS deliverable, completed and approved by the TC and fully ready for testing and implementation.

The prose specifications and related files are available here:

Cross-Enterprise Security and Privacy Authorization (XSPA) Profile of SAML v2.0 for Healthcare Version 2.0
Committee Specification 01
23 April 2019

Editable source (Authoritative):
https://docs.oasis-open.org/xspa/saml-xspa/v2.0/cs01/saml-xspa-v2.0-cs01.docx
HTML:
https://docs.oasis-open.org/xspa/saml-xspa/v2.0/cs01/saml-xspa-v2.0-cs01.html
PDF:
https://docs.oasis-open.org/xspa/saml-xspa/v2.0/cs01/saml-xspa-v2.0-cs01.pdf

Distribution ZIP file
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:
https://docs.oasis-open.org/xspa/saml-xspa/v2.0/cs01/saml-xspa-v2.0-cs01.zip

Members of the XSPA TC [1] approved this specification by Special Majority Vote. The specification had been released for public review as required by the TC Process [2]. The vote to approve as a Committee Specification passed [3], and the document is now available online in the OASIS Library as referenced above.

Our congratulations to the TC on achieving this milestone and our thanks to the reviewers who provided feedback on the specification drafts to help improve the quality of the work.

========== Additional references:
[1] OASIS Cross-Enterprise Security and Privacy Authorization (XSPA) TC
https://www.oasis-open.org/committees/xspa/

[2] Public reviews:
– 30-day public review, 29 April 2014:
https://lists.oasis-open.org/archives/members/201404/msg00010.html
– Comment resolution log:
https://docs.oasis-open.org/xspa/saml-xspa/v2.0/csprd01/saml-xspa-v2.0-csprd01-comment-resolution-log.xls
– 15-day public review, 27 March 2017:
https://lists.oasis-open.org/archives/xspa/201703/msg00006.html
– Comment resolution log:
https://docs.oasis-open.org/xspa/saml-xspa/v2.0/csprd02/saml-xspa-v2.0-csprd02-comment-resolution-log.txt
– 15-day public review, 04 December 2018:
https://lists.oasis-open.org/archives/members/201812/msg00000.html
– Comment resolution log:
https://docs.oasis-open.org/xspa/saml-xspa/v2.0/csprd03/saml-xspa-v2.0-csprd03-comment-resolution-log.txt
– 15-day public review, 15 March 2019:
https://lists.oasis-open.org/archives/xspa/201903/msg00000.html
– Comment resolution log:
https://docs.oasis-open.org/xspa/saml-xspa/v2.0/csprd04/saml-xspa-v2.0-csprd04-comment-resolution-log.txt

[3] Approval ballot:
https://www.oasis-open.org/committees/ballot.php?id=3382

OASIS is pleased to announce that Electronic Court Filing Web Services Service Interaction Profile Version 5.0 from the OASIS LegalXML Electronic Court Filing TC [1] has been approved as an OASIS Committee Specification.

Electronic Court Filing v5.0 (ECF v5.0) defines a technical architecture for an electronic court filing system. ECF Web Services SIP v5.0 defines a Service Interaction Profile, as defined in Section 7 of the ECF v5.0 specification. The Web Services SIP may be used to transmit ECF v5.0 messages between Internet-connected systems.

This specification provides a web service-based system in conformance with the WS-I Basic Profile 1.1 and Basic Security Profile 1.1 for use with the ECF v5.0 specification. This version adds support for bulk filings. It improves security support for tokens, attachments, and rights management through inclusion of WS-Security 1.1 and adds supports for message splitting and assembly through inclusion of WS-Reliable Messaging 1.1.

This Committee Specification is an OASIS deliverable, completed and approved by the TC and fully ready for testing and implementation.

The prose specifications and related files are available here:

Electronic Court Filing Web Services Service Interaction Profile Version 5.0
Committee Specification 01
24 April 2019

Editable source (Authoritative):
https://docs.oasis-open.org/legalxml-courtfiling/ecf-webservices/v5.0/cs01/ecf-webservices-v5.0-cs01.docx
HTML:
https://docs.oasis-open.org/legalxml-courtfiling/ecf-webservices/v5.0/cs01/ecf-webservices-v5.0-cs01.html
PDF:
https://docs.oasis-open.org/legalxml-courtfiling/ecf-webservices/v5.0/cs01/ecf-webservices-v5.0-cs01.pdf
Red-lined changes from previous Public Review (PDF):
https://docs.oasis-open.org/legalxml-courtfiling/ecf-webservices/v5.0/cs01/ecf-webservices-v5.0-cs01-DIFF.pdf
WSDL schemas:
https://docs.oasis-open.org/legalxml-courtfiling/ecf-webservices/v5.0/cs01/schema/
XML WSDL examples:
https://docs.oasis-open.org/legalxml-courtfiling/ecf-webservices/v5.0/cs01/examples/

Distribution ZIP file
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:
https://docs.oasis-open.org/legalxml-courtfiling/ecf-webservices/v5.0/cs01/ecf-webservices-v5.0-cs01.zip

Members of the LegalXML Courtfiling TC [1] approved this specification by Special Majority Vote. The specification had been released for public review as required by the TC Process [2]. The vote to approve as a Committee Specification passed [3], and the document is now available online in the OASIS Library as referenced above.

Our congratulations to the TC on achieving this milestone and our thanks to the reviewers who provided feedback on the specification drafts to help improve the quality of the work.

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

[2] Public review:
– 30-day public review, March 2019:
https://lists.oasis-open.org/archives/legalxml-courtfiling/201903/msg00006.html
– Comment resolution log:
https://docs.oasis-open.org/legalxml-courtfiling/ecf-webservices/v5.0/csprd01/ecf-webservices-v5.0-csprd01-comment-resolution-log.xlsx

[3] Approval ballot:
https://www.oasis-open.org/committees/ballot.php?id=3383

OASIS is pleased to announce that Electronic Court Filing Version 5.0 from the OASIS LegalXML Electronic Court Filing TC [1] has been approved as an OASIS Committee Specification.

ECF defines a technical architecture and a set of components, operations and message structures for an electronic court filing system, and sets forth rules governing its implementation. Version 5.0 provides a number of enhancements including:
– Support for scheduling of court hearings using WS-Calendar
– Limited electronic service of process to process servers and registered agents
– New Document Stamp and operations support retrieval of case information required for stamping
– New Court Policy MDE to better support electronic filing systems with multiple FilingReview MDEs
– Support for cancellation of filings
– Conformance with the 4.0 version of the National Information Exchange Model (NIEM), a national standard for information sharing, new NIEM domains including Biometrics and Human Services
– Conformance with the NIEM Code Lists specification version 1.0 and the representation of all ECF code lists in Genericode format
– Conformance with the 2.2 version of the Universal Business Language (UBL)
– Better management of extensions through NIEM augmentations
– Deprecated content references (e.g. referring to related entities with common identifiers) in favor or element references (e.g. referring to related elements with structures:ref attributes) as described in Reference Rules
– Clarifications and improvements throughout the specification based on feedback from implementers of the ECF 4.0 and 4.01 specifications.

Version 5.0 does not assume that prior versions will be deprecated. However, it is not backward-compatible and applications using the ECF 3.0, 3.01 and 3.1, 4.0 and 4.01 specifications will not interoperate successfully with applications using this version.

This Committee Specification is an OASIS deliverable, completed and approved by the TC and fully ready for testing and implementation.

The prose specifications and related files are available here:

Electronic Court Filing Version 5.0
Committee Specification 01
18 April 2019

Editable source (Authoritative):
https://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.0/cs01/ecf-v5.0-cs01.docx
HTML:
https://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.0/cs01/ecf-v5.0-cs01.html
PDF:
https://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.0/cs01/ecf-v5.0-cs01.pdf
XML schemas and Genericode code lists:
https://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.0/cs01/schema/
XML example messages:
https://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.0/cs01/examples/
Model and documentation:
https://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.0/cs01/model/
UML model artifacts:
https://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.0/cs01/uml/

Distribution ZIP file
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:
https://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.0/cs01/ecf-v5.0-cs01.zip

Members of the LegalXML Courtfiling TC [1] approved this specification by Special Majority Vote. The specification had been released for public review as required by the TC Process [2]. The vote to approve as a Committee Specification passed [3], and the document is now available online in the OASIS Library as referenced above.

Our congratulations to the TC on achieving this milestone and our thanks to the reviewers who provided feedback on the specification drafts to help improve the quality of the work.

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

[2] Public reviews:
– 60-day public review, September 2017:
https://lists.oasis-open.org/archives/legalxml-courtfiling/201709/msg00018.html
– Comment resolution log:
http://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.0/csprd01/ecf-v5.0-csprd01-comment-resolution-log.xlsx
– 15-day public review, October 2018:
https://lists.oasis-open.org/archives/legalxml-courtfiling/201810/msg00014.html
– Comment resolution log:
http://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.0/csprd02/ecf-v5.0-csprd02-comment-resolution-log.xlsx
– 15-day public review, December 2018:
https://lists.oasis-open.org/archives/legalxml-courtfiling/201812/msg00007.html
– Comment resolution log:
https://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.0/csprd03/ecf-v5.0-csprd03-comment-resolution-log.xlsx
– 15-day public review, March 2019:
https://lists.oasis-open.org/archives/legalxml-courtfiling/201903/msg00007.html
– Comment resolution log:
https://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.0/csprd04/ecf-v5.0-csprd04-comment-resolution-log.xlsx

[3] Approval ballot:
https://www.oasis-open.org/committees/ballot.php?id=3381

OASIS is pleased to announce that Exchange Header Envelope (XHE) Version 1.0 from the OASIS Business Document Exchange (BDXR) TC [1] has been approved as an OASIS Committee Specification.

The Exchange Header Envelope (XHE) has been developed jointly by UN/CEFACT and OASIS as the successor to the UN/CEFACT Standard Business Document Header (SBDH) version 1.3 and the OASIS Business Document Envelope (BDE) Version 1.1.

XHE defines a business-oriented artefact either referencing (as a header) or containing (as an envelope) a payload of one or more business documents or other artefacts with supplemental semantic information about the collection of payloads as a whole. An exchange header envelope describes contextual information important to the sender and receiver about the payloads, without having to modify the payloads in any fashion. This vocabulary is modeled using the UN/CEFACT Core Component Technical Specification Version 2.01.

This Committee Specification is an OASIS deliverable, completed and approved by the TC and fully ready for testing and implementation.

The prose specifications and related files are available here:

Exchange Header Envelope (XHE) Version 1.0
Committee Specification 01
21 March 2019

Editable source (Authoritative):
https://docs.oasis-open.org/bdxr/xhe/v1.0/cs01/xhe-v1.0-cs01.xml
HTML:
https://docs.oasis-open.org/bdxr/xhe/v1.0/cs01/xhe-v1.0-cs01-oasis.html
PDF:
https://docs.oasis-open.org/bdxr/xhe/v1.0/cs01/xhe-v1.0-cs01-oasis.pdf

Distribution ZIP file
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:
https://docs.oasis-open.org/bdxr/xhe/v1.0/cs01/xhe-v1.0-cs01.zip

Members of the BDXR TC [1] approved this specification by Special Majority Vote. The specification had been released for public review as required by the TC Process [2]. The vote to approve as a Committee Specification passed [3], and the document is now available online in the OASIS Library as referenced above.

Our congratulations to the TC on achieving this milestone and our thanks to the reviewers who provided feedback on the specification drafts to help improve the quality of the work.

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

[1] OASIS Business Document Exchange (BDXR) TC
https://www.oasis-open.org/committees/bdxr/

[2] Public reviews:
* 30-day public review, 27 April 2018:
https://lists.oasis-open.org/archives/bdxr/201804/msg00015.html
https://lists.oasis-open.org/archives/bdxr/201804/msg00018.html
– Comment resolution log:
https://docs.oasis-open.org/bdxr/xhe/v1.0/csprd01/xhe-v1.0-csprd01-comment-resolution-log.xlsx

[3] Approval ballot:
https://www.oasis-open.org/committees/ballot.php?id=3345

OASIS and the OASIS Key Management Interoperability Protocol (KMIP) TC are pleased to announce that two KMIP specifications are now available for public review and comment.

Key Management Interoperability Protocol Specification Version 2.0
Committee Specification Draft 02 / Public Review Draft 01
11 April 2019

Key Management Interoperability Protocol Profiles Version 2.0
Committee Specification Draft 02 / Public Review Draft 01
11 April 2019

What is KMIP and why is it important?

The Key Management Interoperability Protocol (KMIP) is a single, comprehensive protocol for communication between clients that request any of a wide range of encryption keys and servers that store and manage those keys. By replacing redundant, incompatible key management protocols, KMIP provides better data security while at the same time reducing expenditures on multiple products.

The KMIP Specification v2.0 is intended for developers and architects who wish to design systems and applications that interoperate using the Key Management Interoperability Protocol Specification.

KMIP Profiles v2.0 specifies conformance clauses that define the use of objects, attributes, operations, message elements and authentication methods within specific contexts of KMIP server and client interaction.

The documents and related files are available here:

Key Management Interoperability Protocol Specification Version 2.0
Editable source (Authoritative):
https://docs.oasis-open.org/kmip/kmip-spec/v2.0/csprd01/kmip-spec-v2.0-csprd01.docx
HTML:
https://docs.oasis-open.org/kmip/kmip-spec/v2.0/csprd01/kmip-spec-v2.0-csprd01.html
PDF:
https://docs.oasis-open.org/kmip/kmip-spec/v2.0/csprd01/kmip-spec-v2.0-csprd01.pdf
For your convenience, OASIS provides a complete package of the prose document and related files in a ZIP distribution file. You can download the ZIP file here:
https://docs.oasis-open.org/kmip/kmip-spec/v2.0/csprd01/kmip-spec-v2.0-csprd01.zip

Key Management Interoperability Protocol Profiles Version 2.0
Editable source (Authoritative):
https://docs.oasis-open.org/kmip/kmip-profiles/v2.0/csprd01/kmip-profiles-v2.0-csprd01.docx
HTML:
https://docs.oasis-open.org/kmip/kmip-profiles/v2.0/csprd01/kmip-profiles-v2.0-csprd01.html
PDF:
https://docs.oasis-open.org/kmip/kmip-profiles/v2.0/csprd01/kmip-profiles-v2.0-csprd01.pdf
Test cases:
https://docs.oasis-open.org/kmip/kmip-profiles/v2.0/csprd01/test-cases/
ZIP file:
https://docs.oasis-open.org/kmip/kmip-profiles/v2.0/csprd01/kmip-profiles-v2.0-csprd01.zip

How to Provide Feedback

OASIS and the KMIP TC value your feedback. We solicit input from developers, users and others, whether OASIS members or not, for the sake of improving the interoperability and quality of its technical work.

The public review starts 26 April 2019 at 00:00 UTC and ends 25 May 2019 at 23:59 UTC.

Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility which can be used by following the instructions on the TC’s “Send A Comment” page (https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=kmip)

Comments submitted by TC non-members for this work and for other work of this TC are publicly archived and can be viewed at:
https://lists.oasis-open.org/archives/kmip-comment/

All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the TC members. In connection with this public review, we call your attention to the OASIS IPR Policy [1] applicable especially [2] 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 specifications, so that notice of them may be posted to the notice page for this TC’s work.

Additional information about the specifications and the KMIP TC can be found at the TC’s public home page:
https://www.oasis-open.org/committees/kmip/

========== Additional references:
[1] https://www.oasis-open.org/policies-guidelines/ipr
[2] http://www.oasis-open.org/committees/kmip/ipr.php
https://www.oasis-open.org/policies-guidelines/ipr#RF-on-RAND-Mode
RF on RAND Mode