OASIS to host Borderless Cyber Asia Conference on cyber threat intelligence & information sharing

1 November 2016 – Cyber security threats know no boundaries and only through effective information sharing can we improve our state of preparedness, and response to the ever increasing volume and sophistication of attacks. OASIS, the non profit open standards consortium is pioneering collaboration between security professionals in Government, corporations and academic organizations by fostering information sharing techniques, setting standards and providing tools to encourage best practice. For Laurent Liscia, CEO and Executive Director of OASIS the mission is simple, he has observed the security industry evolve from one where the embarrassment of having to reveal a security incident prevented companies from coming together, to one where global communities share threat detection information. “If you have global communities sharing information with one another, you’re abolishing borders, just like Europe has done. Those communities all function according to a standard philosophy: the more you share information about threats, the better you will be prepared as a nation, company, group, alliance, and interconnected world.” To drive this collaboration OASIS created ‘Borderless Cyber’ and following a successful conference in Europe now bring the event to Asia during 1-2 November 2016, with co-host Keio University in Tokyo, Japan. The conference will feature leaders from around the world who will share their multidimensional approaches and how their national strategies are adapting to change. Also, through successful implementations, working cyber security strategies, tools and practices will be demonstrated. For an organization to improve its state of preparedness, the chief information security officer (CISO) and IT security managers need to keep updated with the latest threat information. Therefore Borderless Cyber Asia will address both strategy and implementation topics including: • Dealing with cyber threats on a country level • Center of Excellence: Global cutting-edge approaches in the defense of cyber intelligence threats • Emerging trends in critical infrastructure protection • Privacy laws and transnational agreements • Cyber security solutions, tools and best practices • Fostering information sharing through non-profit international forums • Navigating the global threat landscape from an Enterprise perspective • Automating Cyber Threat Intelligence with STIX, TAXII, CybOX Fujitsu.Ltd.is delighted to be attending Borderless Cyber Asia and will be giving a PoC demonstration at their booth to show the concept of CTI-Driven Platform for Proactive Defense. “CTI is five Ws and one H (What, Who, When, Where, Why, and How) of cyber attacks and response information in a machine-understandable format. Fujitsu has developed a cyber threat intelligence (CTI) management system, CTIM, which effectively leverages CTI in cyber attack analyses and responses. We will be demonstrating this at Borderless Cyber Asia and hope to show this concept to attendees“. Hirohito Aoki, VP, Deputy Head of Defense Systems Unit, Fujitsu.Ltd. Speakers include: • Yasuhiko Taniwaki, Ministry of Internal Affairs and Communications • Jason P. Hyland, U.S. Embassy in Japan • Masao Horibe, The Personal Information Protection Commission • Ikuo Misumi, NISC • David Ellis, British Embassy Tokyo • Jun Murai, Keio University • Hiroshi Takechi, International Telecommunication Union (ITU) • Barbara Grewe, The Mitre Corporation • Daniel Dobrygowski, World Economic Forum • Richard Struse, U.S. Department of Homeland Security • and many more. Date: 1-2 November 2016 Venue: Keio University Location: Tokyo, Japan OASIS would like to thank esteemed sponsor – Fujitsu, partner sponsor – Hitachi, and event sponsors IBM Security, Darktrace, New Context, NEC and Surevine for their support. About OASIS OASIS (Organization for the Advancement of Structured Information Standards) is a not-for-profit, international consortium that drives the development, convergence and adoption of open standards for the global information society. OASIS promotes industry consensus and produces worldwide standards for cloud computing, security, business transactions, electronic publishing, Smart Grid, and other applications. OASIS open standards offer the potential to lower cost, stimulate innovation, grow global markets, and protect the right of free choice of technology. OASIS members broadly represent the marketplace of public and private sector technology leaders, users and influencers. The consortium has more than 5,000 participants representing over 600 organizations and individual members in 65 countries. http://www.oasis-open.org ###

#EDXL Situation Reporting (EDXL-SitRep) v1.0 published by Emergency Management TC

OASIS is pleased to announce the approval and publication of a new Committee Specification by the members of the TC:

Emergency Data Exchange Language Situation Reporting (EDXL-SitRep) Version 1.0
Committee Specification 02
06 October 2016

What is EDXL SitRep and why is it important?

The XML-based Emergency Data Exchange Language (EDXL) Situation Reporting specification describes a set of standard reports and elements that can be used for data sharing among emergency information systems, and that provide incident information for situation awareness on which incident command can base decisions.

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

TC Description:

The Emergency Management TC creates vendor-neutral and platform agnostic standards for organizations and agencies to more easily exchange emergency information.

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 support operations, logistics, planning and finance.

This draft specification joins the other EM-TC standard efforts including:

– EDXL Common Alerting Protocol (EDXL-CAP)
– EDXL Distribution Element (EDXL-DE)
– EDXL Hospital AVailability Exchange (EDXL-HAVE)
– EDXL Resource Messaging (EDXL-RM)
– EDXL Reference Information Model (EDXL-RIM)
– EDXL Situation Reporting (EDXL-SitRep)
– EDXL Tracking Emergency Patients (EDXL-TEP)

URIs:
The prose specifications and related files are available here:

Editable source (Authoritative):
http://docs.oasis-open.org/emergency/edxl-sitrep/v1.0/cs02/edxl-sitrep-v1.0-cs02.odt

HTML:
http://docs.oasis-open.org/emergency/edxl-sitrep/v1.0/cs02/edxl-sitrep-v1.0-cs02.html

PDF:
http://docs.oasis-open.org/emergency/edxl-sitrep/v1.0/cs02/edxl-sitrep-v1.0-cs02.pdf

XML schemas:
http://docs.oasis-open.org/emergency/edxl-sitrep/v1.0/cs02/schemas/

Example files:
http://docs.oasis-open.org/emergency/edxl-sitrep/v1.0/cs02/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:

http://docs.oasis-open.org/emergency/edxl-sitrep/v1.0/cs02/edxl-sitrep-v1.0-cs02.zip

Members of the Emergency Management 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 Emergency Management TC
https://www.oasis-open.org/committees/emergency/

[2] Public reviews:
– 60-day public review, 11 December 2015: https://lists.oasis-open.org/archives/members/201512/msg00003.html
– Comment resolution log: http://docs.oasis-open.org/emergency/edxl-sitrep/v1.0/csprd03/edxl-sitrep-v1.0-csprd03-comment-resolution-log.txt

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

30-day Public Review for #XLIFF v2.1 – ends Nov. 25th

The OASIS XML Localisation Interchange File Format (XLIFF) TC [1] members have recently approved a Committee Specification Draft (CSD) and submitted it for 30-day public review:

XLIFF Version 2.1
Committee Specification Draft 01 / Public Review Draft 01
14 October 2016

What is XLIFF and why is it important?

The XML Localisation Interchange File Format (XLIFF) is a specification for the interchange of localizable software and document based objects and related metadata. The purpose of XLIFF’s extensible XML vocabularies is to store localisable data and carry it from one step of the localization process to the other, while allowing interoperability between and among tools.

Public Review Period:

The public review starts 26 October 2016 at 00:00 UTC and ends 25 November 2016 at 23:59 UTC.

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.

Note that you must be subscribed to the comment mailing list before sending feedback. Instructions on how to subscribe can be found at https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=xliff.

URIs:

The prose specification document and related files are available here:

HTML (Authoritative):
http://docs.oasis-open.org/xliff/xliff-core/v2.1/csprd01/xliff-core-v2.1-csprd01.html

PDF:
http://docs.oasis-open.org/xliff/xliff-core/v2.1/csprd01/xliff-core-v2.1-csprd01.pdf

Editable source:
http://docs.oasis-open.org/xliff/xliff-core/v2.1/csprd01/xliff-core-v2.1-csprd01.xml

Declarative validation artifacts and XML schemas are accessible from:
http://docs.oasis-open.org/xliff/xliff-core/v2.1/csprd01/schemas/

ZIP distribution file (complete):

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:

http://docs.oasis-open.org/xliff/xliff-core/v2.1/csprd01/xliff-core-v2.1-csprd01.zip

Additional information about the specification and the XLIFF TC can be found at the TC’s public home page:

https://www.oasis-open.org/committees/xliff/

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

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

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/xliff-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 “XLIFF Version 2.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 XML Localisation Interchange File Format (XLIFF) TC
https://www.oasis-open.org/committees/xliff/

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

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

60-day Public Review for Business Document Naming and Design Rules v1.0 COS01 – ends Dec. 18th

Members of the OASIS Universal Business Language (UBL) TC [1] have recently approved a Special Majority Ballot [2] to advance Business Document Naming and Design Rules Version 1.0 as a Candidate OASIS Standard (COS). The COS now enters a 60-day public review period in preparation for a member ballot to consider its approval as an OASIS Standard.

Business Document Naming and Design Rules Version 1.0
Candidate OASIS Standard 01
06 October 2016

Specification Overview:

This specification prescribes a set of naming and design rules used to create XML document model validation artefacts (W3C Schema XSD files and OASIS Context/value association files) associated with abstract information bundles formally described using the Core Component Technical Specification 2.01.

3 Statements of Use were received from the Business Document Exchange TC, Document Engineering Services, and the Universal Business Language TC [3].

Public Review Period:

The 60-day public review starts 20 October 2016 at 00:00 UTC and ends 18 December 2016 at 23:59 UTC.

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/ubl/Business-Document-NDR/v1.0/cos01/Business-Document-NDR-v1.0-cos01.xml

HTML:
http://docs.oasis-open.org/ubl/Business-Document-NDR/v1.0/cos01/Business-Document-NDR-v1.0-cos01.html

PDF:
http://docs.oasis-open.org/ubl/Business-Document-NDR/v1.0/cos01/Business-Document-NDR-v1.0-cos01.pdf

ZIP distribution file (complete):

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

http://docs.oasis-open.org/ubl/Business-Document-NDR/v1.0/cos01/Business-Document-NDR-v1.0-cos01.zip

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

https://www.oasis-open.org/committees/ubl/

Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility as explained in the instructions located via the button labeled “Send A Comment” at the top of the TC public home page, or directly at:

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

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/ubl-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 “Business Document Naming and Design Rules Version 1.0,” we call your attention to the OASIS IPR Policy [4] applicable especially [5] to the work of this technical committee. All members of the TC should be familiar with this document, which may create obligations regarding the disclosure and availability of a member’s patent, copyright, trademark and license rights that read on an approved OASIS specification.

OASIS invites any persons who know of any such claims to disclose these if they may be essential to the implementation of the above specification, so that notice of them may be posted to the notice page for this TC’s work.

==============

[1] OASIS Universal Business Language (UBL) TC
https://www.oasis-open.org/committees/ubl/

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

[3] Statements of Use:

– UBL TC: https://lists.oasis-open.org/archives/ubl/201609/msg00053.html

– BDXR TC: https://lists.oasis-open.org/archives/ubl/201609/msg00052.html

– Document Engineering Services: https://lists.oasis-open.org/archives/ubl/201609/msg00054.html

[4] http://www.oasis-open.org/policies-guidelines/ipr

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

Two public reviews from Biometric Services (#BIOSERV) TC – end Nov. 18th

The OASIS Biometric Services (BIOSERV) TC [1] members have recently approved two Committee Specification Drafts (CSD) and submitted them for 30-day public review:

Biometric Identity Assurance Services (BIAS) Soap Profile Version 2.0
Committee Specification Draft 02 / Public Review Draft 01
30 August 2016

and

WS-Biometric Devices Version 1.0
Committee Specification Draft 01 / Public Review Draft 01
23 September 2016

What are these specifications and why are they important?

The Biometric Identity Assurance Services (BIAS) Soap Profile is a companion standard to ISO/IEC 30108-1:2015, Information technology — Biometric Identity Assurance Services. It specifies the design concepts and architecture, data model and data dictionary, message structure and rules, and error handling necessary to invoke SOAP-based services that implement BIAS operations.

Together, the BIAS standard and the BIAS profile provide an open framework for deploying and remotely invoking biometric-based identity assurance capabilities that can be readily accessed across an SOA infrastructure.

The emergence of web services as a common communications bus has “profound implications.” The next generation of biometric devices will not only need to be intelligent, secure, tamper-proof, and spoof resistant, they will also need to be interoperable.

Such devices will require a communications protocol that is secure, globally connected, and free from requirements on operating systems, device drivers, form factors, and low-level communications protocols. WS-Biometric Devices is a protocol designed in the interest of furthering this goal, with a specific focus on the single process shared by all biometric systems—acquisition

About the Technical Committee

The OASIS BIOSERV TC is chartered to define, enhance, and maintain open standards that facilitate the use of biometrics and biometric operations over a service-oriented architecture, such as web services.

Membership in the BIOSERV TC is open to all OASIS members.

Public Review Period:

The public review starts 20 October 2016 at 00:00 UTC and ends 18 November 2016 at 23:59 UTC.

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.

Reviewers may provide comments directly from the comment-tag version of document. The files

BIAS-v2.0-csprd01-COMMENT-TAGS.html

and

WSBD-v1.0-csprd01-COMMENT-TAGS.html

contain the HTML version of the draft with a “[comment?]” link next to each section heading. Clicking on this link will launch your email application and begin a message to bioserv-comment@lists.oasis-open.org with the specific section number and title in the subject line. Simply enter your comment and click send.

Note that you must be subscribed to the comment mailing list before sending feedback. Instructions on how to subscribe can be found at https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=bioserv.

URIs:

The prose specification document and related files are available here:

– Biometric Identity Assurance Services (BIAS) Soap Profile Version 2.0

PDF (Authoritative):
http://docs.oasis-open.org/bioserv/BIAS/v2.0/csprd01/BIAS-v2.0-csprd01.pdf

HTML:
http://docs.oasis-open.org/bioserv/BIAS/v2.0/csprd01/BIAS-v2.0-csprd01.html

HTML with inline commenting:
http://docs.oasis-open.org/bioserv/BIAS/v2.0/csprd01/BIAS-v2.0-csprd01-COMMENT-TAGS.html

Editable source:
http://docs.oasis-open.org/bioserv/BIAS/v2.0/csprd01/BIAS-v2.0-csprd01.docx

XML schemas:
http://docs.oasis-open.org/bioserv/BIAS/v2.0/csprd01/schemas/

– WS-Biometric Devices Version 1.0

PDF (Authoritative):
http://docs.oasis-open.org/bioserv/WSBD/v1.0/csprd01/WSBD-v1.0-csprd01.pdf

HTML:
http://docs.oasis-open.org/bioserv/WSBD/v1.0/csprd01/WSBD-v1.0-csprd01.html

HTML with inline commenting:
http://docs.oasis-open.org/bioserv/WSBD/v1.0/csprd01/WSBD-v1.0-csprd01-COMMENT-TAGS.html

Editable source:
http://docs.oasis-open.org/bioserv/WSBD/v1.0/csprd01/WSBD-v1.0-csprd01.docx

XML schemas:
http://docs.oasis-open.org/bioserv/WSBD/v1.0/csprd01/schemas/wsbd-v1.0.xsd

ZIP distribution file (complete):

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:

– Biometric Identity Assurance Services (BIAS) Soap Profile Version 2.0:
http://docs.oasis-open.org/bioserv/BIAS/v2.0/csprd01/BIAS-v2.0-csprd01.zip

– WS-Biometric Devices Version 1.0:
http://docs.oasis-open.org/bioserv/WSBD/v1.0/csprd01/WSBD-v1.0-csprd01.zip

Additional information about the specification and the Bioserv can be found at the TC’s public home page:

https://www.oasis-open.org/committees/bioserv/

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

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

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/bioserv-comment/

All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the TC members. In connection with this public review of “Biometric Identity Assurance Services (BIAS) Soap Profile Version 2.0” and “WS-Biometric Devices 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 Biometric Services (BIOSERV) TC
https://www.oasis-open.org/committees/bioserv/

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

[3] http://www.oasis-open.org/committees/bioserv/ipr.php
https://www.oasis-open.org/policies-guidelines/ipr#RAND-Mode
RAND Mode

WS-Calendar Minimal PIM-Conformant Schema v1.0 CS01 published by WS-Calendar TC

OASIS is pleased to announce the approval and publication of a new Committee Specification by the members of the OASIS Web Services Calendar (WS-Calendar) TC [1]:

WS-Calendar Minimal PIM-Conformant Schema Version 1.0
Committee Specification 01
26 September 2016

What is the Minimal PIM-Conformant Schema and why is it important?

The WS-Calendar Minimal PIM-Conformant Schema is a schema that conforms with the WS-Calendar Platform Independent Model (PIM). The schema is minimal to optimize for use in machine-to-machine (M2M) schedule negotiations.

iCalendar (RFC5545) and its peer specification XCAL (also in WS-Calendar 1.0)is a well-known and long used means to convey schedule-related information. iCalendar makes extensive use of extension and recursion. The WS-Calendar Platform Independent Model (PIM) constrains iCalendar and defines a simpler information model which shares iCalendar semantics and can be used to create as the common basis for any number of Platform Specific Models (PSMs).

Because an information model is abstract, it can apply to many transmission and serialization schemas. The PIM itself does not include a transmission and serialization schema. Through transitive conformance such PSMs themselves conform to WS-Calendar. The Minimal PIM-Conformant (MIN) schema defines an XML Schema that conforms just with the PIM. MIN can be used by itself or as a seed-schema for other specifications.

This is a final deliverable. Completed and approved by the TC, this OASIS Committee Specification is fully ready for implementation. If submitted for further ratification as an OASIS Standard, its content will not change.

About the TC:

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.

URIs:
The prose specifications and related files are available here:

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

HTML:
http://docs.oasis-open.org/ws-calendar/ws-calendar-min/v1.0/cs01/ws-calendar-min-v1.0-cs01.html

Editable source:
http://docs.oasis-open.org/ws-calendar/ws-calendar-min/v1.0/cs01/ws-calendar-min-v1.0-cs01.pdf

XML schema:
http://docs.oasis-open.org/ws-calendar/ws-calendar-min/v1.0/cs01/schema/ws-calendar-min-v1.0.xsd

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:

http://docs.oasis-open.org/ws-calendar/ws-calendar-min/v1.0/cs01/ws-calendar-min-v1.0-cs01.zip

Members of the OASIS Web Services Calendar (WS-Calendar) TC 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 Web Services Calendar (WS-Calendar) TC
https://www.oasis-open.org/committees/ws-calendar/

[2] Public reviews:
– 30-day public review, 20 January 2016: https://lists.oasis-open.org/archives/members/201601/msg00007.html
– Comment resolution log: http://docs.oasis-open.org/ws-calendar/ws-calendar-min/v1.0/csprd01/ws-calendar-min-v1.0-csprd01-comment-resolution-log.pdf

– 30-day public review, 01 July 2016: https://lists.oasis-open.org/archives/members/201606/msg00013.html
– Comment resolution log: http://docs.oasis-open.org/ws-calendar/ws-calendar-min/v1.0/csprd02/ws-calendar-min-v1.0-csprd02-comment-resolution-log.txt

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

30-day Public Review for TOSCA Simple Profile in YAML v1.1 – ends Nov. 16th

The OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC [1] members have recently approved a Committee Specification Draft (CSD) and submitted it for 30-day public review:

TOSCA Simple Profile in YAML Version 1.1
Committee Specification Draft 01 / Public Review Draft 01
25 August 2016

What is the TOSCA Simple Profile in YAML and why is it important?

TOSCA Simple Profile in YAML defines a simplified profile of the TOSCA Version 1.0 specification in a YAML rendering which is intended to simplify the authoring of TOSCA service templates. This profile defines a less verbose and more human-readable YAML rendering, reduced level of indirection between different modeling artifacts as well as the assumption of a base type system.

Public Review Period:

The public review starts 18 October 2016 at 00:00 UTC and ends 16 November 2016 at 23:59 UTC.

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.

Reviewers may provide comments directly from the comment-tag version of document. The file

TOSCA-Simple-Profile-YAML-v1.1-csprd01-COMMENT-TAGS.html

contains the HTML version of the draft with a “[comment?]” link next to each section heading. Clicking on this link will launch your email application and begin a message to tosca-comment@lists.oasis-open.org with the specific section number and title in the subject line. Simply enter your comment and click send.

Note that you must be subscribed to the comment mailing list before sending feedback. Instructions on how to subscribe can be found at https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=tosca.

URIs:

The prose specification document and related files are available here:

PDF (Authoritative):
http://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.1/csprd01/TOSCA-Simple-Profile-YAML-v1.1-csprd01.pdf

HTML:
http://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.1/csprd01/TOSCA-Simple-Profile-YAML-v1.1-csprd01.html

HTML with inline commenting:
http://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.1/csprd01/TOSCA-Simple-Profile-YAML-v1.1-csprd01-COMMENT-TAGS.html

Editable source:
http://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.1/csprd01/TOSCA-Simple-Profile-YAML-v1.1-csprd01.docx

ZIP distribution file (complete):

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:

http://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.1/csprd01/TOSCA-Simple-Profile-YAML-v1.1-csprd01.zip

Additional information about the specification and the TOSCA can be found at the TC’s public home page:

https://www.oasis-open.org/committees/tosca/

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

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 “”, 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 Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
https://www.oasis-open.org/committees/tosca/

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

[3] http://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

60-day Public Review for #KMIP Specification v1.3 and KMIP Profiles v1.3 – ends Dec. 12th

Members of the OASIS Key Management Interoperability Protocol (KMIP) TC [1] have recently approved Special Majority Ballots [2] to advance the Key Management Interoperability Protocol Specification Version 1.3 and the Key Management Interoperability Protocol Profiles Version 1.3 as Candidate OASIS Standards (COS). These COSs now enter a 60-day public review period in preparation for a member ballot to consider its approval as an OASIS Standard.

Key Management Interoperability Protocol Specification Version 1.3
Candidate OASIS Standard
21 September 2016

Key Management Interoperability Protocol Profiles Version 1.3
Candidate OASIS Standard
21 September 2016

What is KMIP and why should I be interested?

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.

KMIP v1.3 enhances the KMIP v1.2 standard by:

– defining new functionality in the protocol to improve interoperability;
– defining additional Test Cases for verifying and validating the new functionality;
– providing additional information in the KMIP Usage Guide to assist in effective implementation of KMIP in key management clients and servers; and
– defining new profiles for establishing KMIP-compliant implementations.

The KMIP Specification describes the protocol used for the communication between clients and servers to perform management operations on objects stored and maintained by a key management system. This includes symmetric and asymmetric cryptographic keys, digital certificates, and templates used to simplify the creation of objects and control their use.

The KMIP Profiles provide a selected set of base level conformance profiles and authentication suites; additional KMIP Profiles define specific sets of KMIP functionality for conformance purposes.

3 Statements of Use for each were received from P6R Inc., Cryptsoft Pty Ltd, and Fornetix [3].

About the TC:

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.

Public Review Period:

The 60-day public review starts 13 October 2016 at 00:00 UTC and ends 12 December 2016 at 23:59 UTC.

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:

– Key Management Interoperability Protocol Specification Version 1.3

Editable source (Authoritative):
http://docs.oasis-open.org/kmip/spec/v1.3/cos01/kmip-spec-v1.3-cos01.docx

HTML:
http://docs.oasis-open.org/kmip/spec/v1.3/cos01/kmip-spec-v1.3-cos01.html

PDF:
http://docs.oasis-open.org/kmip/spec/v1.3/cos01/kmip-spec-v1.3-cos01.pdf

– Key Management Interoperability Protocol Profiles Version 1.3

Editable source (Authoritative):
http://docs.oasis-open.org/kmip/profiles/v1.3/cos01/kmip-profiles-v1.3-cos01.doc

HTML:
http://docs.oasis-open.org/kmip/profiles/v1.3/cos01/kmip-profiles-v1.3-cos01.html

PDF:
http://docs.oasis-open.org/kmip/profiles/v1.3/cos01/kmip-profiles-v1.3-cos01.pdf

Test cases:
http://docs.oasis-open.org/kmip/profiles/v1.3/cos01/test-cases/kmip-v1.3/mandatory/
http://docs.oasis-open.org/kmip/profiles/v1.3/cos01/test-cases/kmip-v1.3/optional/

ZIP distribution files (complete):

For your convenience, OASIS provides complete packages of the prose specifications and related files in a ZIP distribution file. You can download the ZIP files here:

– Key Management Interoperability Protocol Specification Version 1.3:
http://docs.oasis-open.org/kmip/spec/v1.3/cos01/kmip-spec-v1.3-cos01.zip

– Key Management Interoperability Protocol Profiles Version 1.3:
http://docs.oasis-open.org/kmip/profiles/v1.3/cos01/kmip-profiles-v1.3-cos01.zip

Additional information about the specifications and the KMIP TC can be found on the TC’s public home page:

https://www.oasis-open.org/committees/kmip/

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

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 these public reviews of “Key Management Interoperability Protocol Profiles Version 1.3” and “Key Management Interoperability Protocol Test Cases Version 1.3”, 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 Key Management Interoperability Protocol (KMIP) TC
https://www.oasis-open.org/committees/kmip/

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

[3] Statements of Use:

– P6R Inc. – https://www.oasis-open.org/committees/download.php/58654/
– Cryptsoft Pty Ltd – https://www.oasis-open.org/committees/download.php/58650/
– Fornetix – https://www.oasis-open.org/committees/download.php/58651/

[4] http://www.oasis-open.org/policies-guidelines/ipr

[5] 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

15-day Review for #DITA v1.3 Errata 01 – ends October 20th

The OASIS Darwin Information Typing Architecture (DITA) TC members [1] have produced a draft Errata and submitted the specification for 15-day public review:

Darwin Information Typing Architecture (DITA) Version 1.3 Errata 01
Committee Specification Draft 01/ Public Review Draft 01
30 August 2016

Specification Overview:

The document contains the errata for Darwin Information Typing Architecture (DITA) Version 1.3. A version of the complete DITA v1.3 OASIS Standard with the draft errata applied is included in the package.

We note that there are some broken links in the complete copy of the OASIS Standard. In particular, the link to the explanation behind the Editions is broken. The link should be http://docs.oasis-open.org/dita/dita/v1.3/errata01/csprd01/complete/part0-overview/introduction/about-the-dita-specification.html#about-the-dita-specification/editions. The broken links will be fixed in the next publication. We apologize for any inconvenience caused.

Public Review Period:

The public review starts 07 October 2016 at 00:00 UTC and ends 20 October 2016 at 11:59 UTC.

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:

– Darwin Information Typing Architecture (DITA) Version 1.3 Errata 01

HTML (Authoritative):
http://docs.oasis-open.org/dita/dita/v1.3/errata01/csprd01/dita-v1.3-errata01-csprd01.html

PDF:
http://docs.oasis-open.org/dita/dita/v1.3/errata01/csprd01/dita-v1.3-errata01-csprd01.pdf

Editable DITA source:
http://docs.oasis-open.org/dita/dita/v1.3/errata01/csprd01/dita-v1.3-errata01-csprd01-dita.zip

– Darwin Information Typing Architecture (DITA) Version 1.3 Part 0: Overview Plus Errata 01

HTML (Authoritative):
http://docs.oasis-open.org/dita/dita/v1.3/errata01/csprd01/complete/part0-overview/dita-v1.3-errata01-csprd01-part0-overview-complete.html

PDF:
http://docs.oasis-open.org/dita/dita/v1.3/errata01/csprd01/complete/part0-overview/dita-v1.3-errata01-csprd01-part0-overview-complete.pdf

Editable DITA source:
http://docs.oasis-open.org/dita/dita/v1.3/errata01/csprd01/complete/part0-overview/dita-v1.3-errata01-csprd01-part0-overview-complete-dita.zip

– Darwin Information Typing Architecture (DITA) Version 1.3 Part 1: Base Edition Plus Errata 01

HTML (Authoritative):
http://docs.oasis-open.org/dita/dita/v1.3/errata01/csprd01/complete/part1-base/dita-v1.3-errata01-csprd01-part1-base-complete.html

PDF:
http://docs.oasis-open.org/dita/dita/v1.3/errata01/csprd01/complete/part1-base/dita-v1.3-errata01-csprd01-part1-base-complete.pdf

Editable DITA source:
http://docs.oasis-open.org/dita/dita/v1.3/errata01/csprd01/complete/part1-base/dita-v1.3-errata01-csprd01-part1-base-complete-dita.zip

– Darwin Information Typing Architecture (DITA) Version 1.3 Part 2: Technical Content Edition Plus Errata 01

HTML (Authoritative):
http://docs.oasis-open.org/dita/dita/v1.3/errata01/csprd01/complete/part2-tech-content/dita-v1.3-errata01-csprd01-part2-tech-content-complete.html

PDF:
http://docs.oasis-open.org/dita/dita/v1.3/errata01/csprd01/complete/part2-tech-content/dita-v1.3-errata01-csprd01-part2-tech-content-complete.pdf

Editable DITA source:
http://docs.oasis-open.org/dita/dita/v1.3/errata01/csprd01/complete/part2-tech-content/dita-v1.3-errata01-csprd01-part2-tech-content-complete-dita.zip

– Darwin Information Typing Architecture (DITA) Version 1.3 Part 3: All-Inclusive Edition Plus Errata 01

HTML (Authoritative):
http://docs.oasis-open.org/dita/dita/v1.3/errata01/csprd01/complete/part3-all-inclusive/dita-v1.3-errata01-csprd01-part3-all-inclusive-complete.html

PDF:
http://docs.oasis-open.org/dita/dita/v1.3/errata01/csprd01/complete/part3-all-inclusive/dita-v1.3-errata01-csprd01-part3-all-inclusive-complete.pdf

Editable DITA source:
http://docs.oasis-open.org/dita/dita/v1.3/errata01/csprd01/complete/part3-all-inclusive/dita-v1.3-errata01-csprd01-part3-all-inclusive-complete-dita.zip

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/dita/dita/v1.3/errata01/csprd01/dita-v1.3-errata01-csprd01.zip

Additional information about this specification and the DITA TC may be found on the TC’s public home page located at:

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

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

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/dita-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 ‘Darwin Information Typing Architecture (DITA) Version 1.3 Errata 01’, we call your attention to the OASIS IPR Policy [2] applicable especially [3] to the work of this technical committee. All members of the TC should be familiar with this document, which may create obligations regarding the disclosure and availability of a member’s patent, copyright, trademark and license rights that read on an approved OASIS specification.

OASIS invites any persons who know of any such claims to disclose these if they may be essential to the implementation of the above specification, so that notice of them may be posted to the notice page for this TC’s work.

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

[1] OASIS Darwin Information Typing Architecture (DITA) TC
http://www.oasis-open.org/committees/dita/

[2] http://www.oasis-open.org/policies-guidelines/ipr

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

ebCore Agreement Update Specification v1.0 published by the OASIS ebXML Core (ebCore) TC

OASIS is pleased to announce the approval and publication of a new Committee Specification by the members of the OASIS ebXML Core (ebCore) TC[1]:

ebCore Agreement Update Specification Version 1.0
Committee Specification 01
18 September 2016

What is ebCore Agreement and why is it important?

The ebCore Agreement Update specification defines message exchanges and an XML schema to support the exchange of messaging service communication agreement update requests and the associated responses to such requests.

The schema offers extensibility for various types of updates. The main initial application of the specification is the exchange of X.509 certificates for certificate rollover, for which a separate extension schema is provided.

The specification is based on the concept of messaging service communication agreements and the creation of new agreements as independently identified updated copies of existing agreements. The specification also provides an Agreement Termination feature. The specification supports ebMS2, ebMS3 and AS4 but can also be used with other protocols that have a concept of communication agreement. The specification is independent of storage or interchange formats for configuration information.

This is a final deliverable. Completed and approved by the TC, this OASIS Committee Specification is fully ready for implementation. If submitted for further ratification as an OASIS Standard, its content will not change.

About the TC:

The ebXML Core TC maintains ebXML specifications transitioned from other Technical Committees. TCs eligible for maintenance by the ebXML Core TC are ebXML Messaging, ebXML CPPA, ebXML ebBP, ebXML IIC, and ebXML RegRep. The ebXML Core TC manages clarifications, modifications, and enhancements for the specifications through the OASIS standards process.

URIs:

The prose specifications and related files are available here:

Editable source (Authoritative):
http://docs.oasis-open.org/ebcore/ebcore-au/v1.0/cs01/ebcore-au-v1.0-cs01.odt

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

PDF:
http://docs.oasis-open.org/ebcore/ebcore-au/v1.0/cs01/ebcore-au-v1.0-cs01.pdf

Agreement Update XML schema:
http://docs.oasis-open.org/ebcore/ebcore-au/v1.0/cs01/schema/ebcore-au-v1.0.xsd

Certificate Update XML schema:
http://docs.oasis-open.org/ebcore/ebcore-au/v1.0/cs01/schema/ebcore-cu-v1.0.xsd

Schema data dictionaries:
http://docs.oasis-open.org/ebcore/ebcore-au/v1.0/cs01/documentation/

XML Signature 1.1 schema driver:
http://docs.oasis-open.org/ebcore/ebcore-au/v1.0/cs01/schema/xmldsig1-schema.xsd

XML document samples:
http://docs.oasis-open.org/ebcore/ebcore-au/v1.0/cs01/samples/

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:

http://docs.oasis-open.org/ebcore/ebcore-au/v1.0/cs01/ebcore-au-v1.0-cs01.zip

Members of the ebCore TC 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 ebXML Core (ebCore) TC
https://www.oasis-open.org/committees/ebcore/

[2] Public reviews:
– 30-day public review, 10 November 2015: https://lists.oasis-open.org/archives/members/201511/msg00003.html
– Comment resolution log: http://docs.oasis-open.org/ebcore/ebcore-au/v1.0/csprd01/ebcore-au-v1.0-csprd01-comment-resolution-log.xls

– 15-day public review, 04 July 2016: https://lists.oasis-open.org/archives/members/201607/msg00000.html
– Comment resolution log: http://docs.oasis-open.org/ebcore/ebcore-au/v1.0/csprd02/ebcore-au-v1.0-csprd02-comment-resolution-log.txt

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

Schedule Signals and Streams Version 1.0 published by WS-Calendar TC

OASIS is pleased to announce the approval and publication of a new Committee Specification by the members of the OASIS Web Services Calendar (WS-Calendar) TC [1]:

Schedule Signals and Streams Version 1.0
Committee Specification 01
18 September 2016

What is Schedule Signals and Streams?

There is a common need to communicate information linked to repetitive intervals of time, for history, for telemetry, for projections, for bids. Much of the information in each interval can be inferred from the surrounding intervals. The document defines a normative structure for conveying time-series of information that is conformant with WS-Calendar. We term these conveyances “Streams”.

This is a final deliverable. Completed and approved by the TC, this OASIS Committee Specification is fully ready for implementation. If submitted for further ratification as an OASIS Standard, its content will not change.

About the TC:

The OASIS WS-Calendar TC works to adapt existing calendaring standards (used in human interactions) for Web services. WS-Calendar is designed for use inside other specifications and standards, bringing a common scheduling and performance alignment to service coordination, including between domains.

Coordinating schedules and activities is critical to connecting the processes and activities of the internet of people with the internet of things. The initial work of WS-Calendar is finding use in enterprise scheduling, in energy markets, particularly in the EMIX and Energy Interoperation specifications, and in combination with BIM (Building Information Models) to enhance energy models.

Other specifications of the WS-Calendar TC include WS-Calendar, SOAP-based Services, REST-Based Services, and a Platform Independent Model (PIM) for Calendar and Schedules.

URIs:
The prose specifications and related files are available here:

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

HTML:
http://docs.oasis-open.org/ws-calendar/streams/v1.0/cs01/streams-v1.0-cs01.html

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

XML schema:
http://docs.oasis-open.org/ws-calendar/streams/v1.0/cs01/xsd/ws-calendar-streams-v1.0.xsd

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:

http://docs.oasis-open.org/ws-calendar/streams/v1.0/cs01/streams-v1.0-cs01.zip

Members of the WS-Calendar TC 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 Web Services Calendar (WS-Calendar) TC
https://www.oasis-open.org/committees/ws-calendar/

[2] Public reviews:
– 30-day public review, 22 January 2013: https://lists.oasis-open.org/archives/members/201301/msg00014.html

– 15-day public review, 09 July 2013: https://lists.oasis-open.org/archives/members/201307/msg00005.html
– Comment resolution log: http://docs.oasis-open.org/ws-calendar/streams/v1.0/csprd02/streams-v1.0-csprd02-comment-resolution-log.pdf

– 30-day public review, 01 July 2016: https://lists.oasis-open.org/archives/members/201606/msg00013.html
– Comment resolution log: http://docs.oasis-open.org/ws-calendar/streams/v1.0/csprd03/streams-v1.0-csprd03-comment-resolution-log.txt

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

15-day Public Review for Business Document Envelope Version 1.1 – ends Oct. 18th

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

Business Document Envelope Version 1.1
Committee Specification Draft 02 / Public Review Draft 02
20 July 2016

What is the Business Document Envelope Specification and Why Is It Important To Me?

The metaphor of a paper envelope in which one places business documents for transport or management is an apt one for describing the an equivalent electronic artifact.

The Business Document Envelope Version 1.1 specifies an XML vocabulary [XML] that expresses in machine-processable syntax the semantics of enveloping a payload of content with information about that content. It enumerates the information components of a payload envelope and formally describes the semantics of each.

This is distinct from any transport-layer infrastructure envelope that may be required to propagate documents from one system to another. A business document envelope describes contextual information important to the sender and receiver about the payloads, without having to modify the payloads in any fashion.

About the TC:

The OASIS BDXR TC advances an open standards framework to support public e-procurement and e-invoicing. The group defines specifications for a lightweight and federated messaging infrastructure that supports a 4-corner model for the secure and reliable exchange of electronic documents. Wherever possible, the TC specifications are based on profiles of existing standards from OASIS and elsewhere. BDXR TC members also coordinate the submission of new requirements as use cases for expanded functionality.

All those involved in e-procurement and e-invoicing are invited to participate in the BDXR TC, including public and private sector agencies, enterprises, solution providers, consultants, and researchers. E-payment actors including financial institutions, associations and payment networks should also be represented in this work.

Public Review Period:

The public review starts 04 October 2016 at 00:00 UTC and ends 18 October 2016 at 11:59 UTC. The specification was previously submitted for public review [2]. This 15-day review is limited in scope to changes made from the previous review. Changes are highlighted in the red-lined version at http://docs.oasis-open.org/bdxr/bdx-bde/v1.1/csprd02/bdx-bde-v1.1-csprd02-DIFF.pdf.

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.

Reviewers may provide comments directly from the comment-tag version of document. The file

bdx-bde-v1.1-csprd02-COMMENT-TAGS.html

contains the HTML version of the draft with a “[comment?]” link next to each section heading. Clicking on this link will launch your email application and begin a message to bdxr-comment@lists.oasis-open.org with the specific section number and title in the subject line. Simply enter your comment and click send.

Note that you must be subscribed to the comment mailing list before sending feedback. Instructions on how to subscribe can be found at https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=bdxr.

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

Editable source (Authoritative):
http://docs.oasis-open.org/bdxr/bdx-bde/v1.1/csprd02/bdx-bde-v1.1-csprd02.xml

HTML:
http://docs.oasis-open.org/bdxr/bdx-bde/v1.1/csprd02/bdx-bde-v1.1-csprd02.html

HTML with in-line comment tags:
http://docs.oasis-open.org/bdxr/bdx-bde/v1.1/csprd02/bdx-bde-v1.1-csprd02-COMMENT-TAGS.html

PDF:
http://docs.oasis-open.org/bdxr/bdx-bde/v1.1/csprd02/bdx-bde-v1.1-csprd02.pdf

Model:
http://docs.oasis-open.org/bdxr/bdx-bde/v1.1/csprd02/mod

XML Schema:
http://docs.oasis-open.org/bdxr/bdx-bde/v1.1/csprd02/xsd

XML Schema run-time:
http://docs.oasis-open.org/bdxr/bdx-bde/v1.1/csprd02/xsdrt

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/bdxr/bdx-bde/v1.1/csprd02/bdx-bde-v1.1-csprd02.zip

Additional information about this specification and the BDXR TC may be found on the TC’s public home page located at:

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

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

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/bdxr-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 ‘Business Document Envelope Version 1.1’, we call your attention to the OASIS IPR Policy [3] applicable especially [4] to the work of this technical committee. All members of the TC should be familiar with this document, which may create obligations regarding the disclosure and availability of a member’s patent, copyright, trademark and license rights that read on an approved OASIS specification.

OASIS invites any persons who know of any such claims to disclose these if they may be essential to the implementation of the above specification, so that notice of them may be posted to the notice page for this TC’s work.

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

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

[2] Previous public reviews:

30-day public review, 21 April 2016:
https://lists.oasis-open.org/archives/members/201604/msg00005.html
– Comment resolution log:
http://docs.oasis-open.org/bdxr/bdx-bde/v1.1/csprd01/bdx-bde-v1.1-csprd01-comment-resolution-log.xls

[3] http://www.oasis-open.org/policies-guidelines/ipr

[4] http://www.oasis-open.org/committees/bdxr/ipr.php
https://www.oasis-open.org/policies-guidelines/ipr#Non-Assertion-Mode
Non-Assertion Mode

No results with the selected filters