Standards at Oracle

Oracle builds products on standards developed by international organizations and industry consortia.

Oracle is committed to building standards-based products to help customers reduce complexity and get the most out of their existing technology investments. We build products on standards developed by international organizations and industry consortia and strive to comply with market-accepted standards to provide our customers with interoperability, choice, and lower costs. As both a contributor and leader in open source communities, Oracle is a supporting member of the Linux Foundation, Cloud Native Computing Foundation, Eclipse Foundation, and the Java Community Process program, among others.

Oracle participates actively in more than 100 standards-setting organizations and more than 300 technical committees, and thousands of our employees are actively engaged in standards or open source projects. These employees contribute to efforts ranging from Java and Linux to Kubernetes.

Our standards work across global geographies and business units includes collaboration with:

Some examples of our work in standards organizations we drive and influence, including specific verticals and technologies.

Standards are in our DNA

Oracle Founders, 1978
Oracle Founders, 1978
Today Oracle products implement thousands of standards.

Oracle was founded around the implementation of an open standard: SQL. Before we released a product, we were able to participate in developing the SQL standard on a level playing field with established technology companies. SQL became an ANSI standard in 1986 and an ISO standard in 1987.

Everything that we have in our cloud runs in Amazon’s cloud and other clouds that are standards-based.

Larry Ellison Chairman of the Board and Chief Technology Officer

SQL Standard

SQL standard logo
Oracle has been a leading player in the development of the ANSI SQL Standard since it was first released in 1986. The SQL Standard remains instrumental in the huge growth of the SQL relational database market to this day. It allowed Oracle and others to compete on the basis of who could provide the best implementation of the SQL Standard, while giving customers the comfort that coding to standard SQL would not lock them into a particular vendor.

Andy Mendelsohn Executive Vice President, Database Server Technologies

Learn more about SQL

Oracle collaborates with standards-setting organizations

Oracle collaborates with more than a hundred standards-setting organizations, including:

3GPP The 3rd Generation Partnership Project unites seven telecommunications standards organizations to develop specifications for mobile telecommunications.
ANSI The American National Standards Institute is a private, nonprofit organization that supports the development of technology standards in the US by providing a framework for fair standards development and quality conformity assessment systems.
HL7® Fast Healthcare Interoperability Resources® (FHIR) HL7® FHIR® is an interoperability standard intended to facilitate the exchange of healthcare information between organizations.
IETF The Internet Engineering Task Force is a large, open international community of network designers, operators, vendors, and researchers concerned with the evolution of internet architecture and the smooth operation of the internet.
INCITS The InterNational Committee for Information Technology Standards is an ANSI-accredited standards development organization composed of information technology developers. It is the central US forum dedicated to creating technology standards for the next generation of innovation.
ISO/IEC JTC 1 The Joint Technical Committee (JTC 1) for information technology was created by the International Organization for Standardization and the International Electrotechnical Commission. Its purpose is to address international information technology standardization.
JCP The Java Community Process is the mechanism for developing the standard technical specifications for Java technology.
Linux Foundation The Linux Foundation is a nonprofit technology consortium that was founded in 2000 to standardize Linux, support its growth, and promote its commercial adoption. They also provide a neutral, trusted home for developers to collaborate on open software projects, such as the Cloud Native Foundation (CNCF). CNCF hosts projects like Kubernetes and Prometheus to make cloud native universal and sustainable.
OASIS The Organization for the Advancement of Structured Information Standards is a nonprofit, international consortium whose mission is to develop open source software and standards through global collaboration and community.
W3C The World Wide Web Consortium is the main international standards organization for the web.
CEN and CENELEC The European Committee for Standardization (CEN) develops standards for a number of sectors, products, and services. The European Committee for Electrotechnical Standardization (CENELEC) focuses on electrotechnical standardization. Both are legally designated providers of European standards.

Contributions to the Linux kernel

linux kernel development
Building on Oracle's longstanding commitment to open source Linux kernel development, Oracle was the top contributor to the Linux kernel in the 6.1 release cycle. Oracle's contributions to Linux span more than 20 years, with key contributions -- and maintainers -- in the areas of SCSI and iSCSI, XFS and btrfs, memory management with large pages, and even core kernel data structure. At Oracle we strive to improve Linux to ensure that our customers can rely on Linux both today and in the future, contributing both code fixes and also foundational technologies like memory folios and the Maple Tree that become the basis of further improvements.

