May 2019 - OASIS Open

Service Metadata Publishing (SMP) v2.0 from BDXR TC approved as a Committee Specification

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

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

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

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

The prose specifications and related files are available here:

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

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

Distribution ZIP file
For your convenience, OASIS provides a complete package of the prose specification and related files in a ZIP distribution file. You can download the ZIP file here:
https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs01/bdx-smp-v2.0-cs01.zip

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

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

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

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

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

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

Invitation to comment on TOSCA Simple Profile in YAML v1.3 – ends June 21

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

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

The documents and related files are available here:

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

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

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

How to Provide Feedback

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

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

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

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

All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the TC members. In connection with this public review of “TOSCA Simple Profile in YAML Version 1.3”, we call your attention to the OASIS IPR Policy [1] applicable especially [2] to the work of this Technical Committee. All members of the TC should be familiar with this document, which may create obligations regarding the disclosure and availability of a member’s patent, copyright, trademark and license rights that read on an approved OASIS specification.

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

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

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

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

Borderless Cyber Wrap-up Report

including slides and photos
8-10 Oct. | The National Press Club, D.C.

Cross-Enterprise Security and Privacy Authorization (XSPA) Profile of SAML v2.0 for Healthcare v2.0 from XSPA TC approved as a Committee Specification

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

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

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

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

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

The prose specifications and related files are available here:

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

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

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

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

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

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

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

ECF Web Services SIP v5.0 from ECF TC approved as a Committee Specification

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

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

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

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

The prose specifications and related files are available here:

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

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

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

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

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

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

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

Electronic Court Filing v5.0 from ECF TC approved as a Committee Specification

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

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

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

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

The prose specifications and related files are available here:

Electronic Court Filing Version 5.0
Committee Specification 01
18 April 2019

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

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

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

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

Exchange Header Envelope (XHE) v1.0 from BDXR TC approved as a Committee Specification

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

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

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

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

The prose specifications and related files are available here:

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

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

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

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

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

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

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

OASIS-Oxford Host Two-day International Privacy Workshop

9-10 September | Oxford University
Open call for presentations & posters.

OASIS Introduces Open Projects Program to Bridge Open Source and Standards Development

AirBus, CIB, Fujitsu, IBM, Red Hat, Siemens, Software AG, The Document Foundation, and others sponsor Open Projects

BOSTON (PRWEB) MAY 08, 2019 – OASIS, a global nonprofit consortium, today announced the launch of Open Projects, the first-of-its-kind program that creates a more transparent and collaborative future for open source and standards development. Open Projects gives communities the power to develop what they choose–APIs, code, specifications, reference implementations, guidelines– in one place, under open source licenses, with a path to recognition in global policy and procurement.

The lines between open source and open standards have been blurring for some time, and communities in both arenas have been calling for more flexibility and options for collaboration. Open Projects is a new approach that addresses the need for change in everything from handling IP to governance and decision-making, from funding to establishing trust and assuring quality.

“With Open Projects, we’re building a movement to transform the open source and standards world,” said Gershon Janssen, Chairman, OASIS Board of Directors. “We want to dissolve the barriers that separate communities. We want to empower groups with more control and streamlined governance. We want to support projects by giving them all the process they need–and not a bit more–so they can accomplish great things fast.”

Open Projects builds on the OASIS experience and reputation for producing quality work that’s been trusted and supported by governments and industries worldwide for more than 25 years.

“For many, open source has become a means of establishing de facto software standards. However, de facto standards are not recognized by many governments and institutions.” said Chris Ferris, IBM Fellow and CTO Open Tech for IBM. “OASIS Open Projects provides an important new opportunity to leverage the rapid innovation of open source in the process of developing open standards. The potential to achieve ISO, IEC, or ITU standards approval is a huge value for many important open source initiatives.” Ferris, who also holds a leadership position on the Hyperledger Fabric project, played an instrumental role in defining the OASIS Open Projects program and now serves on its Advisory Council.

The Open Projects program is being advanced by some of the most accomplished, regarded minds in open source today. The Open Projects Advisory Council provides strategic insight on the needs of open source projects, identifying current practices that work well and exploring new approaches where improvements can be made with a goal of curating the future of open source. Advisory Council members include:

