OASIS elects open source, financial services, cybersecurity, and IT leaders to its Board of Directors

17 August 2018 — OASIS, the international standards and open source consortium, announced the results of its 2018 Board of Directors elections. The makeup of the Board reflects the consortium’s reach into the open source community as well as its reputation as the home of foundational cybersecurity, privacy, legal, and cloud computing projects.

Margaret LaBrecque of Intel; Jenny Menna of U.S. Bank; and Jim Cabral of MTG Management Consultants were elected and Frederick Hirsch of Fujitsu; Gershon Janssen, an independent privacy consultant; Paul Lipton of CA Technologies; and Richard Struse of Mitre were reelected to the OASIS Board.

They join Board Directors with continuing terms: Martin Chapman, Ph.D., of Oracle; Beth Pumo of Kaiser Permanente; and Bruce Rich of Cryptsoft.

“The worlds of standardization and open source development are moving beyond coexistence to coalescence. OASIS is uniquely positioned to enhance this coming-together,” observed Gershon Janssen, chair of the OASIS Board of Directors. “These new Board members bring vital expertise and fresh perspective that will ensure our ability to meet the challenges ahead. It’s an exciting time to be part of OASIS.”

OASIS expressed thanks to outgoing Board members, Dawn Jutla of Saint Mary’s University Sobey School of Business and Monica Palmirani of the University of Bologna’s School of Law. The consortium offered special thanks to retiring Board members, Jenny Huang of AT&T and Dave Ings of IBM. Dave provided leadership for OASIS since 2009.

Trey Darley of New Context and Jacques Durand of Fujitsu were reelected to the OASIS Technical Advisory Board (TAB).

OASIS CEO and executive director, Laurent Liscia, welcomed the new Board Directors and TAB members. “Cybersecurity, cloud computing, and legal standards have long been strong areas of focus for OASIS, and our Board is made up of experts who will ensure we continue to serve and grow those industries. I’m also excited to have leaders experienced in open source development. Their guidance will help shape the next chapter for OASIS.”

About OASIS

OASIS is one of the most respected, member-driven standards bodies in the world. It offers projects—including open source projects–a path to standardization and de jure approval for recognition in international policy and procurement. OASIS has a broad technical agenda encompassing cybersecurity, privacy, cryptography, cloud computing, IoT, legal, emergency management, augmented reality, and more. Any initiative for developing code, APIs, specifications, or reference implementations can find a home at OASIS. Each project operates independently under industry-approved process and IPR policies. Some of the most widely adopted OASIS Standards include AMQP, CAP, CMIS, DITA, DocBook, KMIP, MQTT, OpenC2, OpenDocument, PKCS, SAML, STIX, TAXII, TOSCA, UBL, and XLIFF. Many of these have gone on to be published as ISO, IEC, or ITU standards. New work is encouraged, and all are welcome to participate. OASIS members can be found in 100+ countries on virtually every continent. Major multinational companies, SMEs, government agencies, universities, research institutions, consulting groups, and individuals are represented.

Media inquiries: communications@oasis-open.org; +1.941.284.0403

Universal Business Language (#UBL) v2.2 OASIS Standard published

OASIS is pleased to announce the publication of its newest OASIS Standard, approved by the members on 09 July 2018:

Universal Business Language Version 2.2
OASIS Standard
09 July 2018

Overview:

The Universal Business Language (UBL) is an open library of standard electronic XML business documents for procurement and transportation such as purchase orders, invoices, transport logistics and waybills. It is designed to operate within a standard business framework such as ISO/IEC 15000 (ebXML) to provide a complete, standards-based infrastructure that can extend the benefits of existing EDI systems to businesses of all sizes.

Version 2.2 is completely backward-compatible with UBL 2.0. UBL is freely available to everyone without legal encumbrance or licensing fees.

To find out more about what UBL v2.2 is and why it might matter to you, see https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ubl#overview.

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

Universal Business Language Version 2.2

Editable source (Authoritative):
http://docs.oasis-open.org/ubl/os-UBL-2.2/UBL-2.2.xml

HTML:
http://docs.oasis-open.org/ubl/os-UBL-2.2/UBL-2.2.html

PDF:
http://docs.oasis-open.org/ubl/os-UBL-2.2/UBL-2.2.pdf

Distribution ZIP files

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

http://docs.oasis-open.org/ubl/os-UBL-2.2/UBL-2.2.zip.

Our congratulations to the members of the OASIS Universal Business Language TC on achieving this milestone.

#TOSCA Simple Profile in #YAML v1.2 approved as a Committee Specification

OASIS is pleased to announce that TOSCA Simple Profile in YAML v1.2 from the OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC [1] has been approved as an OASIS Committee Specification.

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.

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:

TOSCA Simple Profile in YAML Version 1.2
Committee Specification 01
19 July 2018

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

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

PDF (Authoritative):
http://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.2/cs01/TOSCA-Simple-Profile-YAML-v1.2-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:

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

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

[2] Public review:
* 30-day public review, 19 January 2018:
https://lists.oasis-open.org/archives/tosca/201801/msg00021.html
– Comment resolution log:
http://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.2/csprd01/TOSCA-Simple-Profile-YAML-v1.2-csprd01-comment-resolution-log.xlsx

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

Invitation to comment on Service Metadata Publishing (#SMP) V2.0 from #BDXR TC – ends August 24th

OASIS and the OASIS Business Document Exchange (BDXR) TC are pleased to announce that Service Metadata Publishing (SMP) Version 2.0 is now available for public review and comment.

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 (endpoint) of the business document, such as types of documents the endpoint 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.

The documents and related files are available here:

Service Metadata Publishing (SMP) Version 2.0
Committee Specification Draft 01 / Public Review Draft 01
18 July 2018

Editable source (Authoritative):
http://docs.oasis-open.org/bdxr/bdx-smp/v2.0/csprd01/bdx-smp-v2.0-csprd01.docx

HTML:
http://docs.oasis-open.org/bdxr/bdx-smp/v2.0/csprd01/bdx-smp-v2.0-csprd01.html

PDF:
http://docs.oasis-open.org/bdxr/bdx-smp/v2.0/csprd01/bdx-smp-v2.0-csprd01.pdf

XML schemas and documentation:
http://docs.oasis-open.org/bdxr/bdx-smp/v2.0/csprd01/xsd/
http://docs.oasis-open.org/bdxr/bdx-smp/v2.0/csprd01/xsdrt/
http://docs.oasis-open.org/bdxr/bdx-smp/v2.0/csprd01/mod/

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:

http://docs.oasis-open.org/bdxr/bdx-smp/v2.0/csprd01/bdx-smp-v2.0-csprd01.zip

How to Provide Feedback

OASIS and the OASIS Business Document Exchange (BDXR) 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 July 26 at 00:00 UTC and ends August 24, 2018 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=bdxr).

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/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, 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 BDXR TC can be found at the TC’s public home page:

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

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

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

[2] https://www.oasis-open.org/policies-guidelines/ipr#Non-Assertion-Mode
Non-Assertion Mode

Invitation to comment on #AMQP Enforcing Connection Uniqueness and AMQP Anonymous Terminus for Message Routing – ends Aug. 14th

OASIS and the Advanced Message Queuing Protocol (AMQP) TC are pleased to announce that Advanced Message Queuing Protocol (AMQP) Enforcing Connection Uniqueness Version 1.0 and Using the AMQP Anonymous Terminus for Message Routing Version 1.0 are now available for public review and comment.

AMQP is a vendor-neutral, platform-agnostic protocol for passing real-time data streams and business transactions. The goal of AMQP is to ensure information is safely and efficiently transported between applications, among organizations, across distributed cloud computing environments, and within mobile infrastructures by enabling a commoditized, multi-vendor ecosystem.

Enforcing Connection Uniqueness defines a mechanism by which two processes communicating using AMQP v1.0 can ensure and enforce that there exists only a single open AMQP connection between the two of them.

Anonymous Terminus for Message Routing defines a mechanism whereby a single outgoing link can be used to transfer messages which are then routed using the address carried in their “to” field.

The documents and related files are available here:

– Advanced Message Queuing Protocol (AMQP) Enforcing Connection Uniqueness Version 1.0
Committee Specification Draft 01/Public Review Draft 01
2 July 2018

Editable source (Authoritative):
http://docs.oasis-open.org/amqp/soleconn/v1.0/csprd01/soleconn-v1.0-csprd01.xml

HTML:
http://docs.oasis-open.org/amqp/soleconn/v1.0/csprd01/soleconn-v1.0-csprd01.html

PDF:
http://docs.oasis-open.org/amqp/soleconn/v1.0/csprd01/soleconn-v1.0-csprd01.pdf

and

– Using the AMQP Anonymous Terminus for Message Routing Version 1.0
Committee Specification Draft 01/Public Review Draft 01
2 July 2018

Editable source (Authoritative):
http://docs.oasis-open.org/amqp/anonterm/v1.0/csprd01/anonterm-v1.0-csprd01.xml

HTML:
http://docs.oasis-open.org/amqp/anonterm/v1.0/csprd01/anonterm-v1.0-csprd01.html

PDF:
http://docs.oasis-open.org/amqp/anonterm/v1.0/csprd01/anonterm-v1.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 file at:

– Advanced Message Queuing Protocol (AMQP) Enforcing Connection Uniqueness Version 1.0: http://docs.oasis-open.org/amqp/soleconn/v1.0/csprd01/soleconn-v1.0-csprd01.zip

– Using the AMQP Anonymous Terminus for Message Routing Version 1.0: http://docs.oasis-open.org/amqp/anonterm/v1.0/csprd01/anonterm-v1.0-csprd01.zip

How to Provide Feedback

OASIS and the AMQP 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 16 July 2018 at 00:00 UTC and ends 14 August 2018 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=amqp).

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/amqp-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 AMQP TC can be found at the TC’s public home page:

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

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

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

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

#UBL V2.2 becomes an OASIS Standard

OASIS is pleased to announce that Universal Business Language Version 2.2 has been approved by the membership as an OASIS Standard [1].

The ballot was held under the OASIS call for consent procedure [2]. Under this procedure, consent is assumed unless eligible voters register valid objections. In the ballot, Universal Business Language Version 2.2 Candidate OASIS Standard 01 received 17 affirmative consents and no objections. Therefore the standard is approved.

UBL is an open library of standard electronic XML business documents for procurement and transportation such as purchase orders, invoices, transport logistics and waybills. It is designed to operate within a standard business framework such as ISO/IEC 15000 (ebXML) to provide a complete, standards-based infrastructure that can extend the benefits of existing EDI systems to businesses of all sizes. Version 2.2 is completely backward-compatible with UBL 2.0.

UBL is freely available to everyone without legal encumbrance or licensing fees.

TC Administration will now prepare and publish the final OASIS Standard and notify members when it is available.

Our congratulations to the members of the TC and to the community of implementers, developers and users who have brought the work successfully to this milestone

=== Additional information

[1] Ballot:
https://www.oasis-open.org/committees/ballot.php?id=3224

[2] https://www.oasis-open.org/policies-guidelines/tc-process-2017-05-26#OScallForConsent

[3] Call for consent

https://lists.oasis-open.org/archives/members/201806/msg00007.html

[4] URLs to the latest published version:

Universal Business Language Version 2.2
Candidate OASIS Standard 01
22 April 2018

Editable source (Authoritative):
http://docs.oasis-open.org/ubl/cos01-UBL-2.2/UBL-2.2.xml

HTML:
http://docs.oasis-open.org/ubl/cos01-UBL-2.2/UBL-2.2.html

PDF:
http://docs.oasis-open.org/ubl/cos01-UBL-2.2/UBL-2.2.pdf

Code lists for constraint validation:
http://docs.oasis-open.org/ubl/cos01-UBL-2.2/cl/

Context/value Association files for constraint validation:
http://docs.oasis-open.org/ubl/cos01-UBL-2.2/cva/

Document models of information bundles:
http://docs.oasis-open.org/ubl/cos01-UBL-2.2/mod/

Default validation test environment:
http://docs.oasis-open.org/ubl/cos01-UBL-2.2/val/

XML examples:
http://docs.oasis-open.org/ubl/cos01-UBL-2.2/xml/

Annotated XSD schemas:
http://docs.oasis-open.org/ubl/cos01-UBL-2.2/xsd/

Runtime XSD schemas:
http://docs.oasis-open.org/ubl/cos01-UBL-2.2/xsdrt/

The ZIP containing the complete files of this release is found in the directory:

http://docs.oasis-open.org/ubl/cos01-UBL-2.2/UBL-2.2.zip

Darwin Information Typing Architecture (DITA) V1.3 Errata 02 from #DITA TC approved

OASIS is pleased to announce that Darwin Information Typing Architecture (DITA) V1.3 Errata 02 from the OASIS Darwin Information Typing Architecture (DITA) TC [1] is now an Approved Errata.

DITA is a specification for creating, maintaining, and publishing modular content. It is designed to support systems that maximize reuse of material. This document contains errata for Darwin Information Typing Architecture (DITA) Version 1.3.

The prose specifications and related files are available here:

Darwin Information Typing Architecture (DITA) Version 1.3 Errata 02
OASIS Approved Errata
19 June 2018

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

PDF:
http://docs.oasis-open.org/dita/dita/v1.3/errata02/os/dita-v1.3-errata02-os.pdf

DITA Version 1.3

– Part 0: Overview Plus Errata 02

HTML:
http://docs.oasis-open.org/dita/dita/v1.3/errata02/os/complete/part0-overview/dita-v1.3-errata02-os-part0-overview-complete.html

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

ZIP file that contains the DITA source for this part:
http://docs.oasis-open.org/dita/dita/v1.3/errata02/os/complete/part0-overview/dita-v1.3-errata02-os-part0-overview-complete-dita.zip

– Part 1: Base Edition Plus Errata 02

HTML:
http://docs.oasis-open.org/dita/dita/v1.3/errata02/os/complete/part1-base/dita-v1.3-errata02-os-part1-base-complete.html

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

ZIP file that contains the DITA source for this part:
http://docs.oasis-open.org/dita/dita/v1.3/errata02/os/complete/part1-base/dita-v1.3-errata02-os-part1-base-complete-dita.zip

– Part 2: Technical Content Edition Plus Errata 02

HTML:
http://docs.oasis-open.org/dita/dita/v1.3/errata02/os/complete/part2-tech-content/dita-v1.3-errata02-os-part2-tech-content-complete.html

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

ZIP file that contains the DITA source for this part:
http://docs.oasis-open.org/dita/dita/v1.3/errata02/os/complete/part2-tech-content/dita-v1.3-errata02-os-part2-tech-content-complete-dita.zip

– Part 3: All-Inclusive Edition Plus Errata 02

HTML:
http://docs.oasis-open.org/dita/dita/v1.3/errata02/os/complete/part3-all-inclusive/dita-v1.3-errata02-os-part3-all-inclusive-complete.html

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

ZIP file that contains the DITA source for this part:
http://docs.oasis-open.org/dita/dita/v1.3/errata02/os/complete/part3-all-inclusive/dita-v1.3-errata02-os-part3-all-inclusive-complete-dita.zip

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/dita/dita/v1.3/errata02/os/dita-v1.3-errata02-os.zip

Members of the DITA TC approved this specification by Full Majority Vote. The specification had been released for public review as required by the TC Process [2]. The vote to approve as a Approved Errata 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 Darwin Information Typing Architecture (DITA) TC
https://www.oasis-open.org/committees/dita/

[2] Public reviews:

* 15-day public review, 30 May 2018:
https://lists.oasis-open.org/archives/members/201805/msg00010.html

[3] Approval minutes:
https://lists.oasis-open.org/archives/dita/201806/msg00044.html

Classification of Everyday Living V1.0 from the #COEL TC approved as a Committee Specification

OASIS is pleased to announce that Classification of Everyday Living Version 1.0 from the OASIS Classification of Everyday Living (COEL) TC [1] has been approved as an OASIS Committee Specification.

Digital technologies are becoming integral to our daily lives. They promise huge benefits to society, but the data they create carries the potential for abuse.

COEL is a hierarchical taxonomy of everyday human life events, comprised of a Knowledge Base, Data Model, and Methodology. It aims to be a roadmap for collecting and handling personal data that protects the interests of both individuals and businesses.

This specification draft defines the Classification of Everyday Living (COEL) Version 1.0 specification for the complete implementation of a compliant system. Examples and non-normative material are also offered as guidance. A model in JSON is also provided.

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:

Classification of Everyday Living Version 1.0
Committee Specification 02
26 June 2018

Editable source (Authoritative):
http://docs.oasis-open.org/coel/COEL/v1.0/cs02/COEL-v1.0-cs02.docx

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

PDF:
http://docs.oasis-open.org/coel/COEL/v1.0/cs02/COEL-v1.0-cs02.pdf

COEL model v1.0:
http://docs.oasis-open.org/coel/COEL/v1.0/cs02/model/coel.json

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/coel/COEL/v1.0/cs02/COEL-v1.0-cs02.zip

Members of the COEL 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 Classification of Everyday Living (COEL) TC
https://www.oasis-open.org/committees/coel/

[2] Public reviews:

– 30-day public review, 10 November 2016:
https://lists.oasis-open.org/archives/members/201611/msg00000.html
– Comment resolution log:
http://docs.oasis-open.org/coel/COEL/v1.0/csprd01/COEL-v1.0-csprd01-comment-resolution-log.xlsx

– 15-day public review, 11 December 2017:
https://lists.oasis-open.org/archives/members/201712/msg00002.html
– Comment resolution log:
http://docs.oasis-open.org/coel/COEL/v1.0/csprd02/COEL-v1.0-csprd02-comment-resolution-log.xlsx

– 15-day public review, 09 May 2018:
https://lists.oasis-open.org/archives/members/201805/msg00004.html
– Comment resolution log:
http://docs-staging.oasis-open.org/ztest/coel/COEL/v1.0/csprd03/COEL-v1.0-csprd03-comment-resolution-log.txt

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

Invitation to comment on #OSLC Requirements Management Version 2.1 – ends Aug. 2nd

OASIS and the OASIS OSLC Lifecycle Integration Domains TC are pleased to announce thatOSLC Requirements Management Version 2.1 is now available for public review and comment.

For anyone developing complex systems and software, managing change and configurations throughout the development lifecycle can be difficult. This is especially true in heterogeneous environments that include homegrown tools, open source projects, and commercial tools from different vendors. Organizations that need to design, develop, deliver, and evolve a portfolio of products can benefit from an open technical architecture that is minimalist, loosely coupled, and standardized.

The OSLC (Open Services for Lifecycle Collaboration) initiative applies Linked Data principles, such as those defined in the W3C Linked Data Platform (LDP), to create a cohesive set of specifications that can enable products, services, and other distributed network resources to interoperate successfully.

The Requirements Management specification builds on OSLC’s Core Specification to define the resources, properties and operations to be supported by an OSLC Requirements Definition and Management (OSLC-RM) server.

Requirements Management resources include Requirements, Requirements Collections and supporting resources defined in the OSLC Core specification. The properties defined describe these resources and the relationships between resources. Operations are defined in terms of HTTP methods and MIME type handling. The resources, properties and operations defined do not form a comprehensive interface to Requirements Definition and Management, but instead target specific integration use cases documented by the OASIS OSLC Lifecycle Integration for Domains TC.

The documents and related files are available here:

OSLC Requirements Management Version 2.1.
Committee Specification Draft 01 / Public Review Draft 01
31 May 2018

– Part 1: Specification

HTML and Editable source (Authoritative):
http://docs.oasis-open.org/oslc-domains/oslc-rm/v2.1/csprd01/part1-requirements-management-spec/oslc-rm-v2.1-csprd01-part1-requirements-management-spec.html

PDF:
http://docs.oasis-open.org/oslc-domains/oslc-rm/v2.1/csprd01/part1-requirements-management-spec/oslc-rm-v2.1-csprd01-part1-requirements-management-spec.pdf

– Part 2: Vocabulary

HTML and Editable source (Authoritative):
http://docs.oasis-open.org/oslc-domains/oslc-rm/v2.1/csprd01/part2-requirements-management-vocab/oslc-rm-v2.1-csprd01-part2-requirements-management-vocab.html

PDF:
http://docs.oasis-open.org/oslc-domains/oslc-rm/v2.1/csprd01/part2-requirements-management-vocab/oslc-rm-v2.1-csprd01-part2-requirements-management-vocab.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 file at:

http://docs.oasis-open.org/oslc-domains/oslc-rm/v2.1/csprd01/oslc-rm-v2.1-csprd01.zip

How to Provide Feedback

OASIS and the OSLC Domains 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 July 2018 at 00:00 UTC and ends 02 August 2018 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=oslc-domains).

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/oslc-domains-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 OSLC Domains TC can be found at the TC’s public home page:

https://www.oasis-open.org/committees/oslc-domains/

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

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

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

#OSLC Change Management V3.0 Committee Specification 01 approved and published

OASIS is pleased to announce that OSLC Change Management Version 3.0 from the OASIS OSLC Lifecycle Integration Domains TC [1] has been approved as an OASIS Committee Specification.

For anyone developing complex systems and software, managing change and configurations throughout the development lifecycle can be difficult. This is especially true in heterogeneous environments that include homegrown tools, open source projects, and commercial tools from different vendors. Organizations that need to design, develop, deliver, and evolve a portfolio of products can benefit from an open technical architecture that is minimalist, loosely coupled, and standardized.

The OSLC (Open Services for Lifecycle Collaboration) initiative applies Linked Data principles, such as those defined in the W3C Linked Data Platform (LDP), to create a cohesive set of specifications that can enable products, services, and other distributed network resources to interoperate successfully.

OSLC Change Management Version 3.0 defines a RESTful web services interface for managing product change requests, activities, tasks and relationships as well as related resources such as requirements, test cases, or architectural resources.

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:

OSLC Change Management Version 3.0
Committee Specification 01
08 June 2018

Part 1: Specification

HTML/Editable source (Authoritative):
http://docs.oasis-open.org/oslc-domains/cm/v3.0/cs01/part1-change-mgt/cm-v3.0-cs01-part1-change-mgt.html

PDF:
http://docs.oasis-open.org/oslc-domains/cm/v3.0/cs01/part1-change-mgt/cm-v3.0-cs01-part1-change-mgt.pdf

Part 2: Vocabulary

HTML/Editable source (Authoritative):
http://docs.oasis-open.org/oslc-domains/cm/v3.0/cs01/part2-change-mgt-vocab/cm-v3.0-cs01-part2-change-mgt-vocab.html

PDF:
http://docs.oasis-open.org/oslc-domains/cm/v3.0/cs01/part2-change-mgt-vocab/cm-v3.0-cs01-part2-change-mgt-vocab.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:

http://docs.oasis-open.org/oslc-domains/cm/v3.0/cs01/cm-v3.0-cs01.zip

Members of the OASIS OSLC Lifecycle Integration Domains 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 OSLC Lifecycle Integration Domains
https://www.oasis-open.org/committees/oslc-domains/

[2] Public reviews:

* 30-day public review, 09 November 2017:
https://lists.oasis-open.org/archives/members/201711/msg00003.html
– Comment resolution log:
http://docs.oasis-open.org/oslc-domains/cm/v3.0/csprd01/cm-v3.0-csprd01-comment-resolution-log.txt

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

OASIS Completes Second Successful Plugfest for STIX/TAXII 2 Interoperability

29 June 2018; Reston, VA, USA; The OASIS Cyber Threat Intelligence (CTI) Technical Committee recently conducted the second STIX/TAXII 2 Interoperability Plugfest as part of a free STIX 2 training event. Nine Plugfest participants–Cisco, FreeTAXII (Bret Jordan), Fujitsu, LookingGlass, MITRE, NC4, NineFX, New Context, and the U.S. Department of Homeland Security—integrated and exercised capabilities in their various STIX/TAXII 2 products.

The STIX/TAXII 2 Plugfest series accomplish several important goals. First, the events provide visibility for the growing list of companies and open source projects that are using these automated threat intelligence standards. Also, the Plugfests are an important validation of the STIX/TAXII 2 specifications themselves and STIX/TAXII Interoperability Tests.

OASIS and the CTI Technical Committee applaud all the Plugfest participants and expresses appreciation to LookingGlass for hosting the event.

Plans for the next STIX/TAXII 2 Plugfest is underway. Any organization that is developing STIX/TAXII 2 capabilities is encouraged to get involved. Organizations interested in participating in the OASIS CTI TC Interoperability Test development and future events should contact communications@oasis-open.org.

More information

CTI Technical Committee

STIX2 and TAXII2 specifications and Interoperability document

About OASIS

OASIS is a non-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 cyber security, privacy, cloud computing, IoT, SmartGrid, and other areas. 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.

Media inquiries: communications@oasis-open.org; +1.941.284.0403

Call for Consent for #UBL V2.2 as OASIS Standard

The OASIS Universal Business Language TC members [1] have approved submitting the following Candidate OASIS Standard to the OASIS Membership in a call for consent for OASIS Standard:

Universal Business Language Version 2.2
Candidate OASIS Standard 01
22 April 2018

This Call for Consent is taking place under the revised TC Process rules effective 01 July 2017 [2]. This is a call to the primary or alternate representatives of OASIS Organizational Members to consent or object to this approval. You are welcome to register your consent explicitly on the ballot; however, your consent is assumed unless you register an objection [3]. To register an objection, you must:

1. Indicate your objection on this ballot, and

2. Provide a reason for your objection and/or a proposed remedy to the TC.

You may provide the reason in the comment box or by email to the Technical Committee on its comment mailing list or, if you are a member of the TC, to the TC’s mailing list [3]. If you provide your reason by email, please indicate in the subject line that this is in regard to the Call for Consent.

This Committee Specification was approved by the Technical Committee and was submitted for the required 60-day public review [4]. All requirements of the OASIS TC Process having been met [5][6], the Candidate OASIS Standard is now submitted to the voting representatives of OASIS Organizational Members.

— Details —

The Call for Consent opens at 26 June 2018 00:00 UTC and closes on 09 July 2018 23:59 pm timezone. You can access the ballot at:

Internal link for voting members: https://www.oasis-open.org/apps/org/workgroup/voting/ballot.php?id=3224

Publicly visible link: https://www.oasis-open.org/committees/ballot.php?id=3224

OASIS members should ensure that their organization’s voting representative responds according to the organization’s wishes. If you do not know the name of your organization’s voting representative is, go to the My Account page at

http://www.oasis-open.org/members/user_tools

then click the link for your Company (at the top of the page) and review the list of users for the name designated as “Primary”.

— Information about the Candidate OASIS Standard and the UBL TC —

The Universal Business Language (UBL) is an open library of standard electronic XML business documents for procurement and transportation such as purchase orders, invoices, transport logistics and waybills. It is designed to operate within a standard business framework such as ISO/IEC 15000 (ebXML) to provide a complete, standards-based infrastructure that can extend the benefits of existing EDI systems to businesses of all sizes.

Version 2.2 is completely backward-compatible with UBL 2.0. UBL is freely available to everyone without legal encumbrance or licensing fees.

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

Editable source (Authoritative):
http://docs.oasis-open.org/ubl/cos01-UBL-2.2/UBL-2.2.xml

HTML:
http://docs.oasis-open.org/ubl/cos01-UBL-2.2/UBL-2.2.html

PDF:
http://docs.oasis-open.org/ubl/cos01-UBL-2.2/UBL-2.2.pdf

Code lists for constraint validation:
http://docs.oasis-open.org/ubl/cos01-UBL-2.2/cl/

Context/value Association files for constraint validation:
http://docs.oasis-open.org/ubl/cos01-UBL-2.2/cva/

Document models of information bundles:
http://docs.oasis-open.org/ubl/cos01-UBL-2.2/mod/

Default validation test environment:
http://docs.oasis-open.org/ubl/cos01-UBL-2.2/val/

XML examples:
http://docs.oasis-open.org/ubl/cos01-UBL-2.2/xml/

Annotated XSD schemas:
http://docs.oasis-open.org/ubl/cos01-UBL-2.2/xsd/

Runtime XSD schemas:
http://docs.oasis-open.org/ubl/cos01-UBL-2.2/xsdrt/

The ZIP containing the complete files of this release is found in the directory:

http://docs.oasis-open.org/ubl/cos01-UBL-2.2/UBL-2.2.zip
— Additional information —

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

TC IPR page
https://www.oasis-open.org/committees/ubl/ipr.php

[2] https://www.oasis-open.org/policies-guidelines/tc-process-2017-05-26#OScallForConsent

[3] UBL TC comment mailing list: ubl-comment@lists.oasis-open.org
(You must be subscribed to send to this list. To subscribe, see https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=ubl.)

UBL main mailing list: ubl@lists.oasis-open.org

[4] Candidate OASIS Standard Special Majority Vote:
https://www.oasis-open.org/committees/ballot.php?id=3200

[5] Public reviews:
60-day public review announcement, 25 April 2018:
https://lists.oasis-open.org/archives/members/201804/msg00006.html
– Comment resolution log:
TBD – no comments received

15-day public review, 28 February 2018:
https://lists.oasis-open.org/archives/members/201802/msg00008.html
– Comment resolution log:
http://docs.oasis-open.org/ubl/csprd03-UBL-2.2/UBL-2.2-csprd03-comment-resolution-log.txt

30-day public review, 08 November 2017:
https://lists.oasis-open.org/archives/members/201711/msg00000.html
– Comment resolution log:
http://docs.oasis-open.org/ubl/csprd02-UBL-2.2/UBL-2.2-csprd02-comment-resolution-log.ods

45-day public review, 01 February 2017:
https://lists.oasis-open.org/archives/members/201701/msg00002.html
– Comment resolution log:
http://docs.oasis-open.org/ubl/csprd01-UBL-2.2/csprd01-UBL-2.2-comment-resolution-log.ods

[6] Statements of Use:

JAVEST: https://lists.oasis-open.org/archives/ubl/201803/msg00025.html

eSENS eTendering pilot: https://lists.oasis-open.org/archives/ubl-comment/201804/msg00000.html

Norwegian Agency for Public Management and eGovernment (Difi): https://lists.oasis-open.org/archives/ubl/201804/msg00003.html

No results with the selected filters