Greg Marsden Senior Vice President, Oracle Linux

Communications Standards

Oracle’s Communication Global Business Unit (CGBU) supplies industry leading products and solutions to the communications industry. This includes critical signaling network functions for 5G, 4G and 3G cellular networks. It also includes best-in-class products and solutions for SIP-based telephony. These products provide a range of standards based interoperable interfaces and functionality essential for our customers to build and operate their networks and services.



Imagine you are given the opportunity to design a system that supports wireless, mobile communication services. The system can, at its core, be looked at as an extension of existing landline telephony services and, as such, must support phone calls to and from any phone connected to the Public Switched Telephone Network (PSTN). These same telephony services must also be supported for calls between devices connected to the wireless, mobile network you are defining. These and other services provided by the system must work when devices are moving at vehicular speeds.

Oracle’s Communication Global Business Unit (CGBU), through its Acme Packet acquisition in 2013, was instrumental in defining the standards for the interworking of the circuit switched PSTN network with the SIP trunk based PSTN network. CGBU continues to supply industry leading Session Border Controller products based on the standards resulting from those efforts.



In addition, your system must support short messaging, emergency services, location services, access to the internet, and other capabilities enabled by wireless mobile devices. The system must address the regulatory requirements of countries that set aside radio spectrum for use in supporting the system you define. It must scale to support billions of devices, both consumer phones and machines accessing the Internet of Things.

Oracle’s CGBU, through its acquisition of Tekelec in 2013, was instrumental in the original definition of the Policy and Charging (PCC) architecture and protocols introduced in the initial 3G specifications. The PCC architecture manages differentiated network access and the charging associated with that access. Oracle continues to support policy focused products that have been updated to support both the 4G/LTE specifications and the more recent 5G specifications.



Services supported by the system must be accessible from anywhere in the world that has a Radio Access Network (RAN) that conforms to the standards you define. And the system must provide services in a secure fashion, must limit access to the services provided only to those who have signed up for the services and must collect the information needed to allow the companies providing the services to be able to bill for usage of those services.

CGBU’s standards team works closely with our customers to help incorporate their requirements into the 3GPP and GSMA standards. This manifests through joint submissions to the various 3GPP working groups and through direct participation in the regular standards 3GPP and GSMA standards meetings.

Your task is made more complicated by the requirement that the definition of the architecture, protocols, and technologies required to make this system work must be done with and agreed to by both the companies that will operate the network (your competitors) and by the suppliers (companies that are competitors amongst themselves) of the hardware and software required to build out the system you define.

On the surface this might seem like an impossible task. And this is a somewhat simplified definition of the problem solved by the 3GPP standards organization.

3GPP, which stands for Third Generation Partnership Project, was formed in 1998. Prior to 3GPP, mobile telephony standards were defined by regional telecommunications standards development organizations. These standards organizations consisted of the following:

Organization Country
ARIB The Association of Radio Industries and Businesses Japan
ATIS The Alliance for Telecommunications Industry Solutions USA
CCSA China Communications Standards Association China
ETSI The European Telecommunications Standards Institute Europe
TSDSI Telecommunications Standards Development Society, India India
TTA Telecommunications Technology Association Korea
TTC Telecommunication Technology Committee Japan

The standards defined by these groups insured interoperability within their regions but often did not support phones roaming into another region that supported similar, but different, standards. Remember that the system you were asked to define requires that it works anywhere in the world.

CGBU focuses its standards efforts on the SA and CT TSGs. It is through these efforts that CGBU is offering various 5G network functions, including an industry leading Service Communication Proxy (SCP), Network Resource Function (NRF), Network Slice Selection Function (NSSF), Network Exposure Function (NEF), Security Edge Protection Proxy (SEPP), Binding Support Function (BSF), and the policy related Policy Control Function (PCF) mentioned earlier.

The first set of standards defined by 3GPP resulted in what is referred to as the 3G cellular system. The 3GPP organization has continued to evolve these standards and has published definitions of 4G/LTE and 5G versions of the standards. And there is already talk about an emerging definition of the 6G cellular standards.

3GPP is divided into three Technical Specification Groups (TSGs).

Each of the TSGs are then divided into multiple working groups. The following table outlines the currently active 3GPP working groups. Definition of the 3GPP standards is done by these working groups.

TSG
RAN SA CT
RAN1 – Radio Layer 1 (Physical layer) SA WG1 – Services CT WG1 - User Equipment - Core Network protocols
RAN2 – Radio layer 2 and Radio layer 3 Radio Resource Control SA WG2 – System Architecture and Services CT WG3 - Interworking with External Networks & Policy and Charging Control
RAN3 – UTRAN/E-UTRAN/NG-RAN architecture and related network interfaces SA WG3 – Security and Privacy CT WG4 - Core Network Protocols
RAN4 – Radio Performance and Protocol Aspects SA WG4 – Multimedia Codecs, Systems and Services CT WG6 - Smart Card Application Aspects
RAN5 – Mobile terminal conformance testing SA WG5 – Management, Orchestration and Charging
SA WG6 – Application Enablement & Critical Communication Applications

3GPP does not define all the protocols that make up the 3GPP system. In many cases, the 3GPP working groups define how standards developed by other standards organizations are used by the 3GPP system.

Much of the work mentioned earlier that was needed for the definition of standards related to the SBC was done in the IETF SIP and related working groups. CGBU was also active in the definition of IETF Diameter related standards defined by the IETF DIME working group that impacted the CGBU Diameter Signaling Router product.

Many of the protocols used within 3GPP standards are defined by the Internet Engineering Task Force (IETF), the group responsible for defining protocols such as IPv4, IPv6, TCP, TLS, http/2, Diameter, and SIP, to name a few used by the 3G, 4G and 5G 3GPP systems.

The Institute of Electrical and Electronics Engineers (IEEE) defines lower layer protocols such as Ethernet.

The GSMA, the primary industry organization for mobile network operators, also defines standards that are focused on interoperability between network operators. As such, GSMA standards focus on issues such as how the 3GPP system is used for roaming between service providers and how reconciliation of charges happens between those services providers.

For those interested in a little late-night reading, the following are the primary specifications that describe the 3GPP 5G System. These are just the tip of the iceberg as they specify what 3GPP defines as stage 2 specifications. These specifications are developed by the SA2 and SA3 working groups and define the architecture for the 5G Core Network.

Specification Number Working Group Specification Title
23.501 SA2 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
System architecture for the 5G System (5GS);
Stage 2
23.501 SA2 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Procedures for the 5G System (5GS);
Stage 2
23.503 SA2 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Policy and charging control framework
for the 5G System (5GS);
Stage 2
33.501 SA3 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Security architecture and procedures for 5G system

The CT groups take this as input to the 3GPP stage three specifications that define the detailed protocols required by suppliers like Oracle to implement the functionality defined in the standards. The following are a sample of the specifications published by the CT groups. The first two are foundational and apply to all 3GPP defined network functions. The next two detail the protocols for two of the 5G network functions being offered by CGBU.


Specification Number Working Group Specification Title
29.500 CT4 5G System; Technical Realization of Service Based Architecture; Stage 3
29.501 CT4 5G System; Principles and Guidelines for Services Definition; Stage 3
29.510 CT3 5G System; Network function repository services; Stage 3
29.512 CT3 5G System; Session Management Policy Control Service; Stage 3

Lucky for you, 3GPP, IETF, IEEE, GSMA and other standards bodies have already designed the system you were challenged to specify. Now, no matter where you are in the world, no matter who is your cellular service provider, no matter who supplied you with the phone you have in your pocket, you can benefit from the 5G cellular system to check on the traffic and weather forecasts prior to your commute home.

Oracle Cerner

Oracle Cerner has been a leader in supporting the development of healthcare IT standards to help ensure different health IT systems can work together and efficiently exchange information. Look at some of our milestones and you can see time after time, not only are we enabling the exchange of data across the ecosystem; but we have engaged in collaborative efforts that require some level of openness and acknowledge the need to work together and share information for the sake of advancing interoperability to improve healthcare and outcomes.


Date Name Description
1991 Clinical data sharing Began using Health Level-7 standards
1995 X12 Joined X12, a cross-industry organization that develops and maintains Electronic Data Interchange standards that drive businesses globally. Participated in development of X12N standards for healthcare claims transactions used under HIPAA
1998 Michiana Health Information Network (HIN) Worked with clients to develop Michiana Health Information Network
2002 CareEntrust Collaborated with CareEntrust to develop an employer-drive HIE
2004 Electronica Health Record Association (EHRA) Founding members of HIMSS EHRA focusing on collectively advancing interoperability
2007 SharedHealth Worked with clients to create SharedHealth, a Medicaid driven HIE
2008 RAND Corporation study Co-funded a RAND Corporation study to help address need for national patient identification system
2009 Health Information Technology for Economic and Clinical Health (HITECH) Act HITECH Act stimulated significant health IT adoption and exchange electronic health information. The goal was for every American to have access to their electronic health information – In 2015 APIs were added to this requirement
2009 Office of the National Coordinator for Health Information Technology Policy and Standards Appointed to initial ONC Health IT Policy and Standards Committee and continued participating in workgroups over the years
2009 uDevelop uDevelop platform was an early indicator of our willingness to collaborate to advance health care - launched as an ecosystem to be fueled by the wisdom of the crowd
2009 Direct Project Donated 200K lines of Java code since 2009 to the Direct Project
2010 Interop certification Within ONC HIT Certification Program, held CERT 2011 Edition, 2014 Edition, 2015 Edition, 2015 Edition Cures Act Updates
2010 National Council for Prescription Drug Programs (NCPDP) Joined NCPDP to address eprescribing standards
2010 Office of the National Coordinator for Health Information Technology Certification Program First ONC rule making for Health IT Certification Program – a part of this certification is intended to ensure that EHR systems can work with other systems and share information
2011 Direct Project Direct Project launched to enable a secure, standards-based way to electronically send health information
2013 CommonWell Became a founding member of CommonWell, leading a first of its kind effort to enable data liquidity across systems, settings and episodes of care. Created entities to create interoperability and scale the network
2014 Argonaut Founding partner of Argonaut to speed development and adoption of the HL7 FHIR standard
2014 HL7® Fast Healthcare Interoperability Resources® (FHIR) Demonstrated the use of FHIR standards with Boston Children's Hospital at HIMSS14
2014 Direct Deployed workflow-driven Direct capabilities to all US clients
2014 Carequality Active involvement with Carequality since conception to further advance nationwide interoperability
2015 Health Information Exchange (HIE) Hearing testimony Founder Neal Patterson HIE Exchange Hearing testimony: "Health IT platforms must be open… The quality of being open is what allows independent developers to build "apps" and extensions that work with the existing health IT platform.“
2015 CommonWell Advanced the CommonWell Health Alliance for signing up Cerner clients to join the network
2015 HL7 FHIR First EHR to release a production version of FHIR
2016 code Developer Program Launched the Cerner Open Developer Experience – truly opening our ecosystem
2016 Clinical Decision Support (CDS) Hooks Participating in CDS Hooks Collaboration – Cerner developers are providing technical leadership for CDS Hooks, an open-source standard that allows for open and interoperable clinical decision support leveraging both SMART and FHIR
2017 Meaningful Use 3 MU3 requires all providers to offer an API so patients can access their electronic health information
2018 CommonWell/Carequality CommonWell Carequality connection became generally available
2018 Da Vinci Project Co-founded the HL7 Da Vinci Project, applying the Argonaut approach to payer-provider space
2018 consumer First consumer FHIR app goes live
2020 Joint Health Information Exchange (JHIE) Worked with the VA and DOD to launch the joint health information exchange to enable medical providers at both agencies to share patient data with private sector healthcare organizations
2020 HL7 Vulcan FHIR Accelerator Joined HL7 Vulcan FHIR Accelerator to connect clinical research and healthcare
2021 Electronic Case (eCase) Reporting Worked with APHL and CDC to increase adoption of Electronic Case Reporting (eCR) through the development of the eCR Now App to automate case report submissions, resulting in Cerner winning the 2021 eCR Now CO
2021 SMART Health Card Co-founded the Vaccine Credential Initiative to develop a universally recognized digital record of vaccination status. Collaborated to develop SMART Health Cards based on W3C Verifiable Credential and HL7 FHIR standards
2022 The Sequoia Project Joined The Sequoia Project Interoperability Matters to provide information blocking/sharing guidance
2022 HL7 Helios FHIR Accelerator Joined HL7 Helios FHIR Accelerator to address Public Health use cases
2022 Trusted Exchange Framework and Common Agreement (TEFCA) CommonWell announced that it was applying to become TEFCA’s first Qualified Health Information Network (QHIN)

Our work with industry leaders

Building on our continued commitment to multicloud innovation and our leadership and contributions with the International Organization for Standardization, we collaborate with industry leaders to provide our customers with standards-based solutions.

Celebrate the 25th Anniversary of the JCP Program

CNCF

As a Platinum Member with a seat on the Cloud Native Computing Foundation (CNCF) Board, Oracle is able to influence the cloud native standards being developed by industry leaders around the world. Our partnership with CNCF showcases Oracle’s commitment to standards and open source projects based on our customers’ needs. We demonstrate Oracle’s thought leadership to the cloud industry through active contributions to over twenty CNCF Projects such as Kubernetes, Falco (Observability), Thanos (Security), and Crossplane (multicloud). https://www.cncf.io/

I’ve never been more excited about the opportunity that Multi-Cloud presents to Oracle with workloads and data flowing seamlessly across clouds . We’re intensifying our focus and investments in CNCF projects and integrations to provide customers an open source, open standards way of onboarding multiple cloud providers.

Mahesh Thiagarajan EVP Oracle Cloud

Open Enterprise Linux Association (OpenELA)

Collaboration is critical to fostering innovation, which is why we welcome everyone to be part of this association and help us uphold open community standards,” said Thomas Di Giacomo, chief technology and product officer of SUSE. “SUSE is a strong believer in making choice happen. Together with the open source community we will redefine what it truly means to be open and deliver a stronger future for EL.

Thomas Di Giacomo Chief Technology and Product Officer, SUSE

Read the press release

Microsoft

Oracle Database@Azure gives customers direct access to Oracle database services running on Oracle Cloud Infrastructure and deployed in Microsoft Azure datacenters.

Learn more about our Microsoft collaboration

We have a real opportunity to help organizations bring their mission-critical applications to the cloud so they can transform every part of their business with this next generation of AI,” said Satya Nadella, Chairman and CEO, Microsoft. “Our expanded partnership with Oracle will make Microsoft Azure the only other cloud provider to run Oracle’s database services and help our customers unlock a new wave of cloud-powered innovation.

Satya Nadella Chairman and CEO, Microsoft

Most customers already use multiple clouds,” said Larry Ellison, Oracle Chairman and CTO. “Microsoft and Oracle have been working together to make it easy for those customers to seamlessly connect Azure Services with the very latest Oracle Database technology. By collocating Oracle Exadata hardware in Azure datacenters, customers will experience the best possible database and network performance. We are proud to partner with Microsoft to deliver this best-in-class capability to customers.

Larry Ellison Oracle Chairman and CTO

Ampere

With a nod to Oracle's strong leadership in the ISO/IEC JTC 1/SC 38 (Cloud Computing & Distributed Platforms) committee to create heterogenous cloud environments, Ampere and Oracle created Arm-based Kubernetes clusters running under the Oracle Container Engine for Kubernetes (OKE) that use the Ampere A1 Cloud Native compute platform in Oracle Cloud Infrastructure (OCI). The choice, interoperability and maturity of this cross-platform service provides opportunities for easy migration and further innovation for our customers.

Sean Varley Vice President of Product Marketing, Ampere

Learn more about Ampere standards

Arm

Arm is quickly becoming a popular choice for customers in the cloud. Arm and Oracle developers are collaborating in the Linux kernel and related upstream projects on a wide variety of technologies to benefit the entire ecosystem, for example, Oracle's contributions to memory management (including maple tree data structure and folios) are enabling performance improvements wider than their specific application. Oracle is also working closely with Linaro to bring virtual CPU hotplug functionality to the Arm architecture. It’s this kind of cross-industry collaboration that helps Linux and the Arm ecosystem to continue to succeed.

Mark Hambleton VP Software, Arm

Java

ampere logo
The Java Community Process (JCP) program has a long and trusted history of establishing specifications that are the foundation of applications developed by millions of developers running on billions of processors. The entire software industry benefits from this and the coupling with the incredible pace of innovation happening at OpenJDK, which drives the standard Reference Implementation for the JCP program. Oracle is proud to stand with our partners who have been moving the Java ecosystem forward for almost 30 years.

Georges Saab Senior Vice President of Development, Java Platform and Chair, OpenJDK Governing Board, Oracle

Learn more about Java standards


Oracle Releases Java 21

New release delivers 15 JDK Enhancement Proposals to increase developer productivity, improve the Java language, and enhance the platform’s performance, stability, and security.

Celebrating 25 years of JCP Program


JCP 1.0

Created JCP, in which Sun approved requests and members contributed to specifications.

1998

JCP 2.0

Established Executive Committees to review and approve JSRs.

2000

JCP 2.5

Granted equal standing to individuals.

2002

JCP 2.6

Embraced open source, streamlined processes, opened up early drafts, license, and TCK terms to the public.

2004

JCP 2.7

Required transparency for public comments and revised the timing of releases.

2009

JCP 2.8

Introduced EC Standing Rules, required transparency in JSR communication, and shortened JSR deadlines.

2011

Adopt-a-JSR

Launched to include voices from JUGs around the world on Java standards.

2011

JCP 2.9

Merged the two ECs into one committee that votes on all JSRs.

2012

JCP 2.10

Broadened membership, removed barriers to membership, added Contributors, and established three types of EC seats.

2016

JCP 2.11

Streamlined JCP program's processes for agility, aligned with open source software development, and reduced the size of EC.

2018

Java in Education

Launched to inspire and educate the next generation of Java developers and bridge the gap between academia and industry.

2020

25th Anniversary

Celebrate 25 years of the JCP program.

2023
To move to the beginning and end use function plus left or right arrow. To move by five steps use function plus page up or page down.
For over 20 years Arm has been an active member of the Java Community Process (JCP), with many long-term contributions to the OpenJDK project. Collaborating with Oracle to move Java to a six-month release cycle has accelerated the evolution of the language and brought new features, like virtual threads and an improved Garbage Collector, to market sooner. The Java 21 release delivers the sixth incubator of the Vector API on Arm, bringing the power of the SVE vector architecture to more Java developers. Our work to enable these key improvements will keep Java at the forefront of scalable, high-performance, cloud native development running on Arm Neoverse cores.

Stuart Monteith Principal Software Engineer, Arm

Performance and Java platform compatibility are critical for customers deploying Java-based workloads on Ampere A1 shapes in OCI, and on premise. Recognizing this, Oracle and Ampere experts have collaborated to significantly increase Java performance across OpenJDK versions, working within the Java specifications and programs such as those led by the Java Community Program (JCP), and specifically Java Specification Request (JSR) 395 covering Java SE 20. Thanks to this collaboration and our open specifications, Java performance is up to 30% higher with the latest JDKs. Even legacy workloads can benefit, including the recently announced Enterprise Performance Pack, which allows customers to get JDK 17 performance on JDK 8 applications.

Atiq Bajwa Chief Technology Officer, Ampere

Artificial Intelligence

Oracle participates in the development of artificial intelligence (AI) standards. The projects in these standards bodies address a variety of aspects of AI systems – bias/fairness, human oversight, explainability/transparency, risk management, privacy, and security. Such standards advance technical harmonization and support market access.


ISO/IEC JTC 1 SC 42 This is a joint body under the International Organization for Standardization (ISO) and the International Electrotechnical Commission (IEC) established AI standardization.
CEN/CENELEC JTC 21 This is a joint body under the European Committee for Standardization (CEN) and the European Committee for Electrotechnical Standardization (CENELEC). Joint Technical Committee 21 develops and adopts standards for AI and related data. This body has also been tasked with establishing harmonized standards (European Norms) for the AI Act.
ETSI ISG SAI The European Telecommunications Standards Institute (“ETSI”) established an Industry Specifications Group on Securing Artificial Intelligence (ISG SAI). This group addresses security of AI and the use of AI to support security.

We are also engaging in the AI activities of:

  • The National Institute of Standards and Technology (NIST, under the US Department of Commerce)

    1. The Trustworthy & Responsible Artificial Intelligence Resource Center (AIRC), which includes supporting the NIST AI Risk Management Framework (AI RMF) and Playbook as well as other resources that cover topics such as bias/fairness and explainability.
    2. The Generative AI Public Working Group.
  • The Organisation for Economic Co-operation and Development (OECD), including the Working Party on Artificial Intelligence Governance (AIGO).
  • The EU-US Trade and Technology Council (TTC), including Working Group 1 on Technology Standards and its AI subgroup as well as the Joint Roadmap on Trustworthy AI and Risk Management

Disclaimer: We participate in, contribute to, or follow these activities, but we make no representations about individual products meeting all standards and versions.

Learn about Oracle Trust Center