Kris Borchers (Sr. Program Manager, Azure PIE Open Engineering, Microsoft)
Amanda Brock (Director of Open UK, Trustable CEO)
Deborah Bryant (Senior Director, Open Source Program Office, Office of the CTO)
Chris Ferris (CTO Open Tech for IBM, Hyperledger TSC member)
Georg Grutter (Chief Expert, Bosch)
Jim Jagielski (Open Source Chef for ConsenSys, co-founder of The Apache Software Foundation)
Tobie Langel (Principal of UnlockOpen, AMP Advisory Committee Facilitator)
Heather Meeker (Open Source Licensing Specialist, OSS Capital)
Tracy Miranda (Director of OS Community, CloudBees)
Nithya Ruff (Senior Director, open source program office, Comcast)
Josh Simmons (Sr. Open Source Strategist for Salesforce, OSI Board Director)

As part of the program announcement, OASIS is launching the first two Open Projects – Open Services for Lifecycle Collaboration (OSLC) and OpenDocument Format (ODF) Advocacy.

The OSLC Open Project advances a suite of standard REST APIs to connect data and achieve the digital thread across domains, applications, and organizations. It is sponsored by AirBus, Austrian Institute of Technology, Bank of America, Boeing, Dassault, Fujitsu, IBM, Koneksys, KTH Royal Institute of Technology, Red Hat, Siemens, Software AG, and Tasktop.

“OSLC helps create standard REST APIs that solve industry integration challenges,” said Andrew Berezovskyi, of the KTH Royal Institute of Technology. “Open Projects enables the OSLC community to produce deliverables that meet requirements from various stakeholders without being hindered by the weight of foundation bureaucracy or the baggage that comes with financial, legal, technical, and marketing administration.”

The ODF (Open Document Format) Advocacy Open Project promotes the world’s leading document standard. After being approved as an OASIS Standard, ODF was recognized by ISO/IEC and endorsed by governments around the world as a way to ensure permanent access to data and eliminate the risk of vendor lock-in. The ODF Advocacy Open Project is sponsored by CIB and The Document Foundation.

“ODF guarantees perennial access to data that can be transferred in a transparent way between different apps, computers and operating systems, getting rid of hidden interoperability costs, vendor lock-in issues and license fees,” said Italo Vignoli, Co-Founder, The Document Foundation.”

Additional Open Projects for blockchain and other areas will be announced in the coming months. Further details about OASIS Open Projects are available here or email info@oasis-open-projects.org.

About OASIS
One of the most respected, member-driven standards bodies in the world, OASIS offers projects—including open source projects—a path to standardization and de jure approval for reference in international policy and procurement. OASIS has a broad technical agenda encompassing cybersecurity, privacy, cryptography, cloud computing, IoT–any initiative for developing code, APIs, specifications, or reference implementations can find a home at OASIS. Some of the most widely adopted OASIS Standards include AMQP, CAP, CMIS, DITA, DocBook, KMIP, MQTT, OpenC2, OpenDocument, OSLC, 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. http://www.oasis-open.org

Media Contact
Ray George
650-922-3825
ray.george@oasis-open.org

No results with the selected filters

Service Metadata Publishing (SMP) v2.0 from BDXR TC approved as a Committee Specification

Invitation to comment on TOSCA Simple Profile in YAML v1.3 – ends June 21

Borderless Cyber Wrap-up Report

Cross-Enterprise Security and Privacy Authorization (XSPA) Profile of SAML v2.0 for Healthcare v2.0 from XSPA TC approved as a Committee Specification

ECF Web Services SIP v5.0 from ECF TC approved as a Committee Specification

Electronic Court Filing v5.0 from ECF TC approved as a Committee Specification

Exchange Header Envelope (XHE) v1.0 from BDXR TC approved as a Committee Specification

OASIS-Oxford Host Two-day International Privacy Workshop

OASIS Introduces Open Projects Program to Bridge Open Source and Standards Development

The work of OASIS is supported by organizations from around the world. Members include: